• MisterFrog@lemmy.world
    link
    fedilink
    arrow-up
    40
    arrow-down
    1
    ·
    edit-2
    5 months ago

    Problems caught early are much easier to fix than problems caught later. This applies to any project (I’m not a programmer, but an engineer in the traditional sense).

    Just “doing it” without coordination and review is a great way to waste a bunch of effort down the line with re-work.

    Edit: typo

    • Tryptaminev@lemm.ee
      link
      fedilink
      arrow-up
      8
      ·
      5 months ago

      While i agree with the principal statement, this also requires two things to work:

      First: The scope should be defined properly, so people can contextualize what they are actually doing and reviewing.

      Second: If the scope is subject to change, or parts of it are unclear, there needs to be room to consider, develop and try different variants

      This is were good management is crucial, which includes giving breathing room at the start. What we tend to experience is the expectation of already good detailed results, that can be finalized but still work if things change significantly.