Find a piece

Building Beautiful Terminal UIs with Bubble Tea

A practical guide to building interactive terminal applications in Go using the Bubble Tea framework and the Charm ecosystem.

Concurrency in Go: Goroutines, Channels, and Select

A deep dive into Go's concurrency primitives — goroutine lifecycle, channel patterns, the select statement, and real-world idioms.

Go's net/http: A Complete Guide to Building REST APIs

Building production-ready REST APIs using only Go's standard library — middleware, routing, JSON, and testing patterns.

Beyond Chat: Discovering Jules and Google's Agentic Future

My journey from standard AI assistants to Google's Jules, and why the async agent model changes everything for developer productivity.

Agentic Self-Building Loop

Architecting a closed-loop agentic system using Azure, Palantir Foundry, and GitHub Copilot to automate parts of the development lifecycle with human-in-the-loop consultation.

The Vertical Soloist and the Perfect Stack

The solution was elegant, high-performance, and solved a problem we didn't have using a stack nobody else could run.

13 Engineering Laws Every Builder Should Know

Named principles that explain why software systems and organisations behave the way they do.

DELETE Doesn't Delete. It Archives. This Was By Design.

Four partners built GDPR compliance flows against a DELETE endpoint that kept all the data.

Nobody on This Team Needs to Know SQL

The ORM abstracted the database. The database kept running queries. Nobody told the database.

Nobody Was Supposed to Be Using That Field

It was deprecated. It returned null. Twelve teams depended on the null.

Our API Accepts Anything. That Was the Feature.

Flexible input, they said. Eleven weeks of corrupted records later, it still accepted everything.

Our Velocity Is Up Forty Percent. Nothing Has Shipped.

The sprint completion rate looks excellent. The product roadmap does not.

The Architecture Nobody Planned

The system diagram looks exactly like the org chart. Nobody drew it that way.

The New Framework Is Forty Percent Faster

The benchmark was accurate. It was just not about this application.

This Config Flag Makes No Sense. We Removed It.

The flag was unexplained. The cleanup PR was approved. The invoices were wrong for three days.

We Gave It Six Months to Be Safe

The estimate was three weeks. The timeline was six months. Both were accurate.

We Padded the Estimate. It Didn't Help.

Two weeks of work. Three months of estimate. Still two weeks away.

We Scaled to Forty Instances. The Report Still Takes Fourteen Minutes.

The infrastructure spend doubled. The bottleneck is in a stored procedure. The two facts are unrelated.

We're Bringing In Three More Engineers

The release was six weeks behind. Now it's nine.

We're Designing the Final Architecture First

The design took four months. The competitor shipped in week six.

Rebuilding DivineForge: From Hugo to Next.js App Router

The Tech Stack That Could Not Be Agreed On

The selection criteria document had 23 criteria. Every vendor scored 6.7.

The Steering Committee That Steered Into Another Steering Committee

The programme needed governance. So governance created a committee to govern the governance.

The Roadshow That Replaced the Roadmap

The strategy deck had 47 slides. The backlog had 3 tickets.

The Demo That Became the Product

It was never meant to go to production. The CTO saw it on a Tuesday.

The Purchase Order That Needed Its Own Purchase Order

The software cost $400 a month. The procurement process cost six weeks and four people.

The Proof of Concept That Ran for Eighteen Months

It was always almost production-ready. Every sprint.

Standing Up DivineForge as a Work Log

The Budget That Was Approved in Q1 and Released in Q4

The money exists. It was approved. It is simply not available yet.

Shipping Roadside Assistance in Bank-Owned Insurance

The Initiative That Required Five Teams to Move First

Every team was waiting for a different team. The initiative was technically still active.

The Architecture Review Board That Reviews Architecture

You need to change an environment variable. The ARB meets on the third Thursday.

The Database That Would Have Been Oracle

Nobody was still using Oracle. Until someone from the enterprise architecture team joined the call.

The Team That Exists in Another Timezone

They own half the integration. They are 6 hours away. Slack messages disappear into the void between 3 PM and 9 AM.

The Dependency Nobody Documented

The system has a hidden dependency on a service owned by a team in another timezone who doesn't know you exist.

Explaining the Thing to the Room

The concept is clear in your head. The room has 12 people with 12 different mental models. You have 15 minutes.

The Three Hat Problem

You are the Solutions Architect. Also the Enterprise Architect. Also the one who actually builds it. These roles have conflicting interests.

The Value Proposition Nobody Agreed On

Six stakeholders. Six definitions of value. One slide deck that tries to please all of them.

Smart Home with Zigbee — A Malaysia Context

Building a reliable smart home network using Zigbee, Tuya-compatible devices, Google Home, and a Zigbee gateway — designed for a Malaysian home.

We Need to Scale This

The product has 200 users. Someone has already drawn a Kubernetes diagram.

It Works on My Machine

A phrase so powerful it ends investigations, closes tickets, and starts arguments.

We'll Clean It Up Later

Later is a place on the map that no engineering team has ever reached.

It's Just a Small Change

Five words. Every engineer's blood pressure goes up 20 points.

The Quick Sync That Wasn't

It's just 15 minutes, they said. You'll be done by 10:30, they said.