Let's clarify:
* Github is not Git
* Android is not Java
* Unit test is not TDD
* Java is not OOP
* Docker is not Devops
* Jenkins is not CI
* Agile is not institutionalised total chaos
* Developer is not Printer Support

A guy and a girl are in a Java seminar.

Afterward, the guy approaches the girl and asks, "Hey gurrl, can I get your number?"
Girl says "Sorry, I don't give out my number, it's private."
Guy says, "Oh I'm sorry, I thought we were in the same class!"

Boys use the word FRIENDSHIP to strart the relationship...

Girl use the word FRIENDSHIP to end the relationship...

Real example of Polymorphism...😜😜😜

If you write it twice and it's not a function call, it's wrong.

True story bro 😂

HTML - hot tomato monkey language
CSS - crazy stupid script
PHP - per hour pay
JS - just scream
JAVA - just a valid acronym
C# - see sharply
Objective C - OOP cash
C - cash
C++ - cash++

She: "I am not getting anything out of these classes!!"

Me: "Try making some Objects first"

*Awkward silence*

How I felt learning JavaScript coming from a strict OOP language...

Gotta love OOP

Colleague: OOP is so elegant, isn't it? *Stares at me with a greedy smile*

Me: ?

Colleague: look how classy it gets!

Kms

The interview was for an internship, I was so nervous about it and thats how I fu*ked it.

Q: So you have studied OOP?
A: Yes Sir, I have studied OOP in C language.
And the rest is history. 😃😃

Interviewer: Can you explain OOP to a six year old?

Applicant: About the 6yo, are you referring to a client or you?

🤦‍♂️🤦‍♂️🤦‍♂️

Chuck Norris can instantiate an abstract class.

IKR. 🙂

Damn right :3

OOP programming be like....

Object oriented thinking.

A boy tries to look at girl in a class.

Girl : It's bad manners.
Boy : No it's not. "MEMBERS OF THE SAME CLASS CAN ACCESS PRIVATE DATA".

when your teacher says he prefers this:
class A
{
// code
};

over this:
class A {
// code
};

me: can u not

Seeing OOP classes with more than a 1000 lines of code really pisses me off.

Functional Programming literally has 'fun' in the title; OOP is one letter away from 💩. I rest my case.

The moment that I finally understood OOP.

Several teachers had already given up explaining it over and over again but one classmate took a few hours to explain.

Suddenly, after a few hours, that AH-HA! moment was there!

I've done as much OOP programming as possible since then and have explained it to others who were struggling with it as well 😊

Java: I'm the complete OOP Language

C: I'm used in most of the places

Python: I am the simplest language that can do wonders...

Assembly level Language: At last you all have to come to me. So all of you STFU.

// Objectify woman
Woman woman = new Woman();

first day of new junior.
me : tell me what you know about inheritance
junior : don't look at me, we're very poor, if my parent's die i wont get a single dime

me(in my head) : this is gonna be fun.

Maybe old, but I had to...

The best prank I ever pulled was on one of my IT teachers.
In 2011, I had an intense OOP JS training and whil ...[read more]

Programming tips #2
overriding vs overloading

The real OOP... Object Oriented Pooh!

Looking for Software Engineers with POOP experience!

"OOP is just a trend." - My first year internship technical manager. It happened 6 years ago, the guy retired soon after.

What’s the object-oriented way to get wealthy?

Inheritance

Finally i get it.

Object oriented way of getting shit rich?

Inheritance.

Pair a FP programmer with an OOP programmer for nine months and they will give birth to a whole new level of procrastination.

Don't get me wrong, I like funcional programming, but this smug „This would neeever happen with FP“ bullshit really gets on my nerve and kind of turns me off the idea of ever wanting to work with FP programmers.
It's just another paradigm, it's still possible to write unmaintainable fuckugly crapcode with functional programming.
And it is still very possible to write beautiful, clean, well maintainable code with OOP. Get over yourselves and understand that it's a tool and not a religion, and a good dev should know when to pick which tool for which job without childish notions of intellectual superiority.

This is why we can't have good things

"Dont use OOP"
- teachers at school

it's time to review your concepts!!! lol

The use of git and understanding/working with foreign keys and performing (including the understanding) JOIN queries.

Also, it took me years and to understand OOP.

When think back to my code from before that, my brain spontaneously starts bleeding.

My CTO in the 'good old times', when he still talked to me and shared his wisdom, once told me what I should know about oop and explained me the world of programming and what really matters:

CTO about oop and C#:
"I think this object orientated stuff is overrated and useless. You don't get finished. I write everything in one file. You should do that too. The fastest way is always the best one."

So, dear readers, you might think, he maybe understood, what oop means. I have to disappoint you. He is as FUCKING STUPID as he sounds.
He didn't understand the whole concept of the language C# or oop.
He doesn't use properties, every single method is static void and there is nothing like an object.

