25 signs your VIBE CODED app will BREAK at 500 users :
Save this before you go live !
1/ no load testing before launch
> you don't know where it breaks because you've never pushed it
> one traffic spike and you're debugging live in production
2/ session data stored in server memory
> works on one instance
> breaks the moment you need two
3/ file uploads going directly to your app server
> disk fills up. server dies. files lost.
> move uploads to object storage on day one
4/ synchronous email sending in API routes
> slow email provider = slow API response for every request that triggers one
> offload to a queue. always.
5/ no queue system for background tasks
> everything blocking
> one slow task pauses everything behind it
6/ hardcoded secrets in deployment scripts
> sitting in your CI logs
> visible to anyone with pipeline access
7/ single database with no read replica
> all reads and writes hitting one machine
> first real traffic spike kills query performance
8/ no CDN in front of static assets
> every image served by your app server
> 500 concurrent users = 500 image requests hitting your backend
9/ DB migrations running automatically on app start
> two instances deploy at the same time
> both run migrations. race condition. data inconsistency.
10/ no database backup ever tested with a restore
> you have backups
> you've never actually restored from one
11/ unindexed foreign key columns
> every JOIN is a full scan
> slow at 100 rows. broken at 100,000.
12/ no rate limiting anywhere
> 500 users. one of them is a bot.
> your server is now a bot server
13/ API responses with no compression
> JSON payloads sent uncompressed
> 10x the bandwidth they need to use
14/ no error alerting configured
> app crashes at 3 AM
> you find out when a user emails you at 9 AM
15/ transactions not used for multi-step writes
> step 1 succeeds. app crashes. step 2 never runs.
> data is now inconsistent permanently
16/ health check endpoint missing
> load balancer sends traffic to crashed instances
> users get 502s. you get support emails.
17/ memory leaks in long-running processes
> memory grows slowly. server hits 100%.
> everything grinds to a halt. restart. repeat.
18/ no graceful shutdown handling
> deploy kills active requests
> users mid-action get errors with no retry
19/ dependent on a third-party API with no fallback
> that API goes down
> your core feature goes down with it
20/ all logs written to local disk
> logs rotate off
> incident happens. no history to debug with.
21/ no circuit breaker on external calls
> external service is slow
> your thread pool fills waiting for it. everything queues.
22/ unparameterized search queries
> search with any real data volume
> 5-second response times at scale
23/ no connection timeout on outbound HTTP calls
> external API hangs
> your thread hangs with it. indefinitely.
24/ WebSockets not handled by a stateful service
> horizontal scale breaks real-time features
> every user gets disconnected
25/ no runbook for common incidents
> something breaks at 2 AM
> nobody knows what to do. everyone panics.
you can ship fast and still build something that holds.
bookmark this before you go live.
Introducing Claude Opus 4.7, our most capable Opus model yet.
It handles long-running tasks with more rigor, follows instructions more precisely, and verifies its own outputs before reporting back.
You can hand off your hardest work with less supervision.
Very soon there are going to be more AI agents than humans making transactions.
They can’t open a bank account, but they can own a crypto wallet. Think about it.
Bought a new Mac mini to properly tinker with claws over the weekend. The apple store person told me they are selling like hotcakes and everyone is confused :)
I'm definitely a bit sus'd to run OpenClaw specifically - giving my private data/keys to 400K lines of vibe coded monster that is being actively attacked at scale is not very appealing at all. Already seeing reports of exposed instances, RCE vulnerabilities, supply chain poisoning, malicious or compromised skills in the registry, it feels like a complete wild west and a security nightmare. But I do love the concept and I think that just like LLM agents were a new layer on top of LLMs, Claws are now a new layer on top of LLM agents, taking the orchestration, scheduling, context, tool calls and a kind of persistence to a next level.
Looking around, and given that the high level idea is clear, there are a lot of smaller Claws starting to pop out. For example, on a quick skim NanoClaw looks really interesting in that the core engine is ~4000 lines of code (fits into both my head and that of AI agents, so it feels manageable, auditable, flexible, etc.) and runs everything in containers by default. I also love their approach to configurability - it's not done via config files it's done via skills! For example, /add-telegram instructs your AI agent how to modify the actual code to integrate Telegram. I haven't come across this yet and it slightly blew my mind earlier today as a new, AI-enabled approach to preventing config mess and if-then-else monsters. Basically - the implied new meta is to write the most maximally forkable repo and then have skills that fork it into any desired more exotic configuration. Very cool.
Anyway there are many others - e.g. nanobot, zeroclaw, ironclaw, picoclaw (lol @ prefixes). There are also cloud-hosted alternatives but tbh I don't love these because it feels much harder to tinker with. In particular, local setup allows easy connection to home automation gadgets on the local network. And I don't know, there is something aesthetically pleasing about there being a physical device 'possessed' by a little ghost of a personal digital house elf.
Not 100% sure what my setup ends up looking like just yet but Claws are an awesome, exciting new layer of the AI stack.
The silent killer poisoning you from within:
Insulin resistance.
38% of Americans have pre-diabetes and most don't even realize...
Here are 5 ways to fix insulin resistance (bookmark this):
Researching several topics today for our new episode of @marketcapping and one is sticking out to me as a major concern.
$stETH / $ETH peg is in rough shape and running out of liquidity fast.
Compiling my thoughts to get more eyes on this... 🧵
How can you improve your personality?
The answer is to develop some micro-routines on the other side of the personality distribution.
So if you're disagreeable, maybe you could start learning how to do nice things for people. (1/5)
Tomorrow, 32 central banks and 12 financial authorities (44 countries) will meet in El Salvador to discuss financial inclusion, digital economy, banking the unbanked, the #Bitcoin rollout and its benefits in our country.
okay so. Multiple people told me Everything Everywhere All At Once was the best movie they’ve seen and I said “we’ll come on, that’s unfair to that movie to set my expectations that high, and there’s no way that’s true.” But I just saw it, and fuck.