393
The Great Software Quality Collapse: How We Normalized Catastrophe (techtrenches.substack.com)
submitted 1 year ago by to c/technology@lemmy.world
134 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 5 points 1 year ago (1 child)

Yeah what I hate that agile way of dealing with things. Business wants prototypes ASAP but if one is actually deemed useful, you have no budget to productisize it which means that if you don't want to take all the blame for a crappy app, you have to invest heavily in all of the prototypes. Prototypes who are called next gen project, but gets cancelled nine times out of ten 🤷🏻‍♀️. Make it make sense.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 5 points 1 year ago

    This. Prototypes should never be taken as the basis of a product, that's why you make them. To make mistakes in a cheap, discardible format, so that you don't make these mistake when making the actual product. I can't remember a single time though that this was what actually happened.

    They just label the prototype an MVP and suddenly it's the basis of a new 20 year run time project.

    In my current job, they keep switching around everything all the time. Got a new product, super urgent, super high-profile, highest priority, crunch time to get it out in time, and two weeks before launch it gets cancelled without further information. Because we are agile.

  • permalink
  • fedilink
  • source
  • parent