Since there is more from where that came from, this will be continued...

WTF python.... How the fuck are you an OOP language and unable to overload constructors...?

No method overloading... and they say JAVA is a shitty language.

Inheritance in cpp

I could go on for days about this. I am gonna go with the captain. COME AT ME!!

Emojicode is a full OOP language. Should I build my startup on it?

Anyone remember when PHP was a straightforward procedural language and not a pseudo-objective mess?

#saturdaynostalgia

Talked to long time friend a while back.
I think he freelances now and does some kind of web design stuff.

He said, he hates java, and I asked what he hates about it:

" Those stupid variable types, I only use VAR in PHP to get around that stupid stuff. And what is this Oop anyway?".

😵 Dude? The fuck?

If you are using a language that allows OOP and you're not coding to OOP standards... I hate you.

Functional Programming literally has 'fun' in the title; OOP is one letter away from 💩. I rest my case.

last semester i was working as assistant professor teaching Basic OOP Subject. and my girl happens to be enlisted as my student. One day she was late for my class and get in without a permission. so i ask her
Me : Why don't you knock the door?
Her : Why should i ?
Me : did i give you my permission ?
Her : Public class doesn't need permission. our class is not Private.

oh my god i'm so in love with her

Do u like the languages that use the OOP?

Spent 2-3 weeks on implementing a new feature, a guy with 10 years of experience jumps in and solves it within 5 days.

*Oh! I forgot to mention, it was his first time working with the framework.

I must say his OOP skills are really good, not sure if this is something you learn by reading books or simply by practice.

I strongly believe that if you have a good understanding of how to build apps with OOP pattern, you'll do a great job in the SW industry.

1 - when I actually got the point of OOP

2 - When I got that I could check if a number was odd or even by doing & 1

3 - (in the future) when I will understand lifetimes in rust.

When you don't use OOP for a casual project, but then shit gets real and you have to redesign the whole thing

I'm so fucking tired of OOP.
This bullshit never ends. Everyone treats OOP in their own, proper (of course) way. You read tons of those fashion books, like uncle bob and shit. and then comes a dumb asshole that starts reviewing your code, and tells you doing it wrong. FUCK. and you can't tell anything to your TL or PM cuz they are same dumb asholes. Because after you fix all the bullshit from the first asshole, those more responsible assholes come and tell you that you still doing it wrong.

- uh.. bruh, why don't you make interface for everything? that' S.O.L.I.D, you know.. it just right thing.
- bruh, why don't you use enum and switch case. we need a factory.
- bruh, we don't use abstract classes, use interface
- could you rewrite your linq/stream thing into a class and a method. it's just simpler for us. foreach loop is something everyone knows.

well,then go and LEARN the tool you're dealing with, coderfucker.

FUUUUCK.

Learning to apply OOP. Still trying to learn it, actually :P Self-learning for the win!

Let's stop putting business logic in Constructors...

I sincerely like the moment, when i train a newbie to code .NET showing him/her how far OOP in .NET goes.

I love to give the following example:
var s = "round and round it goes";
s = s.ToString().ToString().ToString().ToString().ToString().ToString().ToString().ToString().ToString().ToString().ToString().ToString().ToString().ToString().ToString().ToString().ToString().ToString().ToString().ToString().ToString().ToString().ToString().ToString().ToString().ToString().ToString().ToString().ToString().ToString().ToString().ToString().ToString().ToString().ToString();

And yeah. It's totally fine.
Because each component of .NET is inherited of object. And the class object supports you with the function "ToString()".

After that, in most of the cases, i get a slightly irritated look from the newbie.
Than i say, "welcome to Microsoft" ;)
I finally add, that the compiler of .NET finally identifies duplicate results and refactores the given code before execution ^^

Coding Is fun, as long as you get the big picture/concept of the language you're using.

Use OOP, my father once said. Truly wise man, he was...

When I got to learn about json yesterday I hate it cause I need to do extra work to MVC project. But after today the instructor told us what it does, and I love it. Gonna start learning this stuff more tomorrow

My teammate just said they don't know what OOP is 🙃

The easy way

I'm suprised how many programmers think polymorphism is exclusively an OOP thing.

Dont lynch me or anything but...
What if OOP _isn't_ the best programming paradigm?

So I'm just wondering if this happened to everyone else because a few friends of mine at work have corroborated my experience.

So, when I was very young and just starting to learn PHP, I was trying to grasp OOP. I read and read about it and did the example tutorials and nothing really did it for me. Then one day, writing some scripts for a game I played, it just hit me. Literally like "oh.....I get it. That's why this is a thing."

Got an assignment for my OOP class, looked at it, laughed, "haha this is baby stuff I could code this by farting on the keyboard"
Wrote 400 lines of code without debugging
🙃.... Why do I do this to myself?

