About

I tend to notice systems before I notice tasks.

I'm a software engineer who pays attention to the system around the task — the boundaries, assumptions, and recurring friction that make change harder than it needs to be.

Ananda Kevin Refaldo Sariputra

About

Systems before tasks. I look for where boundaries blur, where change is risky, and where a small amount of structure makes good work easier to repeat.

Explanation is part of the deliverable. Models, tests, and runbooks should reduce tribal knowledge — not relocate it behind a single expert.

That instinct also shapes how I teach and collaborate. I like turning complicated technical ideas into models people can inspect, question, and reuse — whether that means a diagram, a test, a runbook, or a conversation at a whiteboard.

Principle

Make variation inspectable

Hidden dimensions become explicit models, tests, and contracts — especially where “special cases” repeat.

Principle

Make change repeatable

Delivery paths, environments, and automation should require less interpretation every time the same class of work returns.

Principle

Keep boundaries legible

Abstractions should clarify ownership and decision rights — not move complexity somewhere harder to see.

02 / Links

Explore.

03 / Motif

An idea that has stayed with me.

Hand-drawn banner reading Build Systems. Create Leverage. Leave Lasting Impact.
The wording has changed over time. The idea hasn't.build systemsleveragelasting impact