11 Years in Tech | Backend | System Design | AI Building https://xitter.cf/t.co/YyyZZNpQyL DM For Collab & work📩
Joined February 2026
- Tweets16.1K
- Following807
- Followers3K
- Likes16.8K
Vikash Singh Tomar retweeted
Your environment variables are encrypted.
Your deployment platform gets compromised.
Some secrets may still be exposed.
Railway's latest security incident is a reminder:
Encryption matters. But credential security doesn't end there.
If you use Railway, rotate your secrets and review your API usage.
Don't wait for an unexpected bill to find out your key was exposed.
Official source: blog.railway.com/p/security-…
Encryption protects secrets at rest. It doesn't guarantee they stay safe after deployment.
Rotate your keys, audit access, and monitor usage.
More autonomy means a bigger attack surface. Secret protection needs to be built in from day one, not bolted on later.
No. A larger context window means more information can fit, not that the model can reliably retrieve every detail. Context size ≠ perfect memory. 💯
Use an atomic database transaction with a conditional update. The first driver to claim the ride wins; all others get rejected. Enforce it with optimistic locking or a unique constraint.
Vikash Singh Tomar retweeted
You build a food ordering app.
Friday 8 PM: dinner rush.
100,000 users open the app at the same time.
Every user hits the "Restaurants near me" API.
Same query. Same area. Same results.
100,000 times.
Database is sweating.
Restaurants list changes once every few hours.
How do you handle this load without upgrading the database? 🤔
Reminder that keeping dependencies updated is part of security, not just maintenance. Patch first, investigate later.
The leading wildcard kills index efficiency. Use a sargable condition or a functional index if your DB supports it.
You build a food ordering app.
Friday 8 PM: dinner rush.
100,000 users open the app at the same time.
Every user hits the "Restaurants near me" API.
Same query. Same area. Same results.
100,000 times.
Database is sweating.
Restaurants list changes once every few hours.
How do you handle this load without upgrading the database? 🤔
Execution. Everyone has access to AI, but not everyone knows how to use it to build something valuable.