Sunday, July 12, 2026
Lagos, Nigeria · Digital Edition
Vol. I
I came into software through content marketing, learned to code because explaining other people’s products was no longer enough, and found a career in the borderland between systems and stories.
By Asaboro Daniel
July 12, 2026
11 min read
The territory
Code is the beat.
Everything around it is the story.
Six desks · One working notebook
Turn the page ↓
After building with agents, MCP servers, wallet tooling, and reusable skills, I no longer think the hard problem is making AI do more. The hard problem is making its authority visible.
Read story →
Audited contracts can still sit behind vulnerable interfaces, compromised dependencies, exposed keys, and ordinary operational mistakes. The strongest wall is irrelevant when everyone enters through the side door.
Read story →
Documentation is not the final explanation of a finished product. It is where abstractions meet reality, developer trust is won, and product defects become impossible to ignore.
Read story →
Topics in rotation
Engineering decisions, architecture, bugs, and what the code teaches after it ships.
The Work Around the Code Is the Work →Documentation, developer experience, community, and the work of making tools legible.
Writing for Builders Is Product Engineering →Field tests from working with models, agents, and the new interfaces around software.
Capability Without Constraints Is Not Agency →Work logs, product experiments, launch notes, failures, and unfinished things worth sharing.
Capability Without Constraints Is Not Agency →Essays on technology, creativity, attention, and the ideas I cannot leave alone.
The Work Around the Code Is the Work →Repositories, useful fragments, collaborations, and lessons from building in the open.
Browse the working archive ↗On the workbench · July 2026
Learning
Better systems for AI-assisted software work.
Shipping
Developer experiences with shorter feedback loops.
Writing
Notes from the edge between code and communication.