Learning AI, on purpose
AI is moving faster than any of us can passively absorb. So I stopped trying to absorb it and started learning it deliberately — as a backend engineer, on purpose, a piece at a time.
Owning systems end to end — clean APIs, workflow automation, and the lessons the work teaches.
AI is moving faster than any of us can passively absorb. So I stopped trying to absorb it and started learning it deliberately — as a backend engineer, on purpose, a piece at a time.
A workflow engine for enterprise service requests — multi-level approvals, SLA tracking, SOP scheduling across time zones. The hard part isn't the automation. It's deciding what stays human.
Across a few backend systems I've shipped 70+ REST APIs. The endpoints blur together; the principles don't. A field guide to the ones that survived contact with production.
I spent a couple of years writing documentation for complex engineering systems before I built them. It turns out explaining a system clearly is the best possible training for designing one.