Quote:
Thats ok, stand up meetings are gay, design patterns are for ******s, libraries are for pussies
I actually agree with some of this to a degree.
Use standups where they make sense - not just because the scrum handbook says so.
Use patterns where they make sense - not just because they exist.
Using libraries ties you to those libraries (which can lead to support nightmares) - so use them when they add value not just because they give you that one thing you really like
But going the other way and never using any of those is a sure fire way to create a team that is coding for the garbage can.
Quote:
TIL there is just "OOP" and "spaghetti code"
Nowadays there's also aspect oriented programming.
Use what's best for the task. If you're just coding an internal tool that will do one thing (and which will not jeopardize the project if it is no longer maintained) then spaghetti code is perfectly fine for, say, 50 lines of code or less.
But as soon as you get what OOP brings you you'll never be going back - even in smallish projects you code for yourself at home. What you spend in thinking about in design you vastly more than make up in debugging/maintenance time.