Went to a job interview for ASP.net even though I don't know ASP.net since they asked me to come. I got the job since I was the only candidate that knew what OOP is.
I don't really want to work there.

Oh my god, who would do such thing O_O

*uses java and c# for a few months without touching GML or my custom script language*

*Jumps back in after said few months*

Oh god I miss OOP, please give it back!

Basic OOPS Question -

A unit of computer information that contains data as well as all the procedures or operations is called:
(1) A method.
(2) Encapsulation.
(3) An object.
(4) An OOP
(5) None of these

This question is a bit confusing to me.. what do you guys think? 🙄

During our OOP class, our lecturer taught us how to make GUI, how to make stuff move, and so on..basically our reaction during the whole class was "woahhhhh...coding is actually fun" XD

Classes are not namespaces!!

Technical phone screens be like, "we see you have years of OOP experience, but can you tell us about the differences between an interface and an abstract class?"

Yes. Yes I can. Can you tell me why you're asking such basic questions? Is this something people actually don't know this late in the game?

We've all experienced something like this. (On a side note, this is why FP > OOP 😜)

So today I saw another 'OOP should die' article.
And I decided I should google around a bit to find out why.

Reasons I found:
- Things get too complicated
- Things get too abstract (same as the above really)

But when I search for alternatives, only functional programming and different ways to use OOP get mentioned.
I still don't get why OOP is supposedly bad though.
Maybe my 20-30k LOC projects aren't big enough to see it?

For me the abstraction works very well. The abstraction is used to keep the complexity low(er).
And the different ways of using OOP are a plus-point for me. (Like the Entity-Component system)

I don't know enough about functional programming to be able to say it's better or worse, but the ideas behind it a perfectly usable in languages like C#.

So if any of you have a good concrete reason to not use OOP, please feel welcome to tell me in the comments :)

My attempt at illustrating OOP 😂

I have a rule made by myself. I call it "550 line".
If a class have more than 500 or a method more than 50 line, something is wrong.
(Is there any better rule? Tell if there is some)

Curious about you devRanters' backgrounds.

I'm 28. Scala Pure FP. Formally Java OOP.

I was fixing an issue where I have encountered a Java class written by a recently hired senior developer with 1K+ lines of code.
Inside that class....
One Method => 1K lines🙄🙄

I don't know where to bang my head now😐😐

Best OOP class ever 😆
"Now you can access your classmates' public data, you know their classes' parts. But you can't touch their private parts (5sec pause) ...of their class. However if you're related, it's okay for you to play with eachothers parts... as long as they're protected. "

does kinda failing oop exam make you a bad programmer?

dev "no no no, you're overengineering it. You just need one class for that"
Me "but ... Those are different object that share a common interface. The internal logic is not the same, only their output is. You know ... That's the purpose of interfaces"
Him "no no, as i said, you don't need that. Listen, you can put ALL the fields and methods in a single class and then you can use a switch with different cases .."

I remember when I first started programming and used to be scared of classes. I was thinking about it after I wrote several today like it was nothing.

We are a web developer team of 4 people. The system we manage is huge because it's a huge organization.

We use php.

Requirements grow rapidly and debugging became a nightmare. So we decided to move from procedural to OOP to ease it a bit.

And we have this one guy in our team (joined recently) who doesn't understand the benefits of following OOP. He is the one who manages most side projects among us too.

We have tried hard to convince him and now we have almost given up.

So I am asking you guys, please give me some ideas of how we could convince him to learn and follow OOP.

What is the object-oriented way to become wealthy?
Inheritance!

pm: next week you have to talk in front of 20 interns

me: oh, sh*t I better get prepared. Googling "principles of OOP"

The worst thing I've seen a developer do would be becoming a university teacher while not being able to understand simple OOP or good programming practices.

I can't think of a most harmful one, just mediocrity cultivating unknowingly mediocre devs.

Correcting basic programming exam, see this part of an answer:

---
for round in all_days:
if round+1 < round:
---

polymorphism is the hookup that wallfucks you hard until you achieve maximum inheritance orgasm

When I was in college OOP was emerging. A lot of the professors were against teaching it as the core. Some younger professors were adamant about it, and also Java fanatics. So after the bell rang, they'd sometimes teach people that wanted to learn it. I stayed after and the professor said that object oriented programming treated things like reality.

My first thought to this was hold up, modeling reality is hard and complicated, why would you want to add that to your programming that's utter madness.

Then he started with a ball example and how some balls in reality are blue, and they can have a bounce action we can express with a method.

My first thought was that this seems a very niche example. It has very little to do with any problems I have yet solved and I felt thinking about it this way would complicate my programs rather than make them simpler.

I looked around the at remnants of my classmates and saw several sitting forward, their eyes lit up and I felt like I was in a cult meeting where the head is trying to make everyone enamored of their personality. Except he wasn't selling himself, he was selling an idea.

