Tag: technology

A Team of One Plus Two

September 12, 2025

I thought LLMs were just Copilot.
This week I discovered agents — and it changed how I code.

Instead of autocomplete, I had Claude Sonnet 4 troubleshooting bugs with me in real time. I redirected it when it drifted, or followed when it made sense. At one point, I asked it to output all its decisions into Markdown — suddenly I had a log of learnings I could share with the team.

A coworker spun up an Model Context Protocol (MCP server), so we all could mine knowledge about our project through hundreds of Confluence pages. Suddenly I wasn’t a solo engineer anymore — I was a team of 1 human + 2 agents.

The result? Faster debugging, better knowledge capture, and new side project ideas. I’m thinking, how could I implement a MCP server to mine Google Drive folders? Or, OneDrive? And hook them into apps or blogging platforms like this one WordPress?

So many possibilities! I’m excited! Hoohaa.

The CI Failure That Could Have Cost Us 42,000 SEK/Year — Until a 2-Line Fix

July 10, 2025

This week, I merged a PR into develop that looked clean locally — only to have it fail in CI after merge.

The reason?
My dev build passed, but there was no local process or a step in our feature branch pipeline that attempted a production build before committing and/or merging.
A small TypeScript mismatch slipped through — and CI caught it only after it was merged.

Root cause

A type import didn’t get checked in the local dev build.

tsc –build in production mode caught it — but that step wasn’t part of local workflows.

Our develop branch builds from scratch using yarn build:prod.

Fix

I added a yarn build:prod step to our Husky pre-commit hook.
Now, prod build errors fail before the commit even hits GitHub.

Impact — Quantified

1. Engineer Time Lost to Debugging

Avg 1 engineer loses ~30 min diagnosing unexpected CI failure
Happens ~2x/month in teams of 3–5
 = 1 hour/month x 1,500 SEK = 1,500 SEK/month

Annualized: 18,000 SEK/year just in lost debugging time

Reduced CI re-runs

  • 5 avoidable failed builds/month + 15 min of rework
    → 2,000 SEK/month = 24,000 SEK/year

Compute cost reduction

  • ~75 CI minutes/month avoided
    → 4.5 SEK/month = ~54 SEK/year

Total estimated savings: ~42,054 SEK/year from a 2-line config change.

____

So, The earlier the feedback, the cheaper the fix. If you’ve been relying on dev builds alone before merging, double check what your CI’s really doing. You might catch more with less.

Verified by ExactMetrics