I sat on my engineering skills for years. Here's what I'm doing about it.

I graduated from Holberton School Tulsa — now Atlas School of Tulsa — as a full stack software engineer. Then I mostly didn't use those skills for a while. Life moved in other directions and the urgency faded. Recently I started job hunting in software engineering and the market made things clear pretty quickly: AI has changed the landscape significantly, the competition for roles is intense, and a credential without visible work to back it up doesn't move the needle the way it used to. I needed more than a diploma. So I thought about what actually separates developers who get hired from developers who don't. The answer I kept coming back to was documented, public work — projects where someone can see the decisions, the reasoning, the mistakes, and the progress. A build diary, essentially. A record of how you think. That's what I didn't do at Atlas School. I built things, but I didn't document them. I'm doing that now, starting with my portfolio. The old site problem There's already a