Build the magic, borrow the rest
A hackathon is a scoping problem wearing an engineering costume. The three layers every product has, and the four questions that decide which of them you are allowed to write yourself.
Field notes · Crafter Station
Subscribe via RSSWhat we try, what we learn, and what is worth sharing. Engineering and culture from people building in LatAm.
6 articles
A hackathon is a scoping problem wearing an engineering costume. The three layers every product has, and the four questions that decide which of them you are allowed to write yourself.
The borrowed stack is free at a hackathon and stays free longer than most people expect. Real monthly numbers from two products in production, and where the build-versus-buy tradeoff actually flips.
The official Cloud API and QR session wrappers solve different problems and fail in different ways. Groups, ban risk, Meta policy changes, and the decision table we use.
Tool selection changed when agents started writing most of the integration code. Eight questions to ask before adding a dependency, and why documentation quality is now a performance characteristic.
crafter.run now ships an agents.md, llms.txt, an OpenAPI description and a read-only MCP server. What each surface is for, and the one rule about writing.
Crafter Station is starting to write in public: what we ship, what we learn, and why we picked one thing over another. This is the first post.