268% higher failure rates for Agile software projects
www.theregister.com
In praise of knowing the requirements before you start cranking out code
  • Aurenkin@sh.itjust.works
    0·
    6 months ago

    Would you rather have working software or a bunch of documentation? If your software is having outages then by definition it is not working. If documentation is the root cause of that then you should fix that by creating enough documentation to allow your software to continue to work per “working software over comprehensive documentation”. Maybe I’m missing something but I don’t see the contradiction here.

    • becausechemistry@lemm.ee
      1·
      6 months ago
      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