I changed 5 small things about how I code, and my workflow has never been smoother

Confession time: For a long time, I thought being a productive developer meant typing faster, memorizing more syntax, and pulling off late-night marathons fueled entirely by coffee and panic.

Spoiler alert: It doesn't.

After burning out a couple of times on projects that shouldn't have been that stressful, I realized the problem wasn't my skills—it was my workflow. I was fighting my own tools, wasting mental energy on repetitive junk, and constantly breaking my own focus.

So, I decided to fix it. I didn't learn a brand-new framework or radically change my stack. I just tweaked a few daily habits. Here are the 5 changes that genuinely made coding fun for me again.

1. Treating AI like a junior intern, not a magic wand Look, I use AI tools every day, but we need to talk about how easy it is to become lazy. For a while, I was letting AI write whole chunks of logic that I barely bothered to read. That bit me in production more than once.

Now, my rule is simple: AI handles the boring, repetitive grunt work—like boilerplate code, standard regex, or basic unit test layouts. But when it comes to actual architecture or tricky business logic? That's all me. If I don't understand every single line the AI spits out, it doesn't go into the codebase. Simple as that.

1. Declaring war on local environment lag Nothing kills a brilliant idea faster than waiting 45 seconds for a local dev server to boot or a test suite to finish. We normalize this way too much.

I finally spent a weekend cleaning up my local setup. I deleted a bunch of bloated extensions I never used, wrote a quick shell script to spin up my local databases in one go, and stopped letting background processes hog my RAM. If your laptop sounds like a jet engine every time you open your IDE, take an hour to clean it up. Your mental health will thank you.

1. Writing the PR description while I'm coding You know that sinking feeling when you finish a massive feature, open a pull request, and then stare at the empty "Description" box for ten minutes because you've already forgotten why you made half those changes? Yeah.

I stopped doing that. Now, I keep a messy scratchpad open while I code. As I figure out a weird edge case or make a tough architectural choice, I jot it down right there. By the time I push the code, the PR description is practically already written. It takes zero extra effort and makes code reviews infinitely smoother for my team.

1. Embracing the "Two-Minute Rule" for refactoring We've all told ourselves, "Ah, I'll clean up this messy function later." And we both know "later" means never.

Instead, I adopted a lightweight version of the Boy Scout rule: if I'm touching a file and I notice a terrible variable name, some dead code, or a poorly structured helper function, I'll fix it right then—if it takes less than two minutes. It keeps the codebase clean organically without needing massive, painful refactoring sprints later on.

1. Defending my "Deep Work" time like my life depends on it If you check Slack, email, and Twitter every five minutes, you aren't actually coding—you're just constantly restarting your brain.

I started blocking out a strict 2-hour window every day where my notifications are silenced and my door is metaphorically closed. No meetings, no quick questions, just me and the hardest problem on my plate. Getting into that flow state used to feel rare; now, protecting it has made me twice as productive in half the time.

Wrapping up
At the end of the day, coding isn't just about the code we write; it's about the environment we create for ourselves to think clearly.

Are you making any of these mistakes right now, or do you have a workflow trick that saved your sanity recently? Let’s talk about it in the comments! 👇