I am 52 years old and I am coding until 4 AM again. Not because I have to. Because AI tools made me fall in love with building again.
After 12 years in management, I genuinely thought my coding days were over. I had moved up the ladder. I was leading Agile transformations, managing enterprise systems for 100,000+ employees, running quarterly planning for product teams. Good work. The kind of work people congratulate you for at company events.
But I missed the thing that got me into tech in the first place. The feeling of building something from nothing. Typing a few lines and watching a screen come alive.
The Gap Between 2005 and 2025
The last time I wrote serious code was around 2012. Back then, building a web app meant learning a framework for months before you could ship anything useful. Setting up a development environment was a project in itself. Deploying to production required a sysadmin and a prayer.
When I looked at coding again in 2024, I expected the same thing. Weeks of setup. Months of learning. A slow crawl back to productivity.
That is not what happened.
I discovered V0, Bolt, Cursor, Copilot, and Claude Code. These tools changed the entire equation.
In 2005, it took me 6 months to learn one framework well enough to build something real. In 2025, I built a working app in 6 hours. That is not an exaggeration. The first version of CareerLeap went from idea to deployed app in a single day.
What AI Coding Actually Looks Like
People hear "AI coding" and imagine a robot writing perfect code while you sit back and watch. That is not how it works. What actually happens is more like pair programming with a very fast, very knowledgeable partner who never gets tired.
You describe what you want in plain English. The AI writes the code. You review it, test it, and tell the AI what to change. Sometimes the first attempt is exactly right. Sometimes you go back and forth for an hour fixing edge cases.
The key difference is speed. Things that used to take me days now take minutes. Setting up authentication, building API routes, creating responsive layouts, configuring deployment pipelines. The boilerplate work that used to eat most of your time is just gone.
What is left is the interesting part. Deciding what to build. Designing how it should work. Figuring out what users actually need. The thinking work. The creative work.
My daily stack is simple. I do not use everything. I picked a few tools and learned them well.
Claude Code is my primary coding tool. I open it in the terminal, describe what I want, and it writes the code directly into my project files. It reads my existing codebase, understands the patterns, and writes code that fits. Most of the work on Sucana, GEOScore, and my personal site happens here.
Cursor is my editor for when I need to see the code and make manual changes. It has AI built in, but I mostly use it as a smart editor with good autocomplete.
V0 by Vercel is great for generating UI components. I describe a layout or a card design and it generates a React component with Tailwind CSS. I rarely use the output directly, but it gives me a starting point that saves 30 minutes of writing CSS from scratch.
Next.js is the framework I use for everything. It handles routing, server-side rendering, API routes, and deployment. Combined with Tailwind CSS for styling and Vercel for hosting, I can go from idea to live website in hours.
ChatGPT and Claude (the chat versions) are my thinking partners. Before I code anything, I talk through the approach. What should the database schema look like? What is the right API design? What am I missing? These conversations save me from building the wrong thing.
What I Built in 10 Months
Since I started coding again, I have shipped 9 products:
- CareerLeap - Career development platform
- GoalSetting - Goal setting framework and workbook
- Part Time Founders - Community for side-project builders
- Discourage.me - AI-powered reality check tool
- Jivro - Product idea discovery platform
- Funny Answers - Entertainment platform
- Laksha - Professional services platform
- GEOScore - AI search visibility analyzer (open source)
- Sucana - AI analytics platform for marketing agencies
Not all of them worked. Most of them did not get traction. But each one taught me something and made me faster at building the next one. By the time we started Sucana, I could ship in hours what would have taken me weeks on CareerLeap.
The point is not that all 9 were good ideas. The point is that AI tools made it possible to try 9 ideas in 10 months while keeping a full-time job. That would have been impossible five years ago.
The Playing Field Is Level Now
Here is what I want people to understand. You do not need a computer science degree to build software anymore. You do not need 10 years of coding experience. You do not need to know the difference between a REST API and a GraphQL endpoint before you start.
You need to be able to describe what you want in clear language. You need to be willing to test things and iterate when they break. You need patience for debugging (see my One Inch Closer philosophy).
That is it.
I know this because I lived the other version. I spent the first 10 years of my career as a developer, learning everything the hard way. Memorizing syntax. Reading documentation for weeks. Debugging with print statements. It worked, but it was slow and it rewarded people who had the time and resources to invest years in learning.
AI tools changed that. A motivated person with no coding background can build a working web application in a weekend. Not a toy. A real, deployed, usable application.
The playing field just got leveled. If you think you missed the coding revolution, you are wrong. You are arriving at the perfect time.
Why I Stay Up Until 4 AM
People ask me why I code until 4 AM at 52. They assume it is hustle culture or some productivity obsession.
It is not. It is the same feeling I had when I first started programming in 1999. I had just left a sales job I hated. I enrolled in a 6-month programming course and coded 12 to 16 hours a day. Not because someone told me to. Because I could not stop.
That feeling came back. The dopamine hit of seeing something work. The satisfaction of shipping a feature that did not exist an hour ago. The quiet pride of building something useful.
AI tools did not create that feeling. But they removed the barriers that were keeping me from it. No more spending three days configuring webpack. No more reading framework documentation for a week. No more writing boilerplate for hours before getting to the interesting part.
Now I describe what I want, and the interesting part starts immediately.
If You Are Thinking About It
If you are in your 40s, 50s, or 60s and thinking about coding (or coming back to it), here is my honest advice.
Start with Claude Code or Cursor. Do not try to learn a programming language first. Start with a tool that lets you describe what you want and generates the code. You will learn the language by reading what it produces.
Build something you actually need. Not a tutorial project. Not a to-do app. Something that solves a real problem in your life or work. The motivation to finish is ten times stronger when you care about the outcome.
Give yourself permission to build ugly things. Your first app will not look like a startup's landing page. That is fine. Ship it anyway. The polish comes later.
Find one other person who is building. Not a community of thousands. One person. Someone you can message and say "look what I just built" or "this thing is broken and I have no idea why." That accountability changes everything.
I found my cofounders by building. Not by networking. Not by going to events. By shipping things and talking about them online. The right people noticed.
If you are coding or thinking about starting, I would love to hear what you are working on. Find me on Twitter/X or LinkedIn.