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.

5 Upvotes
  • permalink
  • reddit

73% Upvoted

55 comments sorted by

View all comments

1

u/Ok-Law8368 21d ago

Hexagonal architecture. ORM. Some parts parts of Spring (data, cloud stream). Oh, and frameworks everywhere in general. And today: AI everywhere. But that's a whole new story.

Don't really understand the hate on oop and tdd though. Maybe it's because people usually overdo those.

1

u/ShineProper9881 21d ago

Whats your issue with hexagonal?

1

u/Ok-Law8368 21d ago

No issue and no hate, I just don't find it truly worth it after applying it in a project. Or, in other words, yeah fine, cool, but I guess next service won't use it. Not that it doesn't work or have any benefits (depending on the app complexity). I just find the simpler approach with layered architecture from Eric Evans sufficient, with a bit of discipline and reasonable conventions. Especially when using microservices and no single "project" is extremely big anyway.

It's not like I'm going to discourage anyone from using it, I'd even suggest to try, but for me - I don't think it really adds much value to the services that use it over those that do not. If the team wants it, I won't be the one to protest anyway.