I don’t understand: “ I launched PRiority yesterday. From tweet to deployed product in three hours”
Beside a landing page which could be done in Wordpress since years without that much compute power, what is the product?
You raise a great point - and honestly, it's exactly the reaction that validates why this exists.
You're right that the visible part is just a landing page. But that's like saying Stripe is just a payment form, or that Product Hunt is just a list. The innovation isn't the frontend - it's the system underneath.
What I actually built in 3 hours is a "commitment engine". Not a survey asking 'would you use this?' (everyone says yes), but a system that asks 'will you put money behind this?' The difference between intention and commitment is everything in product validation.
Here's what's actually happening:
- In 24 hours, I've collected hundreds of dollars in binding commitments for a product that doesn't exist yet
- Each payment is a data point with skin in the game - real signal, zero noise
- I got real feedback from real users and I am changing the business model and details of the specs of the Github bot as we talk
- The GitHub bot implementation? That's the easy part. I can do that in less than 3 hours. The hard part was proving people will pay for it BEFORE building it
Think about it: How many products die after months of development because nobody actually wanted them? How many 'validate with landing pages' experiments get false positives from people who click 'interested' but never convert?
This flips the entire model. Build nothing → Get paid → Build only what's already sold.
I believe this is the future of how products get built. Not 'build it and they will come,' but 'they came, they paid, now build it.'
so, what's the twist? Once this works, the validation platform itself (product #2) becomes the real business. This would be something like Kickstarter meets AngelList meets GitHub, every idea gets validated with real money before a single line of code is written.
"In 24 hours, I've collected hundreds of dollars in binding commitments for a product that doesn't exist yet " - so the original statement "From tweet to deployed product in three hours" means actually 'from tweet to non-existing product in 3 hours' - so what you spend these 3 hours on? Why you need claude for it? what does this have to do with software?
Talking about the actual development: "The GitHub bot implementation? That's the easy part. I can do that in less than 3 hours." - if you can do so, anyone can do, so why to buy your 'product'?
'build it and they will come,' I think thats a very outdated view - basic marketing classes teach you how to validate your product market fit, especially if you go into new markets.
all in all, "Why Everything You Know About Software Is Now Wrong" just reflects on how you misunderstand profesional software companies - they dont build for fun or try out something new - they build to deliver solutions for customer requirements.
But perhaps I am wrong - perhaps stripe already knows that "everything you know about software is wront", and they dont "spent months planning architectures?" and achieved 99.999 uptime with claude and abit of luck: https://stripe.com/blog/how-stripes-document-databases-suppo... .
I will think about it once again when I stuck in Tokyo underground caus the entire IC system goes down as it was reimplemented within 3 hours by vibe coding :)
I ran it for a couple years. While it had some quirks at the time, it (and the rest of the Hashi stack) were lightweight, nicely integrated, and quite pleasant.
However, it’s no longer open source. Like the rest of Hashicorp’s stuff.
What's the context here? Is this guy just pro free speech and anti immigration? Conservative?
(I don't know anything about him and haven't heard of him before this post. It at least seems more coherent than most political posts we see online these days.)
Atm I have a pool of US and Canada +1 numbers that get randomly rotated to show as the caller ID.
I want to keep it as simple as possible but toying with the idea of letting people add their number as the caller ID, it would involve number verification with an automated call to setup so need to see if it's what people would want?
Yup, but when I've tried gorm this is not generic enough to let me do this nested generically (with relations).
In gorm you can't do Car.update({'soundsystem': [{id: 'bluetoothProtocolId'}]}), you can only do something like Car.Association('soundsystem').update([{id:'bluetoothProtocolId'}]), fundamental difference being that the latter is dealing with Car internals and is not generic.
"Woodpecker" is a good metaphorical name for a Write-Ahead Log (WAL) service for several reasons of Persistent and Reliable. Woodpeckers repeatedly and persistently peck trees, symbolizing the reliability and consistent logging of events or data.
