@westurbergin@PedroNeverFolds@andonlabs That was the other experiment, there was a real vending machine in the office, but employees gaslighted claude into giving everything away for free in the span of a week
@theo 4. End to end not so much, fable was able to build a decently strong chess engine, but nowhere near stockfish. With human creativity and intellect it can do 100x more then with loops and stuff, just as any tool
@theo Your questions:
1. My code contain CVRP SISR, but missing VRPTW SISR. Use existing code as a guide and build working VRPTW SISR, run the benchmarks and validate the result
2. Claude code cli
3. Opus 4.8 with codex plugin (5.5 low for codex)
@xikhar I just don’t see them thinking about profiting from b2c. 200$ only purpose is to divide real customers that can convince their company to buy anthropic team/enterprise from antigravity larpers. I think subs end with one company dominating the sector.
Postmortems are underrated
You can read every diagram in the world, but nothing teaches you distributed systems faster than seeing exactly how Cloudflare or Discord took down their own system.
Here are 5 postmoderns you should read:
1. https://t.co/OxEN8F6kr6
Postmortem of database outage of January 31 (A great example of transparency, detailed timeline, and clear lessons learned)
2. https://t.co/ev7vEWOThx
Slack’s Incident on 2-22-22 (A strong example of how cascading failures happen in complex systems)
3. https://t.co/yVWHoXLogs
Meta - More details about the October 4 outage (A useful postmortem for understanding network failures at scale)
4. https://t.co/CZGQyP2Iyy
Post mortem on the Cloudflare Control Plane and Analytics outage (A good example of connecting outage cause, recovery, and follow-up fixes)
5. https://t.co/4hKtXrqjw4
AWS Post-Event Summaries (A solid resource for studying how large platforms document incidents consistently)
This is where your thinking starts to mature.
You stop asking only how the system should work and start asking how it fails.
If you have another good share here.