I Almost Quit Coding to Become a Welder

Eugene Maiorov — Tue, 26 May 2026 18:46:45 +0000

Twelve years. That's how long I've written code for a living.

About a year ago, I was ready to walk away from all of it.

I'm not joking. I spent real evenings looking up welding schools. I read about handyman gigs. I even checked what delivery drivers make near me. My plan was simple: do anything that didn't involve a screen. With welding, at least when something breaks, it's not because of a missing semicolon.

I was burnt out. Bad. I'd open my laptop, stare at the screen, and just... sit there. Four hours would pass. I'd write maybe ten lines of code, hate all of them, then delete nine. The work that used to feel like magic now felt like chewing glass.

The plot twist: I'm not even scared of new tech

Here's the funny part. I'm not some guy who hides from the future.

Back in 2022, I was one of the first 100,000 people to use GPT-3. I thought it was actual sorcery. For a hot minute, I was sure there were real humans on the other end, typing answers as fast as they could. I pictured a room full of very tired interns somewhere, sweating. (There were not. I think. I never got a clear answer on that.)

I jumped in right away. But the tools were rough back then. They'd make stuff up, break my code, and lie to my face with total confidence. Stack Overflow and the docs were still carrying me. AI was more of a weird hobby than a real helper.

Then things got bad in a way I didn't see coming.

The day my safety net disappeared

Last year, I lost my job.

Not because I was slow. Not because I messed something up. I lost it because my boss's clients figured out they could "vibecode" their own little tools. Why pay a developer when you can describe what you want to a chatbot and get something that mostly works?

Turns out my job security was one good prompt away from gone.

So there I was. Twelve years of experience, suddenly out of work, watching the exact thing I do for a living get handed out for free.

That's when the welding tabs really started piling up in my browser.

But I didn't quit. Not yet.

I had months of empty time. So I made a deal with myself.

Instead of being mad at these tools, I'd learn to actually build with them. Not just ask a chatbot to patch a bug. I mean really build. Design whole systems. Ship real features. Move fast.

It was a love-hate thing for a while. Some days the AI felt like a genius pair programmer. Other days it felt like a confident toddler with a keyboard. I'd ask for one small thing and get back something completely unhinged. I yelled at my screen more than once. My kids probably learned a few new words.

But slowly, it clicked.

I stopped "using AI" and started thinking with it. I learned how to talk to it. How to break a big mess into small pieces. How to set things up so it handled the boring parts while I made the real calls. It went from a toy to a power tool.

The comeback

Then I landed a new job.

This time at a company that actually trusts me. They let me bring my whole AI-first workflow to the team. And bringing it to real people, on a real product? Night and day.

I'm building things now I couldn't have touched two years ago. Like an AI that answers the phone and talks to customers like a real person. The kind of project that used to need a whole team and six months. I'm doing it almost solo, in days.

And here's the part I didn't expect.

I love my job again.

I'm not fighting with syntax. I'm not frozen in front of a blank file, slowly dying inside. I get to think about the fun stuff: what to build, why it matters, how to make it actually good. The boring parts mostly take care of themselves.

I feel like a developer again. Maybe more than ever.

Oh, and the welding?

I wasn't totally joking about that part.

I got myself a full welding kit for my birthday last year. Mask, inverter, electrodes, the works. Turns out the dream didn't die — it just turned into a weekend hobby instead of an escape plan.

So now I build software all week and melt metal in the garage on the weekend. Best of both worlds. My code compiles, and so do my welds. (Most of the time.)

Your turn

So that's my story. I went from googling welding schools to feeling more excited about code than I have in years. All because I stopped fighting the wave and learned to surf it.

I can't be the only one.

If you've been doing this for 10+ years and hit that same wall — the "I'm done, I'm going to go work with my hands" wall — I want to hear it. Did you find your way back? Or are you still eyeing the welding catalog?

Drop your story below.