Why I Built It

I've had a blog online since just after college, but while the blog format was hot in 2007, most of what I want to share online has been scattered to other platforms. I have great conversations on LinkedIn, long-form ideas on Substack, and moe than likely those platforms are better places to reach me. I've needed to prune this old site and collapse things to a single page that instantly says “Here’s who I am, what I do, and where you can find my best work.”

The catch? I didn’t want to babysit a website with weekly updates, and I definitely didn’t want to rebuild the same content over and over for different platforms. The solution was obvious: build something lean, automated, and smart enough to stay relevant on its own. Although I probably could have done that on my own on a long weekend, the growing capabilities of LLMs made it possible to automate the process and make it a lot more fun for me.

Why I Used AI (and Which Ones)

I could have written every word by hand, but that would’ve been weeks of drafting, rewriting, and fighting the curse of “too many tabs open.” Instead, I turned to ChatGPT 5—a tool I already use for deep technical reasoning and quick-turn copy—to help me:

• Extract the core themes from my work history
• Turn those themes into clear, scannable skill clusters
• Rewrite and sharpen sections until they were crisp and to the point
• Suggest improvements I wouldn’t have thought of on my own

Why ChatGPT 5 specifically? It’s fast, understands technical language, and, unlike me at 11 PM, it doesn’t get stuck trying to find exactly the right verb. It let me focus on the big picture while it handled the language polish. It also helps that I'd already created a JSON document profiling myself and my work history, which made it easier to extract the core themes.

Why I Used AMP from Sourcegraph

Once the content was ready, I needed a way to make the site easy to update—no complex CMS, no endless hand edits. Enter AMP from Sourcegraph. It let me:

• Generate a static site generator that fits my needs instead of bending to an off-the-shelf template
• Write helper scripts that pull directly from my JSON profile and external feeds
• Automate asset processing, so images, metadata, and links just work without extra effort

I chose AMP because it feels like working with a co-pilot for code: I describe the workflow I want, and it builds the scripts to make it happen. That meant I could focus on the site’s logic, not the boilerplate.

Leveraging An Open Source Template

I've loved hand coding HTML designs for years, but when it comes to my own work I've tinkered with so many verions that now I'm just too tired to keep up. So I'm using an open source template to save time and energy. At this point, I don't think I have anything to show off by insisting on building my own design, and particularly not if I'm building the whole thing with AI. In fact, using off-the shelf resources makes it a lot easier for the AI to understand what I'm doing.

Designing for External Content

Instead of trying to mirror everything I’ve written or built, the site acts as a curated guide. It:

• Points directly to my most active channels—LinkedIn for short updates and discussion, Substack for long-form thinking
• Gives each link the right amount of context so you know why it’s worth clicking
• Stays fresh without me logging in to tweak it every time I post somewhere else

The philosophy here is simple: the website is the map, not the territory. The conversations happen elsewhere, but now there’s a clear entry point.

Outcome Focused

The end result is a site that works like a launchpad: visitors land here, get oriented, and head straight to where I’m most active. No dead pages, no “last updated in 2011” embarrassment—just a living, connected entry point to my work. I want you to engague with me where I'm at - not where I was.