Subject / 01
Backend systems engineer
- Java + concurrency
- Production reliability
- Agentic AI systems

Case board 01 · systems / writing / life
Last mapped · 2026
00 / Profile01 / Systems + Work02 / Field Notes03 / LifeSubject / 01
Senior Software Engineer
Working thesisrequest → queue → worker → recovery
design for the failure pathp99< 120 ms
Observability / live
latency · errors · queue depthdraft → challenge → evidence
keep the useful footnotes
Field notes / Blog
Systems, AI & performanceLong-form writing is part of the map →Off the clock / Life
Ideas, books & elsewherePersonal notes, kept human.Real-time systems · recovery paths · measurable outcomes
Follow the thread

Case board / 00
A senior software engineer focused on making complex production systems understandable, recoverable, and fast.
Java, concurrency, distributed workflows, and performance-sensitive services.
Start with observable behavior, follow the failure path, and measure the recovery.
Building useful agents with production-grade constraints, tooling, and guardrails.
Zoom out. Follow the next board →
Case board / 01
High-throughput systems, deliberate failure paths, and recovery that can be measured.
Concurrency, partitioning, and backpressure without losing ordering.
Recovery paths, replayable queues, and safer operational defaults.
Observable agents designed to operate inside real production constraints.
Zoom out. Follow the next board →
Case board / 02
Practical essays about systems, AI, performance, and the decisions hidden between the diagrams.
Why the recovery story should be designed before the happy path.
What changes when an agent becomes part of a production control loop.
Patterns, bottlenecks, and lessons gathered from Java systems.
Zoom out. Follow the next board →
Case board / 03
Books, unfinished ideas, visual observations, and the side quests that make the systems work better.
Notes from systems thinking, history, design, and good fiction.
Tools, sketches, and curious prototypes without a roadmap.
Street-level observations and the ideas that travel back to the work.
Zoom out. Follow the next board →
Case board / 04
For backend systems, production reliability, and agentic AI work, open a channel directly.
Best for project context, roles, and detailed engineering questions.
Open channelExperience, background, and a direct way to connect.
Open channelProjects, prototypes, and the engineering trail behind the board.
Open channelThe board stays open.