• idriss@lemmy.ml
        2·
        2 months 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
          5·
          2 months ago

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

          • Cityshrimp@lemmy.world
            6·
            2 months 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
              4·
              2 months 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.

            • eldavi@lemmy.mlEnglish
              1·
              1 month ago

              My newest one is as impulsive as I am so the digressions he tasks me with have stalled out long term development plans, yet he’s oblivious enough of the situation to seriously ask why progress is taking so long every year during reviews.

  • moseschrute@lemmy.world
    4·
    2 months ago

    I know this is probably a joke, but they must be doing this. Even if the AI isn’t making this discussion, they must be trying to separate good engineers from AI bros that only ever knew how to vibe code.