BLOG
TIMELINE.

A small feed for software engineering, architecture, leadership, game development, books, and the systems around them.

SEARCHTAG FILTER

5 POSTS

1mo

13 min

92% heat

Good deploys should feel a little boring

Pipelines, Docker, Kubernetes and cloud are tools. The real goal is helping the team change the system with less fear, more feedback and less ritual.

I have seen DevOps treated like a shrine of YAML. Big pipeline, Docker, Kubernetes, a wall of checks, lots of variables. It looks mature. But maturity is not ceremony before deploy. Maturity is confidence.

DevOps

2mo

12 min

89% heat

What I learned by standing between frontend and backend

Full stack is not just switching tabs between Next.js and an API. It is understanding how a screen decision becomes a contract, how a rule becomes state, and how backend details reach the user.

I like full stack work when it stops being a technology checklist and becomes a way of thinking. The real value is translating problems between worlds that often pretend they are separate.

Full Stack

3mo

13 min

93% heat

The less glamorous part of technical leadership

Being a technical reference should not mean becoming the team's universal power outlet. Good leadership helps the team see better, decide better, and depend less on one person.

There is a seductive trap in technical leadership: you start helping everyone, solving problems, unlocking decisions, explaining context. Then one day you realize you became the router. Everything goes through you.

Leadership

4mo

12 min

94% heat

Good backend is when nobody has to ask about the backend

Users do not see the kitchen, but they feel when the dish is late, cold or wrong. Good backend is the invisible part that keeps the restaurant standing without needing applause.

I like backend because it has a built-in humility. When everything works, nobody comments. The screen opens, the transaction passes, the event arrives, the queue moves. It looks simple. It only looks simple.

Backend

5mo

11 min

91% heat

The kind of code I like finding on a Monday

Code that looks beautiful on day one is not always code you can live with for years. The real test is change, onboarding, production bugs, and whether the house remains livable.

I started understanding code better when I stopped thinking of it as sculpture and started thinking of it as a house. A sculpture you admire from the outside. A house you live in. It has bills, leaks, cabinets you open every day, and outlets in places that either help you or annoy you for years.