this post was submitted on 18 Nov 2024
194 points (78.9% liked)

Memes

45712 readers
977 users here now

Rules:

  1. Be civil and nice.
  2. Try not to excessively repost, as a rule of thumb, wait at least 2 months to do it if you have to.

founded 5 years ago
MODERATORS
194
submitted 4 days ago* (last edited 4 days ago) by trespasser69@lemmy.world to c/memes@lemmy.ml
 

Check out my new community: !tech_memes@lemmy.world

you are viewing a single comment's thread
view the rest of the comments
[–] _pi@lemmy.ml 1 points 3 days ago* (last edited 3 days ago)

SDLC can be made to be inefficient to maximize billable hours, but that doesn't mean the software is inherently badly architected. It could just have a lot of unnecessary boilerplate that you could optimize out, but it's soooooo hard to get tech debt prioritized on the road map.

Killing you own velocity can be done intelligently, it's just that most teams aren't killing their own velocity because they're competent, they're doing it because they're incompetent.

And note this is one instance of task, imagine a team of people all using your code to do the task, and you get a quicker ROI or you can multiply dev time by people

In practice, is only quicker ROI if your maintenance plan is nonexistent.