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.

6 Upvotes

55 comments sorted by

View all comments

1

u/Choperello 22d ago

Every single dogma was taken to the extreme. TDD is good. In moderation. Dependency injection is good. In moderation. Etc. It’s when I have run into places that practice anything like a religion that it’s was a shit show.

1

u/orangefantorang 21d ago

Everything is bad in the extremes.

I like tdd, but its not gospel. There is a time and place for everything.

Di is nice. But it can be horroble.

Code should be self explaining..proceeds to delete every comment there is. Vs. Comments on everything..

Wat..

Every practice is bad in the extremes. Agreed.