I patiently waited it out, wanting there to be something of value in the after the bell lesson. Something I could use to better my own programming ability. It never came.

This same professor would tell us all to read and buy gang of four it would change our lives. It was an expensive hard cover book with a ribbon attached for a bookmark. It was made to look important. I didn't have much money in college but I gave it a shot I bought the book. I remember wrinkling my nose often, reading at it. Feeling like I was still being sold something. But where was the proof. It was all an argument from authority and I didn't think the argument was very good.

I left college thinking the whole thing was silly and would surely go away with time. And then it grew, and grew. It started to be impossible to avoid it. So I'd just use it when I had to and that became more and more often.

I began to doubt myself. Perhaps I was wrong, surely all these people using and loving this paradigm could not be wrong. I took on a 3 year project to dive deep into OOP later in my career. I was already intimately aware of OOP having to have done so much of it. But I caught up on all the latest ideas and practiced them for a the first year. I thought if OOP is so good I should be able to be more productive in years 2 and 3.

It was the most miserable I had ever been as a programmer. Everything took forever to do. There was boilerplate code everywhere. You didn't so much solve problems as stuff abstract ideas that had nothing to do with the problem everywhere and THEN code the actual part of the code that does a task. Even though I was working with an interpreted language they had added a need to compile, for dependency injection. What's next taking the benefit of dynamic typing and forcing typing into it? Oh I see they managed to do that too. At this point why not just use C or C++. It's going to do everything you wanted if you add compiling and typing and do it way faster at run time.

I talked to the client extensively about everything. We both agreed the project was untenable. We moved everything over another 3 years. His business is doing better than ever before now by several metrics. And I can be productive again. My self doubt was over. OOP is a complicated mess that drags down the software industry, little better than snake oil and full of empty promises. Unfortunately it is all some people know.

Now there is a functional movement, a data oriented movement, and things are looking a little brighter. However, no one seems to care for procedural. Functional and procedural are not that different. Functional just tries to put more constraints on the developer. Data oriented is also a lot more sensible, and again pretty close to procedural a lot of the time. It's just odd to me this need to separate from procedural at all. Procedural was very honest. If you're a bad programmer you make bad code. If you're a good programmer you make good code. It seems a lot of this was meant to enforce bad programmers to make good code. I'll tell you what I think though. I think that has never worked. It's just hidden it away in some abstraction and made identifying it harder. Much like the code methodologies themselves do to the code.

Now I'm left with a choice, keep my own business going to work on what I love, shift gears and do what I hate for more money, or pivot careers entirely. I decided after all this to go into data science because what you all are doing to the software industry sickens me. And that's my story. It's one that makes a lot of people defensive or even passive aggressive, to those people I say, try more things. At least then you can be less defensive about your opinion.

Private data

I hate it when (Java) programmers produce such clutter just because their OOP 101 professor told them to do so in 2005.
I refactored it using `git rm`.

Random talk with a colleague:
-How familiar are you with oop concepts?
- I don't need that, I will make my life easier instead. They say "the" Java is faster though.
-Faster from which lang?
- C.
Me: Aw shiet.

Can't believe who I share this precious air with.

I hate OOP. Fuck OOP.

Any tips on nailing OOP design interview questions? This is a black hole, weak area for me, and I get absolutely no feedback on what I'm doing wrong.

I feel like most of it is because I *nothing* about what I'm asked to design.

And yes, I ask clarifying questions, list out use cases and constraints, identify nouns/verbs and map them to objects/methods - but these don't help with the overall *design* when you can't even grasp what the components are, nor which parts need extensibility.

