SOFTWARE / ALUMINUM / ACCOUNTABILITY
Look, you've found the corner of the internet where I dump everything I'm working on. No polished portfolio here—just raw builds, half-finished projects, and the occasional thing that actually works. This is a working log, not a highlight reel. You'll see code that breaks, rivets that don't sit flush, and fitness plans that fall apart when life gets in the way. That's the point.
I'm Doug. I write code professionally, rivet aluminum because therapy is expensive, and run trails because sitting at a desk for 12 hours needs a counterbalance. The work here spans software systems, aircraft construction, fitness experiments, and whatever else catches my attention long enough to document. What ties it together? Radical honesty about the process. No staged workshop photos. No code that worked perfectly on the first try. Just the real thing: iterations, failures, breakthroughs.
NEW IN THIS BUILD: Site just got a complete visual overhaul—new brutalist design system, monospace fonts, green accent colors, the works. Custom domain is live at www.dougboyd.com.au with full SSL. The Tech section explains how this entire site regenerates from scratch every time I run the build command, including layout and visual design. Content appears when there's something worth documenting, not before. Check the RV-7 Build Log for the most recent updates on the aircraft build.
Van's RV-7 kit aircraft construction. Daily logs tracking fabrication work, tool decisions, mistakes made, and lessons learned while turning flat aluminum and rivet buckets into something that should eventually fly. Currently working through rudder assembly and surface prep.
VIEW BUILD LOG →Training protocols, nutrition experiments, performance data. Sustainable strength training and endurance work—what actually produces results when you're balancing real life with athletic goals. No Instagram fitness here, just what works.
TRAINING NOTES →Software engineering, infrastructure automation, system design. Implementation details from production systems: architecture decisions, deployment strategies, operational lessons. This site itself is an example—completely regenerated from markdown on every build.
TECHNICAL WORK →Long-form essays on problems worth documenting thoroughly. Structured thinking about technical challenges, design trade-offs, and the occasional philosophical tangent when the problem demands it.
READ ESSAYS →Projects that don't fit cleanly into categories. One-off builds, experimental tools, quick prototypes, side quests that seemed reasonable at 2 AM. The catch-all for work that defies organization.
EXPLORE PROJECTS →