~/blog
Engineering notes, written while doing the work.
APIs, tooling, automation, and the small decisions that decide whether software stays maintainable. Written for the engineer who has to keep it running on Monday.
manual / serial MON ─▶ SAP ─▶ handoff ─▶ Excel ─▶ FRI automated / on demand operator ─▶ run ──────────▶ dashboard │ └─▶ Excel └─ failure ─▶ notify ~30 min
From a Week of Handoffs to a 30-Minute Reporting Workflow
A reporting workflow that moved between people for an entire working week became an on-demand 30-minute process by moving stable knowledge into software, removing routine handoffs, and designing a clear path for…
Read article →
unfamiliar repository
│
▼
┌────────┴────────┐
│ run trace map │
└──┬─────┬─────┬─┘
▼ ▼ ▼
facts gaps risks
│
first safe changeThe First Week in an Unfamiliar Codebase: A Practical Discovery Playbook
A useful first week in an existing codebase produces more than notes. It creates a reproducible baseline, a traced workflow, an evidence-backed system map, and a safe first change.
Read article →
request
│
▼
┌────────┐ contract ┌───────┐ data ┌───────┐
│ UI ├─────────▶│ API ├─────▶│ STORE │
└───┬────┘ └───┬───┘ └───┬───┘
│ │ │
└──────── tests + telemetry ───────┘
│
human verifiesWhat Full-Stack Engineering Means in the AI-Assisted Era
AI can generate code across the stack. That makes system understanding, clear boundaries, verification, and operational ownership more important—not less.
Read article →