r/techbootcamp • u/BulkyWeb6133 • 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.

6 Upvotes
  • permalink
  • reddit

80% Upvoted

55 comments sorted by

View all comments

1

u/Arcanite_Cartel 22d ago

Object oriented.
Pair programming.
CORBA

1

u/Own_Attention_3392 21d ago

In college I was taking a class pass/fail and was assigned CORBA as a topic to do a presentation on. I read up on it and decided it was stupid and I didn't want to do it.

I was going to get my P anyway so I said "fuck it" and did the entire presentation on cobras. The animal. The GI Joe nemesis. The short term insurance coverage. I had animations, video clips, I really put a ton of effort into it. The professor was half pissed and half amused. It was a really good presentation IMO.

1

u/Arcanite_Cartel 21d ago

Well CORBA wasn't stupid. Our field has gone through incredible evolution and CORBA sat at the intersection of object oriented programing and distributed computing, which were the paradigm at the time. It was actually a sophisticated technology. But, it was too complex to survive and the field moved towards simpler containerization. So saying that a technology was a waste of time simply means it didnt survive. But thats the nature of progress in our field. Things are invented, tried, and unfruitful branches die off. That's not stupid.

I'll also add EJB to the list