Imagine you've *never* been inside a car, let alone even understand there's components to a car (you don't even know that cars have engines, or that they take fuel). Now imagine you're asked to design a car. It's just, silly.

I was assigned to maintain the website as full stack dev but the code from backend is horrible previous devs didn't use SOLID principle, DRY, KISS, or Design patterns. I had to adjust from OOP mindset to Procedural its hard to debug in this state.

Something that really bothers me about the oop idea of "oop allows better code reuse" is the fact that I have yet to encounter a situation where I need to reuse old code for a new project.

And the code I do want to reuse I've put into a library and made genetic anyway. Something which can easily be done with any language supporting generic programming, object oriented or otherwise.

Every time I come back to Java:
"Oh man OOP is fun"
A few days later...
"This stupidly verbose, hand-holding garbage."

Previously, I use Codecademy to learn code.

Now I learn from my friends. Believe me, they helped understand OOP better.

So, I just started learning OOP(Object-Oriented Programming) and my brain hurts. like I maybe understood 10% of the information I just consumed. Is that a thing? Is OOP hard for people the first time around? Am I just dumb? Hell, it wouldn't be the first time

When the code you wrote 3 months ago is actually reusable else were in your program #OOP

to the guys saying "oop is dumb" / "i don't need oop" / "i've never worked with oop"...

i have some questions:
- which language are you working with
- which problems are you solving
- how big is your code base
- how do you maintain readability of your code?

don't get me wrong, i don't believe that oop is always the answer. i'm just curious which fields these statements are coming from. if they all come from a low level (assembler, C, ..) or functional languages or "scripty" languages (python, JS), or if there are also people working with languages like C++ where oop is pretty much established. and if the latter, i'm curious how people design their code and what problems they solve... tell me your story :D

I JUST SPENT A PAINFUL TWO HOURS TRYING TO FIND OUR WHY MY EXCEPTIONS WERE BEING THROWN AFTER EVERY SINGLE INPUT THE USER ENTERED...

I commented out the try catch, it worked, I commented out the throw and it worked, so I uncommented them both and it worked again? WHY DIDN'T IT WORK BEFORE Y U DO DIS

I bring you all another gem from my computer science course, this time from my OOP class.

The first assignment we made for this class was a simple CLI shop, where you would have basically three main classes:

- A Product class that you extend to create different types of products.
- A Cart class that manages a list of products (basically an ArrayList<Product>) and has some useful methods
- A CLI class to display a simple interface to the user and call methods on a Cart.

Basic OOP stuff, so far so good.

Then for our second assignment the teacher asked us to make Cart a generic class, where you would say Cart<Bagel> and you would only be able to put bagels in it. This makes absolutely no fucking sense, this is not a good use case for generic types since

1) you would never limit your customer's cart to one type of product at compile time.
2) in Cart, you have to cast the generic type to Product to extract any information from the product, like when getting product prices to calculate the total price, so might as well use a fucking ArrayList<Product>

