@thisishars@weswinder 1. you don’t have to sell what you’re building. a product is just an automated version of an outcome. so really you should be selling the outcome to test if people will buy it and then build
2. when you do get to building, you can talk about it as soon as it’s shipped
Day 16/
You can now cache for 12h in the API and for logged in users across Codex & Work we keep cache forever and you don’t have any penalty for coming back to an old conversation or resuming after a few hours and are now guaranteed to hit the cache.
Every landing page has the same flat background.
So I built https://t.co/pdkVQPHKbc, moving gradient backgrounds for any site.
- 207 animated presets
- Tweak colors, speed and grain
- React, Vue, Svelte or plain HTML
- Or ask your agent to add it
39 free, all customizable 👀
i had 12 Claude agents running in parallel for 6 hours and i managed to reverse engineer @supabase
i'm making it available here so that you can save your tokens - 100% free & open-source:
https://t.co/uA7zj7SCV9
@zoidz00@ryanvogel do you want to see the internet with content made by llms only
none of your users are reading code so that's very different. it’s not meant for people
Recently I interviewed a Senior Engineer.
Strong candidate.
Kafka? ✅
Redis? ✅
Microservices? ✅
Distributed systems? ✅
Then I asked:
"You're building the inventory service for a flash sale.
Only 1 item left in stock."
Two users hit “Buy Now” at the exact same millisecond.
Both requests pass the “is available?” check.
Both create an order.
Both deduct stock.
Now you’ve sold 2 items when only 1 existed.
How do you guarantee you never oversell — even with concurrent requests, client retries, and partial failures?
"Just use a database transaction."
Doesn’t fully solve it if both requests read `stock = 1` before either writes, or if the response is lost and the client retries.
"Check stock before deducting."
What happens when both checks happen at the same time?
"Use Redis DECR and reject if it goes negative."
What happens if Redis is down, or the decrement succeeds but the order is never persisted?
Your turn:
How would you design this inventory reservation API so concurrent buyers and retries never oversell the last item?
There’s a specific distributed-systems concept behind this.
And you’ll encounter it everywhere inventory, tickets, seats, coupons, and limited resources are involved.
@dora_lee_1344@hiddnest@AsideAI oh i misread, lol. here
windows 11 25H2, build 26200
i changed my wallpaper to test if it would get more visible maybe and it did! so the effect is there
resolved ✅