I have been writing notes for years. Architecture decisions, debugging war stories, things I wish someone told me before I shipped that thing to production. All sitting in private docs nobody reads.
That felt like a waste. So here we are.
Why bother?
I have shipped 15+ products across 10+ industries over the last decade. Google, Telefonica, startups you have never heard of. Every project taught me something. Most of those lessons live in my head or in scattered docs. A blog gives them a permanent home and forces me to think clearly about what I actually learned vs what I think I learned.
A portfolio shows what I built. A blog shows how I think. If you are deciding whether to work with me, both matter.
What to expect
Short posts on real engineering problems. Architecture decisions where both options suck and you pick the less painful one. AI tooling -- I have been deep in Claude Code, building plugins, automating my own workflow. Performance work. Shipping fast without shipping garbage.
No listicles. No "ultimate guides." No sponsored content. Just notes from building things.
This blog's stack
Astro with MDX on Cloudflare Workers. Zero client JavaScript (except a tiny search filter). Content Collections for type-safe frontmatter. Shiki for code highlighting. The whole thing scores 100 across Lighthouse.
const posts = await getCollection('blog', ({ data }) => {
return !data.draft && data.publishDate <= new Date()
})
Every post is an .mdx file committed to the repo. Git is the CMS. No database, no build-time API calls, no dependencies that will break in six months.
First real posts coming soon -- starting with how I set up my AI development stack and why most people are burning tokens for nothing.
Originally published at harryy.me
Top comments (0)