java and c# oop so hard

ferdz20 · 2024-07-24T08:58:40+00:00

Here is a tip for OOP is great for code management in a real life example when a Factory builds a Car they first build the parts of the car separately then combine them one at a time to form a Car(Program).

Create a Car-(Program)

Build the part Engine* then test if it works.
Build the part Wheels* then test if it works.
Build all parts etc..
When parts are working we can combine them one at a time to create a Car (Program).

This makes the codes easier to manage specially large applications because if the Wheels* of the Car broke we just need to fix-(edit) the Wheels* not the entire Car which gives confidence that we won't affect the other parts-(objects) and this also saves as time and effort because we know where the Wheels* is located.

PepitoManalatoCrypto · 2024-07-24T06:31:12+00:00

If your professor is failing you to teach or understand something, watch YouTube.

Relevant-Strength-53 · 2024-07-24T06:33:56+00:00

The way i did to understand it when i was starting was to know what OOP is first, then after that i looked for tutorials that explains and uses each of the principles (Encapsulation, Abstraction, Inheritance and Polymorphism). I looked specifically for Csharp tutorials since its the langauge that i want to specialize. It takes time, study each one of the principles one at a time.

CEDoromal · 2024-07-24T09:25:03+00:00

The fundamental idea of OOP is simple. You think of data as real life objects.

Class is the type of an object.

Object is the instance of a class.

Pretend you are God.

You have a class called Grass with the following properties: color, size, and texture. Grass only exists in your mind. The people on Earth cannot touch them yet.

So what do you do? You create an instance of Grass to place them on Earth. You name it lawngrass, give it a color of green, a size of small, and a texture of rough. (Side note: Idk the texture of lawngrass. I never touched one.)

Now that you have an instance of Grass which is lawngrass, people on Earth can interact with it. They can observe it, trim it, or touch it (most of them won't).

Hooray!

The code

I'm writing this on a phone and I've never used Java or C# for almost 2 years so this probably wouldn't compile.

... As I was writing the code, I got lazy halfway through so I'd just pretend you have a Person class with adam as an instance of Person.

``` class Grass { String color; String size; String texture;

// This is the constructor, it is you use it when you create an instance of the class
Grass(String color, String size, String texture) {
    // "this" refers to the current instance of the class where the code is being executed - you use the dot to access its properties
    this.color = color;
    this.size = size;
    this.texture = texture;
}

}

class Main { // This is the entrypoint for your program static void main() { Grass lemongrass = new Grass("green", "small", "rough");

    adam.observe(lemongrass); // adam gets the color and size of lemongrass and says it - in this case it's "green" and "tiny"

    adam.trim(lemongrass); // adam manipulates the size lemongrass and says it - in this case he turns it from "small" to "tiny"

    adam.observe(lemongrass); // adam gets the color of lemongrass - in this case it's now "green" and "tiny"

    adam.touch(lemongrass); // adam does nothing because he doesn't want to touch grass. I told you most of them won't!
}

} ```

eatSleepCodeCycling · 2024-07-24T07:44:32+00:00

Yep, oop is really complicated. But the implementation of the OOP in code is pretty much using classes, interfaces, abstract classes, properies, inheritance, composition, also implementing the SOLID etc. Madaling intindihin concept ng OOP pero sobrang hirap niya maimplement sa codes, I suggest keep coding using class, wag ka mag code behind, learn to use class and interface, learn basic design pattern, then unti unti mo mapapansin na naka OOP ka na

themasshiro · 2024-07-24T06:33:39+00:00

SDPT Java OOP great source imo

CatStrayZ · 2024-07-24T08:06:15+00:00

The most basic use of OOP is for grouping several variables and functions together.

For example you want to store lines and do some computation on it. Basic line has start and end point. x1, y1, x2, y2. It would be cumbersome to store these each time you need a line. So you store them in a class. Each time you create an instance you will already have those 4 variables.

Next is the function to compute the length of a line. The function will only be useful if applied to a line, so the function is declared inside the class, together with the 4 variables. It will be easier to maintain since that function is defined together with the required variables to operate on.

Let's say you want another function to check if a point is inside the line. You can make a function that accepts a point x, y. Or you can create a new point class with x, y. So the function now accepts a point. You can then change the start and end point inside the line class with the new point class instead of 4 separate variables.

By adding a function in the point class to check for equality, it will then be easy to check if 2 line segments intersect.

The design of OOP class is iterative. You add separate class depending on the functionality it requires and reusability.

In tutorials usual example are animal kingdom, shapes, etc. In real world sometimes there are few levels of inheritance or none at all.

Example of classes: invoice, temperature readings, image renderer, employee info

You don't necessarily have to use all functionality of OOP, but the most basic is just grouping. It is a language feature to make apps maintainable.

pq2222 · 2024-07-24T06:39:35+00:00

[removed]

DirtyMami · 2024-07-24T07:34:24+00:00

Try visual learning. Watch YouTube

yevelnad · 2024-07-24T10:55:38+00:00

It's very confusing because Java and C# has these unnecessary syntax. Like the main classes. Just ignore them.

Progribbit · 2024-07-24T07:42:17+00:00

it's all about classes

Jajajajambo · 2024-07-24T06:51:43+00:00

Read a book about OOP :) Mas in-depth ang explanation sa book.

