• MangoCats@feddit.itEnglish
        0·
        55 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
        0·
        13 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.mlEnglish
          0·
          3 hours ago

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

          • Cityshrimp@lemmy.world
            0·
            44 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

            • Kjell@lemmy.world
              0·
              32 minutes ago

              And there is never time to maintain the code, because each project only want to add more feature/s which makes the spaghetti code even worse.

              In my group we had a golden opportunity to fix all old mistakes but no, we (decided by PO and group manager) needed to spend all time on proof of concepts that will go to production at earliest in 5 years. Now that opportunity is gone and we are crunching in order to meet the deadlines instead. Still with bad code quality of course.