• aluminiumsandworm@kbin.social
        link
        fedilink
        arrow-up
        11
        ·
        edit-2
        1 year ago

        oh, no, it’s far worse than that. the last 90% is enough time to make what you thought was the first 90% become 10%.

        so 0.9*expected time = 0.1* actual time

        which, if you can do some very basic algebra, results in 900%. this implies that every project will seem “almost done” for about 9x the length of time you thought the project would take. in my experience, this is roughly correct

        • Johanno@feddit.de
          link
          fedilink
          arrow-up
          5
          ·
          1 year ago

          As someone who has been working on a “almost done” Task for 2 years I can confirm.

    • aksdb@feddit.de
      link
      fedilink
      arrow-up
      6
      ·
      1 year ago

      I also heard (and used) it as a mix of both: “the last 20% take as long as the first 80%”

  • KSP Atlas@sopuli.xyz
    link
    fedilink
    arrow-up
    14
    ·
    1 year ago

    I mean, it makes sense, 90% of the code is probably relatively easy while the 10% is intricate

    • henfredemars@infosec.pub
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 year ago

      Embedded dev: basic OS functions not so bad.

      Task switcher and interrupt code, short but painfully difficult to write correctly.