• nilclass
    link
    fedilink
    arrow-up
    10
    ·
    11 months ago

    That sounds super familiar :D

    Anyway, a prototype is not a bad thing, if the managers know the difference. It’s easier said than done to “do it right the first time” if you don’t know how / what to build. Prototypes can be built to validate hypotheses and generally figure out what works, then build the real thing afterwards.

    • tatterdemalion@programming.dev
      link
      fedilink
      arrow-up
      9
      ·
      edit-2
      11 months ago

      Yea I should have clarified. Prototypes are a great idea. The problem occurs when you say, “this is good enough we can improve on it as we go.” Yea good luck balancing priorities when everything breaks from tapping your keyboard too hard. You MUST NOT MERGE the prototype.