• Ah, ok not too dissimilar.

    Its either items of work that doesn't meet spec or assurance documentation that is not complete and you need to get sorted out before close-out (and final payment).

  • I sometimes use construction metaphors to explain technical debt in the software engineering context. "You put a wonky stepladder in the place where the stairs should go, but now the deadline for completing the upper floor work is so tight that it's in constant use, and while it's slowing all that work down, nobody will let you pause things to put the stairs in." Much of the software that goes to market is wonky stepladders all the way down.

  • Much of the software that goes to market is wonky stepladders all the way down.

    Placed upside-down

  • What is the solution to this? Good architecture from the outset? Being honest about the true cost? Shooting anyone who uses mvp?

About

Avatar for itsbruce @itsbruce started