In mid-2015 I set myself one goal: become a professional front-end developer. I had a text editor, a pirated-design-era sense of guilt about typography, and a lot of time.

Ten years later, the scorecard reads: 50+ approved HTML templates on ThemeForest, WordPress themes, Laravel Blade front-ends, static sites in Astro, Hugo, and Jekyll — and a Stack Overflow tab that never closes.

What ThemeForest actually teaches you

People underrate template marketplaces as a school. A ThemeForest reviewer doesn’t care about your feelings; they care about pixel accuracy, responsive behavior, RTL support, and documentation. Getting fifty templates through that gate teaches you a kind of discipline no bootcamp covers:

• Ship the whole thing, not the fun 80%
• Someone you’ll never meet must be able to customize your code
• “Works on my machine” is not a browser support policy

What changed

Almost everything mechanical. Floats died, flexbox and grid won, Sass went from superpower to convention, and :has() quietly deleted a whole category of JavaScript. Static site generators made “just HTML” a serious architecture again — which, for someone who started in HTML, feels like the industry circling back to say I was right.

The newest change is AI. I use it the way I once used Stack Overflow: a collaborator for the parts outside my specialty, while the design decisions stay in my head. It hasn’t replaced the craft; it’s removed the drudgery around it.

What never changed

The job is still the same sentence it was in 2015: look at a design, understand why it works, and rebuild it in code without losing the why. Tools rotate. Taste compounds.

Ask me again in 2035.