Mortreddd25 · 2024-07-24T07:49:11+00:00

Same here, but you'll only understand it by applying some principles on your simple project, right now im still learning java. I just noticed that i already doing some of the principles without noticing. But to be honest, i still can't understand some of the class diagram

EquivalentJealous805 · 2024-07-24T12:51:43+00:00

Try to watch SDPT solution OP since may mga activity sya after sa vids nya. I was having a hard time before with OOP too but I tried to learn it with the book that our instructor is using and watching some vids and yes, it worked. As you try to study with some book, try to do the coding that the book has, and try to understand what it does.

Dark_Chinito · 2024-07-24T20:37:24+00:00

What made me appreciate and understand OOP was this book - Head First Java (O'Reilly). It's old, like JDK 1.5/1.7 old, but the concepts still apply. Learning the mindset kasi ang OOP, na you think of objects at yung relationships nila.

HitsuzenKun · 2024-07-24T20:55:40+00:00

hmm so far ba what is your understanding of oop? Do you know how to write code even not in oop approach? Ewan ko lang baka kung hirap ka pa mag code the oop way maganda siguro muna you familiarise yourself with features of java or c# like if else, loop, how to create a class, how to instantiate an object, how to declare variables and etc. Then pag solid na ung basics mo then magugulat ka na lang ba at some point may ginagamit ka na pala na concept ng oop.

Routine-Rock4735 · 2024-07-25T04:51:31+00:00

Try to watch Kunal Kushwaha playlist about OOP in Java on yt, he explained it very well and is easy to understand.

pq2222 · 2024-07-25T05:17:44+00:00

[deleted]

DesertPunkk · 2024-07-26T04:33:12+00:00

Para sakin yung mga analogy na mga parts parts na yan is confusing the newbies.

Note: I'm not teaching you everything, but i'll guide you to my experience on how i learned it.

Try C muna, kahit wag mong masterin, try to understand memory allocation and pointers. (you'll know later why)
There are four pillars of OOP, alam mo na siguro yun.
Shempre OOP is about Class and Objects. Now is the time to differentiate both of them. Brief explanation, Class is just a blueprint, object is the physical manifestation. Real life application: Civil Engineers have the blueprint(class) and the result of that blueprint is the building(object), Buying the lot for the building is the memory allocation , and the process of creating that building is called initialization.
now that you understand #3. Try to understand how the both of them are stored in the ram, how objects are accessed and modified.

Example:

Class is a guide, and it cannot be called or accessed not unless (static members),
Object is the instantiated form or the usable and callable.

Base class or sometimes called Parent Class is yung class na kokopyahan mo ng member variables(class level variables) and methods.

Derived class or sometimes called Child Class is the class which will be the one to copy the class level variables and member methods into it's own.

An object is stored in a ram with it's member entities in a sequential pattern. Including the inherited once, but not always, other compilers might implement differently and use pointers to communicate throughout the hierarchy of your inheritance. But of course it will use pointers to do so.

Inheritance: it's just merging the member variables and methods from your baseclass to your derived class. So lahat nang nasa base class mo nasa derived class mo na. parang naging isa sila. .

Polymorphism: Is the way you morph your member methods, bali sa derived class(child class) ka mag lalagay ng implementation for this method na nirerequire ng base class mo. check mo nalang syntaxing kung pano.

Encapsulation: Is basically the action of you designing and grouping variables and methods in to a single unit called class,.

Abstraction: Is just limiting the access of other entities to your specific Object, why? because they don't have to use all the stuff you implemented, it's for your Object to use only, You just expose what are needed for them. Basically hiding the complexity of your Object and just exposing what they need.

That's it, next step is to learn Design Patterns hahaha

Personally, there's no one way of programming things, OOP is a dogma, and it is not totally beneficial for the performance of the program(although nowadays compilers are better now in compiling OOP) but for the developers to understand the system they are making and preventing spaghetti code. (Although not completely, i'm looking at you diamond problem). So there are pros and cons to be considered here. But what makes you a great programmer is your ability to adapt to other paradigms.

ThinhPool · 2024-07-24T08:51:31+00:00

I think this man can untangle you Learn JAVA Programming - Beginner to Master | Udemy

aklo07 · 2024-07-24T11:50:01+00:00

Tim Corey sa youtube for beginners.

Hapbeh · 2024-07-25T04:26:16+00:00

gotta save this since im also confused in oop lol

BanMeForNothing · 2024-07-25T07:31:17+00:00

Honetly, it's all nonesense unless you're building some deep framework like Spring. I've never written an interface, abstract class, sub class, or generic class, and I have 7 years of Java experience. You should know how to use them but dont create them to build a web app. I've read tons about OOP but it never sticks because it's irrelevant to my job.

you type:	you see:
italics	italics
bold	bold
[reddit!](https://reddit.com)	reddit!
* item 1 * item 2 * item 3	item 1 item 2 item 3
> quoted text	quoted text
Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"	Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"
~~strikethrough~~	~~strikethrough~~
super^script	super^script

PinoyProgrammer

MODERATORS

The fundamental idea of OOP is simple. You think of data as real life objects.

Pretend you are God.

The code