this post was submitted on 17 Aug 2023
819 points (98.5% liked)

Programmer Humor

32508 readers
666 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] lukas@lemmy.haigner.me 15 points 1 year ago* (last edited 1 year ago) (1 children)

Yet the solution is so simple. Let the them spend 20 – 35 % of their paid time on backlog. Let them refactor the architecture. Let them improve the code base. You know, that thing the Lean book talks about, the part that everyone overlooks, the part so critical yet so often overlooked that others wrote books that ride that one aspect home. Oh, unless you want them to spend overtime on a production problem whose root cause a scrum master added to the backlog 5 years prior to the incident, of course. Oh, unless you want them to give you one year estimates for changes as simple as translation changes 'cause the architecture is so ass-backwards and never improved upon that everything depends on everything and everything breaks with one simple change. And who needs tests, right? Waste of time and money! Just live in fear that one change can break the entire software, like a real man.

[–] Prox@lemmy.world 9 points 1 year ago

Backlog isn't sexy. Management wants sexy. Nobody's boss wants to hear about how the DB schema was improved - they want to see some new, flashy widget.

And the whole product line suffers because of it.