The honest path from Navy veteran to self-taught developer after 30 — no CS degree, no bootcamp, just build-break-fix-repeat.
A legendary salute to INFS and FITTR Family for revolutionizing the fitness dimension of humankind.
I wrote that years ago after completing a nutrition certification. It was not my first self-teaching experience, but it was the one that made the pattern click. I had taught myself calisthenics over years in Navy parks. I had taught myself investing from books and spreadsheets. And with that nutrition course, there were light bulb moments and chain reactions in my brain — I realized that everything I had ever learned, I had taught myself. Not because I was gifted, but because I had no other option.
That same pattern is how I became a developer. No CS degree. No coding bootcamp. No mentor holding my hand. Just a Marine veteran who was past 30, who needed to build things, and who applied the same stubborn self-teaching method that had worked for everything else.
The Starting Point: A Spreadsheet
My first "project" was not a website or an app. It was a Google Sheets spreadsheet that tracked my workout metrics. Sets, reps, body weight, personal records — all entered manually after every training session.
After a few months, I wanted the spreadsheet to do more. Calculate weekly averages automatically. Generate charts without me manually selecting data ranges. Send me a summary every Sunday. Basic automation.
So I Googled "Google Sheets automation" and discovered Apps Script. That was my first exposure to code. JavaScript syntax in a spreadsheet context. I copied scripts from Stack Overflow, broke them, fixed them, broke them again. Each broken script taught me something. Each fix gave me a tiny piece of programming understanding.
I did not know it at the time, but that spreadsheet was my bootcamp. The curriculum was my own need. The projects were real problems I actually wanted solved. The motivation was not a certificate — it was a better training log.
The best programming curriculum is your own unsolved problems. Real needs produce real learning. Everything else is tutorial entertainment.
The Learning Path: Build, Break, Fix, Repeat
From Apps Script, I moved to HTML and CSS. I wanted to build a simple webpage to display my fitness progress publicly. The first version looked terrible. Black text on white background, no layout, no design. But it loaded in a browser and showed my data. That was enough to keep going.
Then JavaScript. Not from a course — from needing interactivity on my page. I wanted a button that filtered exercises by type. That meant learning DOM manipulation. One feature, one concept, learned because I needed it.
Then Python. Not from a tutorial series — from wanting to automate data collection from multiple sources. A script that pulled my training data from Sheets, my weight from a CSV export, and generated a combined report. One automation, one language, learned because the alternative was doing it manually forever.
Then React. Because static HTML pages could not handle the complexity of what I was building. Then Next.js. Because I needed server-side rendering and API routes. Each technology was learned not in sequence from a curriculum but in response to a specific limitation of the previous technology.
The progression: HTML/CSS, JavaScript, Python, React, Next.js. That is five technologies over several years. Not five technologies in a 12-week bootcamp. Real learning at a pace dictated by real needs.