x.com/i/article/2022…

Built sth in Replit ⠕ , worked on dev. Ship it, right? Ship ≠ build. Ship = refuse to stop. The last weekends and late nights looked like this: The AI voice app interrupted itself on iPhone speakers. I fixed the echo. Fixed it again. Then threw away that approach entirely and

The old carpentry rule applies to vibe-coding too: Think twice, prompt once. But also: most of those 25 fixes? I caused them by jumping straight into code. Before you prompt the AI to build something, I now spend 5 minutes asking: - What happens when the user actually interacts

Trend I'm seeing in the Valley: the latest AI-native startup teams are all building their own internal tools, 100% customized for their needs, instead of buying SaaS. Do not dismiss these as vibe coded slop. They are built by professional internal developers dedicated to

positively surprised by this delightful valentines gift. such a unique brand PostHog.

think twice prompt once.

x.com/i/article/2025…

x.com/i/article/2025…

Something fascinating happened when ‚vibe coding‘ graduated to ‚personal software‘: emergence of features through use. OpenClaw showed that all you need is memory, cron jobs and tools in a loop. So the good news for builders: it doesn’t take a large training cluster.

„AI made building free and distribution harder than ever. Everyone ships now. Good luck getting anyone to notice.“ True. Also maybe true: MCP descriptions become the new SEO for agents.

PMs don’t just ship features. They kill them. Shipping isn’t the job. Shipping the right product is. A great PM doesn’t fall in love with the roadmap. They fall in love with the problem and have the guts to say: This isn’t solving it. This adds complexity. This doesn’t matter.

solo founders in 2026: engineering spec → openclaw → marketing content your engineering docs are literally your content gold mine extremely context dense, and the "why we built it this way" becomes content your audience actually wants to know today it explained why our

I’m ready to wear my agent harness as a contextual meat suit. Years of groggy morning journaling included.

“Your idea is actually a trend”

x.com/i/article/2027…

Think like an agent. Or: the Goldilocks zone of tool calling.

Fascinating read on the great transition (that really is a set of smaller transitions): Specialised knowledge becomes open domain, interfaces become agent-native, enterprises become skill graphs.

x.com/i/article/2028…

x.com/i/article/2028…