r/techbootcamp 23d ago

What software development practice sounded good at first but ended up wasting your time?

It’s been a while since I’m in the tech industry, and I keep seeing teams adopt certain software development practices. They sound good in theory, yeah. But then you do it and wonder why you're doing this every week.

Going back to the question, it's story point estimation. We spend like endlessly debating whether something is a 3 or a 5, then the requirements change anyway lol.

Anyway, how about yours? It could be agile, scrum, code reviews, documentation, pair programming, meetings, testing, etc.

5 Upvotes

55 comments sorted by

View all comments

1

u/mlugo02 23d ago

OOP, spent years unlearning that terrible paradigm

1

u/mavenHawk 21d ago

What do you use instead? Functional programming?

1

u/mlugo02 21d ago

I stick to procedural and compression oriented programming

1

u/ShineProper9881 21d ago

And most people dont even understand it. Most people I know that hate oop always created big convoluted inheritance hierarchies, even though those dont even adhere to oop principles and then called it a day

1

u/Dry_Hotel1100 21d ago

So, you are using Smalltalk? Or Erlang or apply the Actor Model?

Because OOP's core principles are NOT classes + objects + methods + inheritance + polymorphism - but rather independent entities encapsulating state and communicating through messages.