Writing
Notes from building, debugging, and trying to make systems thinking practical.
Useful Tools Start as Annoyances
The tools I keep using rarely start as grand ideas. They begin as one small irritation that keeps showing up until building the fix becomes the honest response.
5 min readPackaging Is Part of the Product
Developer tools are judged by more than their core command. Install paths, config, errors, docs, updates, and recovery flows decide whether people keep using them.
3 min readChaos Engineering for Backend Teams
A practical view of chaos engineering shaped by production work: resilience is not something architecture diagrams prove. It is something you test under controlled failure.
4 min readLangGraph for Backend Engineers
The framing that made LangGraph click for me: treat it like workflow orchestration for stateful, model-driven software, not as AI magic.
4 min readReplayable Systems Are Easier to Trust
The most useful testing habit I picked up from competition software was replayability: once behavior can be reproduced on purpose, debugging becomes calmer and more honest.
3 min readSystems That Must Work on the Day
Competition software taught me a stricter version of reliability: when a live mission depends on your system, responsiveness, logging, and operator trust are not optional polish.
3 min readOperator-First Software
Ground station work changed how I think about interface design: in live systems, clarity, honest feedback, and fast comprehension matter more than decorative polish.
3 min readReal-Time Telemetry Is About Trust
CanSat and TEKNOFEST ground stations taught me that real-time pipelines are not only about speed. They are about readable state, clean boundaries, useful logs, and replayable evidence.
3 min read