Chuck C retweeted
Very interested in what the coming era of highly bespoke software might look like.
Example from this morning - I've become a bit loosy goosy with my cardio recently so I decided to do a more srs, regimented experiment to try to lower my Resting Heart Rate from 50 -> 45, over experiment duration of 8 weeks. The primary way to do this is to aspire to a certain sum total minute goals in Zone 2 cardio and 1 HIIT/week.
1 hour later I vibe coded this super custom dashboard for this very specific experiment that shows me how I'm tracking. Claude had to reverse engineer the Woodway treadmill cloud API to pull raw data, process, filter, debug it and create a web UI frontend to track the experiment. It wasn't a fully smooth experience and I had to notice and ask to fix bugs e.g. it screwed up metric vs. imperial system units and it screwed up on the calendar matching up days to dates etc.
But I still feel like the overall direction is clear:
1) There will never be (and shouldn't be) a specific app on the app store for this kind of thing. I shouldn't have to look for, download and use some kind of a "Cardio experiment tracker", when this thing is ~300 lines of code that an LLM agent will give you in seconds. The idea of an "app store" of a long tail of discrete set of apps you choose from feels somehow wrong and outdated when LLM agents can improvise the app on the spot and just for you.
2) Second, the industry has to reconfigure into a set of services of sensors and actuators with agent native ergonomics. My Woodway treadmill is a sensor - it turns physical state into digital knowledge. It shouldn't maintain some human-readable frontend and my LLM agent shouldn't have to reverse engineer it, it should be an API/CLI easily usable by my agent. I'm a little bit disappointed (and my timelines are correspondingly slower) with how slowly this progression is happening in the industry overall. 99% of products/services still don't have an AI-native CLI yet. 99% of products/services maintain .html/.css docs like I won't immediately look for how to copy paste the whole thing to my agent to get something done. They give you a list of instructions on a webpage to open this or that url and click here or there to do a thing. In 2026. What am I a computer? You do it. Or have my agent do it.
So anyway today I am impressed that this random thing took 1 hour (it would have been ~10 hours 2 years ago). But what excites me more is thinking through how this really should have been 1 minute tops. What has to be in place so that it would be 1 minute? So that I could simply say "Hi can you help me track my cardio over the next 8 weeks", and after a very brief Q&A the app would be up. The AI would already have a lot personal context, it would gather the extra needed data, it would reference and search related skill libraries, and maintain all my little apps/automations.
TLDR the "app store" of a set of discrete apps that you choose from is an increasingly outdated concept all by itself. The future are services of AI-native sensors & actuators orchestrated via LLM glue into highly custom, ephemeral apps. It's just not here yet.
A prototype is worth a thousand meetings. Prototypes are so easy to make now, there’s zero reason not to do it.
Started to quickly vibe coding prototypes for every new major features to align business, design and dev and it makes everything SO much faster.
We are adding a coding section to all of our Product Managers interviews at @Shopify.
We'll start with APM interviews. We expect candidates to build a prototype of the product they suggested in the case interview.
There is no excuse for PMs not building prototypes.
Chuck C retweeted
Pieter has over a thousand concurrent players connected to his game server, an unoptimized Python script running on a VPS, through websockets.
Meanwhile, we have an entire generation of web developers who are led to believe that traditional servers won't scale for their 5 concurrent users.
Chuck C retweeted
There’s a series of tasks where the “delegation overhead” to another person is greater than the time & energy spent in doing it yourself.
There’s serialization overhead (writing down the spec of inputs and outputs), verification overhead, context-switching / async overhead.
I suspect that the end-state of AI is that the pool of tasks you can do “yourself” (with agents) increases dramatically. This will lead to companies and teams getting dramatically smaller.
x isn't your university library
just vibe here, get inspired, talk shit with people. that's literally it
u shouldn't be here for knowledge, too many of you are :(
7
264
always look for the source
the book, not the summary
the article, not the tweet
the doc, the paper, not the 10min video
4
11
346
Chuck C retweeted
i was wrong about indie startups. i can explain in 2 minutes.
i've been thinking a lot about arc browser lately. it's probably my favorite piece of software built recently.
but they just announced they're building a new ai-first browser. the original arc is basically on life support.
for the makers of arc, this is about scaling their business.
building a beautiful ui on top of chromium might get you a great product. but it won't get you to $100b.
i get it.
arc built something tech twitter fell in love with. including me. it's my daily driver.
but being well-loved isn't enough when you're vc-backed. you need to reinvent the category.
and that's okay. because here's what i've learned:
reinventing a category is a vc-backed startup game.
cash flow is an indie game.
never forget that.
it's a pattern i see everywhere:
notion trades simplicity for ai dreams and a mailbox
wordpress battles lawyers while ghost picks up
i call it the "mirror effect":
every time a vc startup is forced to reinvent, they create a $1-100m opportunity for indie founders.
the math is simple:
• vcs need billion-dollar exits
• small markets don't work
• original users get abandoned
• someone needs to serve them
smart indie founders don't compete with vc dreams.
they inherit the forgotten users.
the playbook is obvious:
1. build what made the original special.
2. serve the users who hate "progress."
3. stay "small" and profitable.
you don't need to be a unicorn when you're making $10m arr with 80% margins.
sell that business for $50m-$100m. no investors.
there's a fortune in forgotten users.
and they're just waiting for someone to serve them.
i love arc. i hope it stays. but if it changes course, someone will continue that legacy.
maybe it should be you.
i used to think indie startups had to avoid competition with giants, but now i see they can win by embracing the forgotten markets.
some of the best opportunities aren't in the "next big thing."
they're in the markets vcs consider too small.
while everyone else chases billions
you can build a beautiful business serving the forgotten millions.
no right or wrong approach.
choose what excites you the most.
go big or go home.
or go small or go home.
each is beautiful in its own way.
what game do you want to pick?




















