Why did you put 80+ properties for a single class? What’s the point? Why?

Because fuck you, thats why.

"Who cares, it works"

@irene That's an example of my single biggest pet peeve during my studies. We would get these tiny artificial problems so of course you would just write a public static void main with your 30 lines of logic, only to be reprimanded about solid and best practices.

The only strict, no-compromise rule I follow is "It Depends (tm)".

It depends!

@irene @ltlian this isn’t oop, this is shit

@irene Oh it sounds like one of my very first C++ projects after I discovered QT but was lost in QT creator haha

It worked with main window class beeing.. around a fuckton of methods. And it only contained MainWindow class and some popup's classes ;-;

But it worked, so here is that...

After single page application, there is now single class application. Whole new future is arising

@veakey

Next step is single method application ;)

@DubbaThony time for me to be a baker, no shit design anymore

@theKarlisK single line application ? What about python?

Okay, nobod.. eghm...
Ermm..
I don't like and care about python

80 seems a little excessive, but maybe they felt the class was lonely and underused so needed some more positive attributes?

I've seen something similar, and it wasn't the worst part of the project.

That happens when you don't know arrays bruh

Currently working on a project that have 150+ columns in several tables :/ my models starts being chubby

@Lyniven I don’t even know which properties goes into which context, ffffaaaakkk this

@devTea Be careful and talk quietly. It might be Skynet. Also, if it is Skynet save humanity by adding Asimov's laws and Wheaton's law to the constructor.

@irene Did you write our legacy apps? I hate you.

@ltlian https://youtu.be/GtujUCURgtM

@DubbaThony "why not just simply wrap everything in the main function?"

@irene didn't APL have the first code golf contests?

PlayerController for a game

@Krokoklemme

And if any functions used, make sure these are inline functions (its feature of c or cpp i dont rly remember) that way you make sure it ends up as truly one function heh

@irene yeah, but the king. Maybe they are king and queen?

@irene you're king of online arguments ;-) (perl though, I dread this project that's awaiting us using it. Even after some thousand lines of bashisms and an awkward JS encounter I'm still intimidated.. Don't understand how it could have been elected to teach programming to my wife.)

Power user features

Some people run around all day carrying hammers.

And everything looks like a nail.

My favorite is when some near-do-well creates a single base class, or interface, when theres only two classes that implement it "just in case."

Motherfucker, save that for the REFACTOR when the code has 7-10 classes with something in common WORTH factoring down into a class, interface, or other ilk. I don't want to sift through someones fifty pages of doxygen bullshit interfaces and base classes where 50% of the classes are base classes that do nothing just so I can figure out what every other fucking class I'm using actually does.