Notes from the build.
Lessons, experiments, and useful mistakes from building software, understanding systems, and learning one layer at a time.
Building EITAMS: Eight Months, a Real Client, and 43 Findings I Didn't See Coming
What I learned building an enterprise IT asset management system for TIQRI Corporation — the problem we got wrong at first, the decisions that mattered, and the five-hour code review that changed how I write software.
- 20268 minSystems engineering
I spent five days building an AI agent, and most of it was deciding what the AI wasn't allowed to do
Building a maternal health WhatsApp agent for IDEALIZE 2026 taught me that in a high-stakes domain, good engineering means pushing intelligence out of the model, not into it.
#AI agents#Health tech#Agent Kernel#WhatsAppRead - 5 minEngineering notes
My first open source contribution came from a TypeError
I wasn't looking for a good first issue. I was stuck, I read the source to get unstuck, and I found the docs disagreed with the code. Here's the loop, and how to actually file the fix.
#Open source#GitHub#Agent Kernel#Lessons learnedRead - 9 minEngineering guides
How to integrate the Spotify Web API with Next.js
A practical Spotify Web API and Next.js guide covering OAuth, refresh tokens, currently playing data, secure Route Handlers, polling, rate limits, and compliant UI.
#Spotify API#Next.js#OAuth 2.0#TypeScriptRead - 5 minEngineering notes
A background that cost more than the page it sat behind
My portfolio ran a neural network in the fragment shader to draw a dark gradient. Replacing it with four CSS gradients removed a dependency, a context leak, and every frame of main-thread work.
#WebGL#CSS#Performance#ReactRead - 3 minEngineering notes
What a telemetry dashboard taught me about resilient interfaces
Building live coding, GitHub, and Spotify signals into one portfolio changed how I think about loading states, partial failure, and honest interface design.
#Next.js#Resilience#API design#User experienceRead - 4 minSystems engineering
Design tenant boundaries before automation writes data
What DayBoard taught me about identity-derived scope, defence in depth, and why multi-tenant safety has to precede booking automation.
#Multi-tenancy#ASP.NET Core#PostgreSQL#SecurityRead - 5 minEngineering notes
OCR accuracy is a product decision, not a model score
Getting receipt extraction from below 60% to roughly 92% was mostly image preprocessing and arithmetic cross-checks. Deciding what to do with the remaining 8% was the harder problem.
#OCR#WebAssembly#Offline-first#SupabaseRead - 4 minEmbedded systems
Real-time software changes when physics joins the system
Lessons from an ESP32 flight controller about task rates, coordinate frames, saturation, failsafes, and debugging software attached to hardware.
#ESP32#C++#FreeRTOS#Control systemsRead - 5 minSystems engineering
Twenty-three calculators, one definition
HariTools could have been twenty-three hand-built pages. Making each tool a typed definition that routes, metadata, structured data, and the sitemap all derive from changed what it costs to add the twenty-fourth.
#Next.js#TypeScript#Content architecture#SEORead - 5 minEngineering leadership
Enterprise software is a problem of state and ownership
Building EITAMS showed me why custody, financial rules, concurrency, and audit history matter more than the number of forms in an internal platform.
#Next.js#PostgreSQL#System design#TeamworkRead