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 gradients.sh, 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: github.com/supabase/supabase

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.

extremely high performing, safe, good looking apps can be built with Opus 5.5 without ever reading code—from scratch there is no tech debt if you dont look at the code what are yall waiting for anons? go out and ship

Please pangram itself is not that accurate. It is literally known for false positives. This is literally in their research paper. Just saying, you never know the one email that may change things

Six projects from the last few weeks that caught our attention: A wildfire analysis prototype that maps the fire’s spread over time and tracks hot spots, made with Opus 5.5.

can't believe im doing this