• 0 Posts
  • 2 Comments
Joined 3 years ago
Cake day: June 12th, 2023
  • VoterFrog@lemmy.worldtoProgramming@programming.dev•I tried AI, was impressed by it, and it's embarrassing; Need advice
    3·
    1 hour ago

    The way you guys are working is not about speed. It’s procrastination. The work needs to get done. You can either do it now or you can do it when the bug reports and change requests start coming in. There’s no speed to be gained by procrastinating, often it’s the opposite.

    If it was me, I’d focus on producing better code despite the pressure. You know you’ve got coworkers spending time watching YouTube instead of turning their work in or picking up the next ticket. There’s your time to ask Claude to refine and refactor the code before you commit it. Just don’t be the slow guy and you’ll be fine.

    Just refactor as you go. You don’t have to over engineer things. KISS and YAGNI are valuable engineering approaches. But don’t fool yourself into thinking that turning your work in an hour or two earlier is going to make a big difference in how the higher ups see you.

    Where this really starts to pay off is

    1. Your name comes up less often when assigning bug reports since you don’t own the feature that is bugged. People notice this.

    2. Less time spent fixing bugs means more time making new features. Means you own a larger part of the codebase. People also notice this.

    3. When a change request comes in and you go “Oh yeah, that’s easy. I already considered that and it’s like a 1 line config/code change.” You look like a fucking wizard when this happens.

    This has always been my approach. Even in places with little to no quality standards. Hell, I think it works even better in places with no quality standards because it makes you stand out more.

    P.S. While you already have a job is the best time to look for a new one. Because you don’t have any real stakes for failure.