I'm just saying what he's asking us to do has (to our fictional shop's business logic) absolutely no advantage over subtyping.

Also, why the fuck teach generic constraints when you can just tell your students "just cast T to Product", right?

Like fucking hell, couldn't you spend like 10min to come up with a decent assignment that actually teaches generic types the right way? ffs

And just so no one can say "but wut simple assignment would you give to teach students generic types?", here's a simple and much, much better alternative: implementing your own ArrayList. Done. Can't get much better than that, it's a legit use case and teaches you the basics.

Sorry man, you're a great person, you really are, but you suck as a teacher.

this is my legacy code, it's stupid, Change my mind.

a large number of lecturer and friends are against my thought. personally, i think this kind of code is told to be an OOP yet this is against the OOP concept. why ? first you assign the field to be private, but you implement Getter and Setter method later on, this is the same if you assign the field to be public in the first place.

another minor thing; yes this is old me, i use Bahasa Indonesia as a variable name.

"What are the four pillars of OOP?"

Me:(I'm not an OOP guy, but focused on design patterns)

1. Encapsulation
2. Abstraction
3. Polymorphism
4. ??(was it inheritance or composition).

Fuck, Because of the phrase "composition over inheritance". I've been mixing both composition and inheritance at the same time.

FP > OOP
I wish the enterprise world starts learning this!

As an "OOP Programmer" you have one job to do:

Kill all the if statements.

Sometimes with fire.

When you ask a bunch of C programmers to make an application in Java you get a main function that is 1,125 lines long because who needs OOP anyways? amirite?

Student dev : "C++ is C but with OOP features"
Teacher dev : "C++ is a OOP language, you'll loose points if you don't use OOP"
Me: "Time to leave this school"

"thir" will be the new gender-inclusive form of "this".
Example:
thir.printPronouns();

JavaScripts idea of OOP is nothing like anything else and misses halve the functionality.

My professor asked me today why I wanted to build my project using OOP.

This is a 480 level course and I have 2 1/2 years experience building well over 30 projects with OOP. And yes, we have students here who are nervous about the idea of using OOP. Nevermind that I and others took two classes on the topic.

I have hit my dispair event horizon. It has to get better from here. 🤯😬🤬🤬🤮☠️

When you're diving deep in OOP PHP but at University you're learning how to getElementById... Fml

That moment when you automated the application so much, working on it get's actually kinda boring 🙈😂

I just leave it there.

public enum FileType {
True, False
}

Just because OO exists, it's not mandatory.

Some code would be 10(+) times simpler, more readable and more maintainable without it.

Taught myself assembler at 13 (this was the mid 1980s) and wondered how the hell people could stand to do this. Then I found out there were more abstract languages like BASIC or COBOL. So I taught myself BASIC and MS-DOS batch scripting. Various other languages came later (PROLOG, Pascal, C, Smalltalk, C++, VisualBasic, etc). But it’s never been easy for me because I suck at math and complicated logic structures. Especially not good with OOP. My brain was ruined by learning procedural coding first. It refuses to incorporate OOP.

Forcing to use OOP on golang is like use basketball shoes on the right foot and ballerina shoes on the left foot
Ugly

Don't be specific on any programming languages, focus more on OOP approach, and say you know about OOD/A rather than, you know Java, C# and this and that.

Keep it simple, stupid!

I like building large apps in flat php.

I get bullied for not using OOP / Frameworks.

I don't like this.

Dear Java developers who has a fetishes with OOP and Design Patterns, and are now using Python:

Not every fucking thing you build has to be a class, a singleton or a factory. Specially in Python. Go with your boredom and boilerplate elsewhere.

Why is OOP hated, here?

How is functional programming much better than OOP? (as stated by so many peole here)

Stop. Using. Fucking. ADA. To. Teach. Basic. Programming.

I wouldn't say you should use a dynamically typed language like Python, but having programed since high school, I hated each and every aspect of Ada. We were even taught OOP and generics with it! (And not, you do not want to know how it is, because it is dreadful)

Oop for beginners

Project manager pictured with team after deciding to refactor their project from OOP to FP

Functional programming literally has 'fun' in the title. OOP is one letter away from 💩

Coming from Java, I am slowly loving the MVC OOP PHP.

"Do you know OOP in Java?"
"No, I don't."
"How about POJO?"
"I dunno too."
"Okay, so what do you know?"
"Pascal."
"Then why do you call yourself a Java programmer, dude?"
"Cuz, I'm a programmer, and I'am a Javanese."
"Oh..."

When I was taking a programming course as a Mathematics prerequisite, and then object oriented programming basics (inheritence, interfaces specifically) all just clicked at once. Immediately decided I was going to pursue the computer science major instead of math.

The object-oriented model makes it easy to build up programs by accretion. What this often means, in practice, is that it provides a structured way to write spaghetti code.
~Paul Graham

I just love PHP. You can do so much awesome stuff with it. Here, let me show you:

How to READ a private member of an object:
$reader = \Closure::bind(function ($instance, $name) {
return $instance->{$name};
}, null, $instance);
$value = $reader($instance, $name);

How to WRITE a private member of an object:
$writer = \Closure::bind(function ($instance, $name, $value) {
$instance->{$name} = $value;
}, null, $instance);
$writer($instance, $name, $value);

See? Just like that. This is really amazing stuff. I don't know of any other languages that allow this.

Just been cleaning out an old cupboard and found the book that really helped me to understand OOP ... Python for absolute beginners .. Before I picked it up, I was having a hard time getting my head around it all. Good times, good book :)

Some alabama shi+ going on in here...

New folks, learn functional programming. Avoid the stupid pain with OOP and mutability. Pays off a lot and for ffs, increase your salary demand, don't lowball, so everyone can enjoy higher pay.

HR: What is Java?
Me: Ah... OOP... uhm... is a programming language... *awkward silence*... Yep, that's all
HR: Congrats, you have bombed the interview

Source: Me from few days ago ._.

Trying out pure functional programming in javascript. First few weeks: wow, this is so fresh, oop can die, etc. Now: this isn't readable at all! 😐

That feeling when you think your workflow is bad and happens to see"Professional" Degree level team of coders writing crap code with even crappier workflow

Who the fuck invented the glorified pile of shit people call laravel? Is this actually used in PROD for anything else than load testing a monitoring server by creating loads of error messages?
OOP exists for a reason, not to create bazillions of classes with static methods.
Dump that shit ffs!

When OOP backfires

So i've been working with OOP and now that i have some free time i decided to learn Golang.... Great language but at the beginning was really hard to go back to the non OOP.

thinking about getting a laracasts subscribtion, is it worth it at all? I've recently been working with PHP a lot, and my OOP skills are pretty narrow tbh, I wanted to learn more OOP and laravel, because there are a lot of job's that require you laravel knowledge.

So I've been programming for a while now in various languages like C#, JavaScript, etc. I have never understood how to do OOP until I watched the MVA videos on Microsoft's website and I have to say, its made me love C# more and made things so much easier to understand!

I'm already thinking about rewriting my personal projects from scratch lol.

I have lately seen a lot of people mentioning that functional programming is better than object oriented programming.

So far I have only experience in oop and I would really like to know some reasons why it is better.

I've been writing various forms of OOP for three years and just now learned exactly what static means

That's how I learned OOP in Java at University 😎😅

Just got an internship a few days ago. The manager threw a project at me. I have to do it alone. It's a user-system (registration, login etc.) The front-end is ready. And I have to build its back-end in PHP. I started to draw the project on paper (pseudocode) and then asked a few questions about design patterns to jump into coding. They recommended me Laravel. I'm good at PHP (procedural) and have done some basic OOP. I've actually built a few projects in Python using OOP. But I've never used any framework (yeah, I know). So I started to learn Laravel and realized that it's very different than normal PHP (procedural or even normal OOP). I almost don't write any normal PHP code. This makes me confused. But I have to learn it fast and well, and finish the project to hit the deadline and get the full-time job. I'm desperately looking for any kind of help to learn Laravel more effectively! I've googled and got some recommendations. But I need more live help from devs directly.

Went shopping with my girlfriend the other day and saw one of the sizes was OOP

I immediately asked out loud: “Object Oriented Programming?”

I dont understand why we must use PHP to
understand OOP

Im a student software developer and this is the first time i will learn about Object Oriented programming but i dont know man im really confused why our prof makes us use PHP to understand the concept of OOP rather than to learn Python or Java which is ten times easier for an OOP based application

I can understand that PHP can be used for OOP but why just why... can someone please explain why this might be and how does it feel to use PHP for OOP purpouses

People who are too cool for old-and-busted OOP, but want to build microservices: networks of independent, encapsulated systems that look after their own data and communicate by passing messages.

Yup, that's totally not OOP you're doing there, kiddo.

OOP things...

Java rant...

If public field declaration is so so bad, why can't all class fields in java just be private by default? And make it a pain in the ass to expose it as public?

I can't actually remember a time declared a class field as public, it is muscle memory now... Private bla Bla Bla, return, private bla Bla, return...

So I'm at this gaming event to enter in a small game I have been working on with fellow teammates. As an OOP, does anyone find the following conversation hmmm, odd?

Guy: I program for Microsoft!
Me: That's great! What's your favorite syntax?
Guy: I don't want to get into that? Me(inMyHead): 🙄😂😂😂👍🏾

What do you think about class-based OOP vs. Prototype-based OOP?
I think that class-based OOP is an unnecessary abstraction of structs, functions and global variables most of the time.

A sweaty furry sodomizing a dead dog would still be less disgusting than the codebase on which I have to work, some highlights are:
- The same class repeated 40 times with little variations instead of using some decent parametrization
- Inexistent encapsulation and separation of concerns, most changes requires to modify and recompile 2-3 indipendent Maven projects
- Abuse of inheritance which instead of being used to create "is-a" relationship as it should be it's used to reuse some methods of a class in another instead of using Spring dependency injection as we should be

It would be understandable in a 20 years old legacy projects but in something which started 2 months ago it drives me mad, I tried to fight to change it but in the big enterprise to which I'm "body-rented" it's impossible

People might like it. People might love it. People might wanna kiss it. People might wanna share bed with it.

But I just don't feel it.

Python ecosystem drives me nuts!

Not the language tho, i kinda like it, and some features are damn straight awesome.

But ecosystem... man!

The way ppl write code in it, the lack of documentation (or in quality of it)...

I recently wanted to check how library does one thing (debug purposes), and not only i had to track some method up 3 classes, the other method i hunted only by signature and still i have no idea how it ends up being accessible where it should...

"Explicit is better than implicit" my ass...

Also dev managed to make the code very unreadable. In Python. Language with such strong opinions about code formatting. HOW ?!!

And the worst part is, it wasn't that big of a library and didn't really need the full freaking Enterprise OOP treatment with layers over layers of generally named classes and fucked up architecture.

FUCK THAT LIB, FUCK THAT DEV, FUCK IT ALL !!!

PS.
Project seems to be abandoned for a year or two, so there is hardly an option to fix things with the author sadly :(

What's the OOP way to get rich quickly? Inheritance.

The worst thing about Java is, that it created a generation of coders, that think OOP is the opposite of FP.

deal with oop.

because they made it waaaaay more complicated than it needs to be.

the company I work for has code that's very procedural which makes cringe as I strongly prefer object oriented.

we have 4 options when come to Windows 10 development
+ Windows 32 API
+ WPF
+ WinForm
+ UWP
the best performance would be Windows 32 API but really painful when maintaining
but game like League Of Legends have complex logic still accomplish so I think they also create their own OOP pattern

Keep your life and code "low in coupling and high in cohesion" 🙌😋

Opinions about this book??
It just arrived today.

So I applied to a Java internship, I'm an absolute newbie in coding, they invited me to an interview and we're gonna have an assessment exercise regarding Java and OOP in general, any one have a Java or OOP one weekend crash course? Thx!

I kind of don’t like OOP. There I said it.
Don’t get me wrong there are times I like using it. I don’t mind some of the features but I can rarely find times I want to use them.

It can be useful depending on the project but I mostly don’t use it and when I’m using Python I always feel like I have to? I know Python offers multiple types paradigms of programming to use but everyone’s making a big deal about OOP and I can rarely ever find uses for it. What I said for Python also goes for C++ I feel like I’m forced to do it. And I especially hate it in C++ fuck that.

I’d just like to use Python, and C++ without using it or if I do not have to use all the fancy features. And kinda wish Java and C# didn’t force OOP on you but I just don’t use all the fancy features in those languages (I don’t even use java but I’m mostly talking about C# for that one).

It’s not that I don’t know how to use it it’s that I can never find a use for any of the features or just don’t want to actually do it. Personally I only really see it shining in Game development, GUI development, and MAYBE network programming??

By all means I’m not trying to flame on OOP, I just wanted to throw my OOPinion (HA) on the matter. in fact you can tell me why you like it or dislike it. I’d like to discuss the topic with anyone.

I've always sucked at OOP and OOD, _in part_ because I have never encountered a good, common sense, relatable real-world example or analogy of why one would use protected or private variables/objects/functions over public. I watch tutorials and it all just sounds like static in my head and the explanations are just like "well, it's obvious you want to do blah blah blah because reasons."

Maybe it's just painfully obvious to everyone but me and my tiny brain just isn't capable of understanding. But if anyone has the example or analogy that made OOP click for you, please share.

Been wanting to get into OOP and unit testing, haven't found a single semi big project that I can use to study these techniques...

Wrote myself a class when asked to do an API call last week, and I think it looks pretty decent...

Does anyone have a ressource to just see how to do it "properly" on medium sized projects? (100k loc)

I realized only now that OOP is POO when read backwards. I wonder if this is a secret message encoded by somebody to make us all switch to functional programming

Hello developers!!
I just wanted to know from where I can learn OOP skills from scratch? Suggest me some good tutorials available on YT ;-;

I came from a procedural background, then adopted object-oriented programming, and now I am very enthusiastic about functional programming. Is this kind of an evolutionary path as a programmer? Or am I just late to the party?

And what paradigm follows?

OOP ze daisy

In React, OOP is now the old way of approaching react.js everybody doing functional programming/functional components.. this that the future ???

In interviews, I tend to forget the basics while I can answer more advanced questions. For example, I can't for the life of me remember the four principles of OOP but I can talk about garbage collection in my main programming language.

Hehehehe

Programming Paradigm Convergence.

I can already see it in JS and C#. Both have functional/OO aspects and keep growing more similar in terms of language features.

I'd rather see OOP die a fast and horrible death though 🤷‍♂️

I remember my college days, i had a subject about OOP. Damn, the professor only talked about how to make a f*cking TextBox and Buttons in VB.NET and we finished the course without hearing anything about OOP.

OOP coder:
OOP is so useful and realistic!
Let me give you an example -> Cat extends Animal.

Every other coder:
So how is that useful in reality?

OOP coder:
...cat pictures?

Any recommendation of a free book for learning c#? Already know about OOP with java.

in my OOP class the prof spent most of the time telling us OOP is dying, but we have to learn it anyway.

When I started branching out from frontend development and took an Intro to OOP course. I still do web, but getting more into the giant world of programming was really inspiring!

Im looking to check out a new language, any recommendations?
P.S: I'm sick of OOP.

Typescript is a PIECE OF SHIT that adds 3 problems for every 1 it solves! Messing with so much shit from its linter and builder just so some OOP fools can code JS like *TAB* *TAB* *TAB* again!

All u need is C folks seriously fuck the OOP concept you waste more time in a paradigm dilemmas than writing functional code. And that’s a damn fact.

I feel sorry for the mobile developers that are stuck using the OOP methodology

node devs are the dev-world equivalent of the 12-year old in a crew cut who really thinks your shoes are dorky.

there was a oop question on reddit/node that had 1000 "ew/cringe" replies before anyone said "nice class"

Java is truly an OOP language... As in; OOPs, I used Java! 😛

Sometimes OOP feels like this:

How do you do java style oop with classes and inheritance and all that in c++?
Do I really have to make a header and a source file for each class?

And while we are on it: are there any sources of "famous" games written in cpp?

this.is = (bool)shit;

!rant
I finally published my first open source project. A package for calculation a geohash of a geolocation for pharo smalltalk.
I know that most of the users don't know smalltalk but it's the best OOP you can code with. And geohash is such a great algorithm. Lovely combination

a guy that i had to work with. He was a senior developer and asked me for helo in python. First i had to explain to him how to use OOP and when he couldnt implement my solution he blamed me for his slow progress... serval times

Hey devRant! Long time no see
I recently landed a job as a java developer so that's amazing
Still getting my head around the company's codebase, and holy fuck its huge.
I was taught best oop practices and patterns in CS class, but seeing them implemented in such a huge project is kinda pisssing me off: every single thing in the code has dozens of classes that call and implement each other, I spend half my time spamming the "open declaration" shortcut in a futile attempt to understand how the pieces fit together.
Sometimes I wish they had stuck to implementing everything in a handful of files, instead of the jungle of nested packages and references I got :pensive:
Oh well at least most thing are documented :shrug:
I kinda get y some people despise java for being so verbose and forcing strict pop on the programmer XD

Six different .NET solutions using reflection to interface with each other just made OOP look a lot like spaghetti code.