• 1 Post
  • 7 Comments
Joined 1 year ago
cake
Cake day: August 9th, 2025

help-circle


  • Anyone can learn to code well enough for a corporate environment.

    The bar is even lower for a government environment. 🥲

    Thankfully, we’re already setup with a linter/auto code formatting. Mandatory PR templates/size limits would probably be overkill with a team this small - but I get your point. He really just needs to stick to the ticket’s original scope and I’m going to harp on it more. We just had another talk about it on Thursday.

    I appreciate the suggested dialogue. We’ve had conversations like this - mainly to see his openness to a lead in developer-adjacent things like testing. He’s not very… self aware or well experienced career wise to say the least.

    We’re at the “figure out somewhere he can fit” or “remove him from the team” phase. We’d prefer to find a way to keep him.

    Thank you for the sound advice/suggestions though.




  • Appreciate the advice; I’ve been indirectly documenting it with the other devs since they were wondering why Bob’s pull requests take 2-3 rounds of fixes. (They were starting to wonder if I was just being a hard ass about everything).

    But holy shit I am never ever letting him script anything that has the potential to last beyond a few months, as it’s brilliant, but completely unmaintainable, impossible to debug, and generally can’t handle edge cases.

    This sounds like Bob, but subtract a few years of experience… but finding things with a short lifespan is hard on a project that’s all new code. The architecture/long term planning is crucial and that’s where Bob struggles.

    Point is, it’s your boss’s job to figure out where all his people fit into the grand scheme of things.

    Agreed, but it’s a small team of 4 devs (myself included) + 3 others. We’re basically at the phase of trying to find him something or else we’ll need to remove him. He’s a good fit socially and is genuinely trying.


  • Bob has great ideas / an eye for design, which has definitely helped. Unfortunately, he’s here as a developer because he wanted to move away from the webdesign space so nudging him that direction isn’t want he wants.

    He was fully on our backend at the start and was getting help from another dev. He’s now on the frontend because that dev needed a break and was hoping the familiarity/different language would help. The problems I see are language non-specific, like basic programming principals/architecture.

    Bob would probably do fine on a team that’s just maintaining a legacy codebase, but we’re writing everything from scratch.

    It’s a weird work environment; HR/performance improvement plans aren’t really a thing. We’re basically at the step of asking if he should be removed but trying to find something for him. He’s a good person and fits well socially.