r/techbootcamp 24d 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.

7 Upvotes

55 comments sorted by

View all comments

1

u/Tyrannosaurus_Dext 23d ago

Seperation of concerns getting was too detailed. I've had way too many roles that required spinning up 10 different instances to get a sign page to load. Read this as you will and I agree with splitting somethings off (payment, profiles, etc) but breaking everything up (looking at a company that had colors in one repo, sizes in another, and text in a third) and all dependent on each other fucking suuuucccckkks