Topic
API design
4 posts on this topic. All of them come out of work I have actually shipped.
-
Writing MCP tools an agent picks correctly
The tool name, description and schema are the interface. What the protocol guarantees, what it only hints at, and why the server still has to check everything.
Read it
-
What to do about a webhook that arrives twice
Duplicate deliveries, no ordering guarantee, and a signature you have to check yourself. The handler shape that survives all three.
Read it
-
Designing a REST API other people can actually use
Naming, status codes, errors, pagination, and versioning decisions that save your consumers from guessing.
Read it
-
Validate API input before it reaches your database
A practical pattern for Pydantic models at the API boundary, and why coercing bad data is worse than rejecting it.
Read it
Next step
Looking for someone to own this end to end?
I am open to full-stack engineering roles and to contract builds. Tell me what you are trying to solve and I will tell you honestly whether I am the right person for it.
- Replies: Within two working days
- Based in: the United States
- Open to: full time, contract, remote or hybrid