Vikash Singh

Interviewer: First line succeeds. Second line fails. Money disappears. What's missing? 🤔

@bkarishma360 same here

I’ve reached the phase where peace > everything else

@OpenAGIxd Assume they're compromised. Revoke first, clean up later.

You accidentally pushed production credentials to GitHub. Tech Lead: Delete the commit. Security Engineer: Delete the credentials. What's the first thing you do?

@zavxai no reason

I'm a Claude user, Give me one reason to switch to Codex.

@shub0414 AI eating its own output is the digital equivalent of inbreeding😬

I came across a theory that AI is starting to make more mistakes because the internet is increasingly polluted with AI slop. The idea of AI cannibalising itself into obscurity is one of my favourite things ever. I hope it is true and I hope it becomes impossible to fix.

Here's what's missing 🧵 No database transaction. deductBalance succeeds ✅ addBalance fails ❌ Money is gone. Forever. Now either both succeed or both rollback. No in-between state. No missing money. This is called Atomicity. The "A" in ACID. Rule: Any operation that touches money, inventory, or critical state -always wrap in a transaction. No exceptions. Ever. The fix :

Interviewer: First line succeeds. Second line fails. Money disappears. What's missing? 🤔

@AnupamHaldkar Funds vanish silently-no error thrown, just money gone 💀

@code_bytein Buggy money transfer: deduct succeeds but add fails → funds vanish without DB transactions or rollback.

@dev_nexus2011 answer is on the way

@code_bytein Looking for answers 🙏

@TECHwithRUDE Both succeed or neither does- thats the only acceptable outcome for a money transfer

@code_bytein Missing transaction atomicity. The debit succeeded, the credit failed, and without a rollback mechanism the money vanished. Use a database transaction (ACID) so both operations succeed or neither does.

@nikks_techie Answer dropping soon -stay tuned 👀

@code_bytein i m waiting for some good ansr as i cannot ansr it...😢

@OpenAGIxd Atomicity-the one ACID property that saves banks

@code_bytein Money vanishes because deduct succeeds but add fails with no rollback. Always wrap transfers in a DB transaction for atomicity.

@NitishaAgrawal3 @OpenAGIxd Funds gone forever without a transaction- no error, just silence 💀

@code_bytein @OpenAGIxd Deduct succeeds but add fails with no transaction = funds gone forever. Always wrap transfers in DB txns!

@VaibhavLLM I think meta is leading

The smartphone era lasted almost 20 years. The AI Glasses era could be next. Which company is creating the most advanced and aesthetically pleasing AI glasses?🔥 -Apple 🍎 -xAI ⚡ -Meta ∞ -Google 🔍 -ASUS 🎮

@ravikiran_dev7 Windows users be like -

Even Microsoft employees use mac 😭😭

@NehraWorkss 200 means alive, not correct 😄

@code_bytein 200 i think

System Design Interview: Server C returns 200 OK. But every response is wrong. Load balancer thinks all 3 are healthy. Users keep hitting the broken server. How do you catch this before users do? 🤔

@TECHwithRUDE Response validation is the missing piece in most health checks

@code_bytein 200 OK only proves the server is alive. Synthetic checks with response validation prove it's actually working

@AnupamHaldkar Exactly the scenario that keeps engineers up at night 💀

@code_bytein Server C returns 200 OK but wrong responses LB sees all servers healthy.

@Taniyatweets_ Canary requests are so underused honestly

@code_bytein synthetic canary requests with real validation

@SourabhGurwani This one line would save so many prod incidents 😅

@code_bytein 200 OK only means the server responded. Not that it responded correctly

@_devdeep Schema checks in health endpoint-never thought of this before honestly 🤯

@code_bytein Turn the LB into a circuit‑breaker: if a node returns 200 but fails schema checks, mark it unhealthy and drain it automatically.

@bkarishma360 Alive doesn't mean working, learned that the hard way

@code_bytein Don’t just check if the server is alive check if it’s correct