
4 min read
Why the single package.json monorepo policy is a trap
A single root package.json can look simpler in an Nx monorepo but dependency hoisting hides ownership and can turn upgrades into confusing production build failures.
Read articleIndependent engineering notes
Notes on web, JS/TS, CI/CD, and experiments. Written from production experience, without the ceremony.

4 min read
A single root package.json can look simpler in an Nx monorepo but dependency hoisting hides ownership and can turn upgrades into confusing production build failures.
Read article
5 min read
GraphQL solves a real problem, but in many enterprise setups that problem is already handled by BFFs. After years using Apollo in production, I think the tradeoffs often outweigh the win.
Read article
4 min read
Dependabot PRs are useful, but researching every upgrade across a large monorepo is slow. I wired Copilot CLI into GitHub Actions so AI handles the dependency research and humans make the call.
Read article
4 min read
I ran Knip across our Nx repo, took the “unused” list as a hint, deleted candidates, built, tested, booted apps, and put a few back when they were secretly used. Net, about 120 packages gone.
Read article