web3 technology and UX partner for companies and DAOs
Joined March 2024
- Tweets 65
- Following 46
- Followers 85
- Likes 39
16 Photos and videos
May 6
A protocol we operate infrastructure for had a 9.5-hour outage last quarter.
The actual fix took a few minutes. The rest of the nine was an alert that sat unread from 00:30 until someone saw it at 09:00. The technical cause: 250GB of old database schemas accumulated over months. A cleanup script existed. It just hadn't been scheduled.
Both root causes converge to one missing branch in the decision tree: who owned this, by when, with what threshold.
Engineering rarely fails at engineering. It fails at ownership boundaries nobody drew. Code shipped without a clear answer to "who pages at 00:30?" is code preserving the absence of that decision.
That's the work a Sprint Zero exists to surface. Before it shows up at 00:30.
1
93
Apr 30
1/ A client on working with us:
"The abyss between a supplier that delivers what you asked for, and one that asks why you want that in the first place, understands what you actually need, and builds that instead."
1
57
Apr 30
3/ We can't work like that. Half the time the most useful thing we do early is push back on what we were hired to build.
The answer might be smaller, a different shape, or upstream of a problem you haven't named yet.
1
31
Apr 30
4/ That feels like friction at the start. It saves you from the version you'd be paying to rebuild a year in.
If the thing you want built feels like a symptom, the real project is probably a different one.
24
Apr 28
1/ Shipped and solved aren't the same word. Merging PRs and calling it done is how the real cost gets buried.
1
34
Apr 28
4/ Most of what software costs lives in the gap. Not writing the code. The second pass nobody scoped, the one that turns "it works" into "it works for people who actually use it."
1
21
Apr 28
We don't get paid for shipped. We get paid for solved. Harder commitment. Also the one you're not paying somebody to rebuild in six months.
18
Apr 22
Most people treat Discovery as prep work.
What it actually produces is a decision on what to build, why, and what the architecture has to support.
Skip it, and those decisions still get made. Just later, under pressure.
3
49
Apr 17
You can ship on time, follow every requirement, and still miss the point entirely.
The spec was right. The build was clean. The problem is still there.
1
3
48
Apr 17
What changed: a team that thought about what the feature meant for the whole platform before touching the code.
Not after the scope was locked. Before.
1
15
Apr 15
Two bets for 2026: the Brazilian market and the AI x crypto interface.
Full clip with Pedro from @moic_digital below!
8
71
Apr 14
Most teams don't fail because of bad engineers or bad PMs.
They fail at the boundary between the two, where nobody is paying attention!
Full post below 👇
1
7
54
Apr 14
1
21