Why I'm starting this blog

For years I told myself I'd start writing "when I had something interesting to say." Turns out that bar is conveniently impossible to clear. Every week I solve a hard problem, make a trade-off I'll need to remember, or explain something to a colleague that probably deserves to be written down, and then it disappears into chat logs and forgotten Jira tickets.

This blog is my attempt to fix that.

What you'll find here

I'm a Senior Frontend Engineer focused on enterprise-scale Angular and React architecture, Nx monorepos, microfrontends, and design systems. I also spend a lot of time thinking about how AI tooling changes the engineering craft, not as a replacement, but as a force multiplier.

Posts here will fall into a few buckets:

• Architecture deep-dives: real decisions from real codebases, with the constraints intact.
• AI-assisted development: workflows, prompts, patterns, and honest assessments of what works.
• Engineering craft: everything from naming things to managing complexity at scale.

Why "from the engine room to the codebase"

Before I was an engineer, I worked as a marine engineer on cargo vessels. I spent years keeping large, complex machines running in conditions that didn't care about your deadline. I didn't know it then, but that job taught me more about debugging, redundancy, and operational discipline than any bootcamp could.

Frontend development is younger and friendlier, but the underlying challenge is the same: understanding systems deeply enough to make them reliable.

I write about both worlds, because the lessons transfer.

A note on format

The first few posts will be short. I'd rather publish a sharp 500-word insight than a meandering 3,000-word essay. If something resonates, I'll go deeper.

Here's what that might look like in practice:

// Write the small, complete thing.
// Expand only when the idea earns it.
function publish(post: Post): void {
  if (post.isComplete && post.addsValue) {
    ship(post);
  }
}

See you in the next one.