this post was submitted on 05 Jun 2024
405 points (94.3% liked)

Programming

17313 readers
591 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]



founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 43 points 5 months ago (2 children)
  1. Hack together a proof of concept
  2. Works well enough that management slaps a “done” sticker on it
  3. Pile of hacks becomes load bearing
  4. One or two dependencies change, the whole thing falls over
  5. Set evenings and weekends on fire to fix it
  6. Management brags about moving fast and breaking things, engineers quit and become cabbage farmers and woodworkers
  7. New graduates are hired, GOTO 1
[–] [email protected] 9 points 5 months ago* (last edited 5 months ago) (2 children)

If 2 and 3 happen the game is up. Management killed it.

That's not agiles fault.

[–] [email protected] 5 points 5 months ago

Surely you're not gonna blame the manager.... /s

[–] [email protected] 1 points 5 months ago

But that’s what agile sounds like to management. They don’t understand the “it’s held together by hopes and dreams” communication, because all they see is something that appears to work. So why would they invest anything else in it.

[–] [email protected] 6 points 5 months ago

This is the most accurate description of anything that's ever been written.