Journal
Longer notes on building software, architecture, tools, and what I learn while shipping.
How I extended my hobbyist AI budget by moving deterministic compliance checks out of Claude sessions and into shared shell scripts across all four of my iOS projects.
Why reusable, structured skills matter more than prompts when building with AI, and how I use them with Claude and Codex in practice.
AI makes protocol archaeology and lost tooling less painful, which opens the door to extending the life of genuinely good hardware.
If the app is the source of truth, the marketing site can be generated and kept in sync without a week of context switching.
Screenshots are only useful if they move through your workflow without breaking it.
AI can generate UI, but without a design system it will quietly erode consistency and quality over time.
Why I treat documentation as infrastructure once AI becomes part of the build loop.
Between side projects, AI at work, and learning new platforms, things were accelerating fast. Obsidian became less of a tool and more of a pressure valve.
How I use AI to explore ideas, write specs, and ship changes without outsourcing responsibility.
A dev journal on using AI to explore fast, then knowing when to slow down, harden foundations, and build real trust into a v1 codebase.
Why I pulled Kanora out of Electron and started rebuilding it natively, and what that taught me about friction, frameworks, and shipping.
A deep dive into how I built a scalable music streaming server using modern web technologies and why I chose this particular stack.
Why I decided to build my own music streaming solution when iTunes went downhill and Spotify got expensive.
A quick note on what EightyThree Apps is, why I'm building these apps now, and what you'll find here.