Insights
Case studies and engineering notes on building software with AI agents: harnesses, multi-agent review, evaluation, and frontend architecture.
Case Study /
How cheaper agents built Musnad Ahmad unattended in one night, how three independent checkers and a second-vendor plan review caught what they got wrong, and why a scholar's ruling is never filled in by a model.
By topic
Latest
Case Study /
The repositioning you are reading was carried out by cheaper agents working in parallel worktrees under a file-ownership manifest, with a failing test shown before every change. What the audit found first, how the phases were cut, and what the record shows.
Case Study /
A multi-pass agent pipeline made 19,548 word matches, accepted 83% automatically, and left 362 for a reviewer agent and the owner's final read. What the review caught, and what changes next.
Case Study /
How a complete Roman Urdu Qur'an went from an agent's draft to a shipped edition: lint, two independent model verdicts pinned to the text, an owner's random sample that found two wrong words, and the sweeps that found nineteen more.
Angular Enterprise Patterns /
Angular rewards teams that lean into its opinions rather than fight them. A practical view of standalone components, dependency injection, and boundary patterns that keep large Angular applications maintainable for years.
Developer Experience /
Developer experience is not perks or preference — it is build times, test signal, and feedback loops treated as infrastructure. A practical view of measuring and improving frontend DX.
Platform Engineering /
Frontend platform teams fail when their mandate is vague. A practical view of what a platform team should own, what it should not, and how to tell whether it is working.
Frontend Governance /
Good frontend governance is nearly invisible: it removes uncertainty and makes the right decision the easy one. A practical view of standards, review, and decision records that help teams move faster.
Nx Monorepos /
An Nx monorepo is only an asset while its structure stays legible. A practical view of the library taxonomy, dependency rules, and conventions that keep large workspaces navigable.
Frontend Architecture /
Why package boundaries, not frameworks, decide whether many teams can build on one frontend platform — and how to draw them so they hold under pressure.
Frontend Governance /
A practical architecture view of how enterprise teams can govern Storybook as shared frontend infrastructure rather than a loose component gallery.