These started as notes to myself — a decade of front-end work will do that. You solve something carefully, then six months later you cannot remember the careful part. So I write them down as I go until they sounded like notes I would have sent a teammate.
MCP belongs in front of the APIs you already have
Agents should call threat and search the way our services already do.
How to add MCP in an API repo so agents can query latest email-threat detections and search without scraping a UI.
MCPAI
Remotes still need a route
Standalone serve is not the product. The shell’s URL is.
How an independently deployed Angular remote dies in the host when routing and auth contracts are implied instead of written down.
AngularFront-endMicro front-end
Affected is the CI
If tags are wrong, you either rebuild the world or skip a remote.
How Nx affected keeps a multi-product Angular monorepo honest in CI — and what happens when the graph lies.
AngularFront-endMicro front-end
Teachers and donors are not the same user
Same API, different data. A donor does not get a child’s name.
How a Node API for a child-education NGO splits teacher and donor access so progress can be shared without leaking learners.
Node.jsBack-end
Go after years of Node
Errors are values. Goroutines are not Promises. The binary is the deploy.
What actually changes when someone who ships Node and Java starts writing small Go tools.
GoBack-end
Share the tokens, not the components
Remotes can share a colour. They should not share a junk drawer of widgets.
How a design-token library keeps Angular micro frontends looking like one product without a fat shared component dump.
AngularFront-endMicro front-end