• MangoCats@feddit.it
        link
        fedilink
        English
        arrow-up
        1
        ·
        19 minutes ago

        Every time I look back at old stuff, I have to remind myself of the relative importance of getting it done, vs getting it perfect, at the time.

        Inevitably, there were no clear requirements at the outset, or if there were they were vastly outnumbered by additional requirements that scope-crept their way into the project. The project was “due” before I was asked to help / landed with the whole thing to do myself. The project was under-estimated and is now “on the critical path” for a larger initiative. Other interested parties are too busy to meet during definition time, but all too willing to point out missing scope after a “finished solution” is presented.

        Yeah, me from the past… not a fair reflection.

      • idriss@lemmy.ml
        link
        fedilink
        arrow-up
        2
        ·
        12 hours ago

        Progressing is cool, but having 10 yoe and still outputing spaghetti is bad. I am just saying if you care enough about what you are doing you are top 10% already

        • eldavi@lemmy.ml
          link
          fedilink
          English
          arrow-up
          2
          ·
          3 hours ago

          the quality of the code is dependent on the quality of the pay. lol

          • Cityshrimp@lemmy.world
            link
            fedilink
            arrow-up
            2
            ·
            9 minutes ago

            And as others have noted, how much time you are actually given. PMs and managers don’t know or care about code quality, they just want something to work NOW