• Scrubbles@poptalk.scrubbles.techEnglish
      29·
      un anno fa

      I just had a Jr dev do this to me. Came in, so bold, and said our patterns were stupid. Told him no, while there are things to improve it’s not worth the effort to rewrite hundreds of classes over a personal preference.

      Of course when he inevitably brought it up again, I told him okay, schedule with our architect, that’s how things work after all for major rewrites. Man, was that meeting entertaining.

      Kids, we know it could be better. But we also know things like level of effort and value. Your CS330 patterns are really cool, we know them too. But we aren’t going to build them.

        • Scrubbles@poptalk.scrubbles.techEnglish
          22·
          un anno fa

          Oh god this was a trigger. Had one guy just casually demand that we change our middleware layers out because it would be “more performant”. Our middleware that was rock solid, never had any issues, and no one ever noticed. He brought up how it would shave so much time, like maybe a ms or 2 when I read through what he proposed. Sure, let’s just throw out what’s been working for years without issue for a new, untested version that will take weeks to dev and test for a payout of 2 ms per request.

  • mr_tyler_durden@lemmy.worldEnglish
    11·
    un anno fa

    Dealing with this now at work. Got a dev whose time in the industry should make him a senior dev but he gives off massive junior vibes.

    • The need to change everything he touches

    • Wanting to write clever code over straightforward code

    • Everything “needs” a refactor

    • Just deprecates things when he doesn’t want to learn them and writes a new implementation without updating old code

    • Thinks he knows best while not understanding huge swaths of the codebase

    • Everything he can’t understand in <5 min is stupid and wrong

    If he was less competent (when kept in a box and closely monitored) I’d be pushing even harder to get rid of him.