Why This Blog Uses RSS (Not a Newsletter)
Newsletter platforms promise reach and metrics. They also own the channel. RSS is a protocol — you own the content; the reader owns the experience.
Newsletter platforms promise reach and metrics. They also own the channel. RSS is a protocol — you own the content; the reader owns the experience.
Most companies have a mission. Almost none have a manifesto. Branding is not enough. But why?
The bottleneck moved. Execution got cheap and most builders aren’t optimizing for it. Yet.
AI is getting better at solving it. You still don’t know how. This will keep happening.
You pushed the code, the tests are green, the feature is live — and three days later your audience finds out by accident. Creation and delivery run on different fuels.
Every abstraction introduces rules. If you can explain them in a sentence, your design is mature. If you can’t, something went wrong — and it’s one of three things.
You can have the best product in the world and still lose to nothing. Progress is a balance of forces — here’s the napkin math.
We’ve been told that everything is relative and every truth is just an interpretation. It sounds intellectual, but it’s a trap that keeps you in a loop while the world moves on.
Why focusing first on properly modeling the domain is better than forcing design patterns into your code.
In the vast landscape of business, one truth remains immutable: you can’t negotiate genuine desire. It’s a lesson that traditional industries have tried to bend to their will, and even in the dynamic world of startups and tech products, it’s a concept that refuses to yield.