11 Years in Tech | Backend | System Design | AI Building https://teapawt.org/t.co/YyyZZNpQyL DM For Collab & work📩
Joined February 2026
- Tweets16.3K
- Following813
- Followers3K
- Likes16.8K
Pinned Tweet
Tech Lead says:
Never use boolean flags in your database.
Junior dev: But isActive, isDeleted, isPaid is so simple.
Tech Lead: What happens when business logic needs a third state?
Junior dev: 😶
Do you know what the Tech Lead meant? 🤔
Vikash Singh Tomar retweeted
Your code isn't the only thing attackers want.
API keys, AI session tokens, and cloud credentials can be far more valuable than the code itself.
That's why security needs to go beyond the browser and cover your entire development environment.
Protect your secrets before they become someone else's access.
Your secrets don't live in just one place.
-> Browser: catches keys before you paste into AI tools
-> Desktop: anonymises exposed secrets locally
-> Dashboard: tracks it all for your team
One tool. Every surface.
Start free -> secureintent.ai
Your code isn't the only thing attackers want.
API keys, AI session tokens, and cloud credentials can be far more valuable than the code itself.
That's why security needs to go beyond the browser and cover your entire development environment.
Protect your secrets before they become someone else's access.
Your secrets don't live in just one place.
-> Browser: catches keys before you paste into AI tools
-> Desktop: anonymises exposed secrets locally
-> Dashboard: tracks it all for your team
One tool. Every surface.
Start free -> secureintent.ai
Vikash Singh Tomar retweeted
Your laptop is more than a coding machine.
It may hold:
-> Cloud credentials
-> AI session tokens
-> API keys
-> SSH keys
-> Browser sessions
New infostealer research shows attackers are targeting developer keyrings and AI assistants.
One compromised endpoint can expose far more than your source code.
🔐 Protect your credentials.
🔄 Revoke compromised keys.
🤖 Keep secrets out of AI prompts.
Your code isn't the only thing worth protecting.
Vikash Singh Tomar retweeted
Still hand picking UI components?
Now no need to do it .
Check out Avara UI.
@Pranto39
I stopped hand-picking UI components.
Now my AI agent builds the page for me, using redesigned @shadcn /ui-based components, through MCP.
Meet AvaraUi.com : → 189 components → 24 website sections & app blocks → AI agents MCP support → Built on shadcn/ui
100% free. Try it now AvaraUi.com 👈
Still hand picking UI components?
Now no need to do it .
Check out Avara UI.
@Pranto39
I stopped hand-picking UI components.
Now my AI agent builds the page for me, using redesigned @shadcn /ui-based components, through MCP.
Meet AvaraUi.com : → 189 components → 24 website sections & app blocks → AI agents MCP support → Built on shadcn/ui
100% free. Try it now AvaraUi.com 👈
Vikash Singh Tomar retweeted
I stopped hand-picking UI components.
Now my AI agent builds the page for me, using redesigned @shadcn /ui-based components, through MCP.
Meet AvaraUi.com : → 189 components → 24 website sections & app blocks → AI agents MCP support → Built on shadcn/ui
100% free. Try it now AvaraUi.com 👈
Vikash Singh Tomar retweeted
Product exists -> 200 OK.
Product doesn’t exist -> 200 OK, body: null.
Frontend shows a blank page.
Monitoring says everything is healthy.
Nobody gets an alert.
Same endpoint. Same code.
Zero errors anywhere.
What’s wrong? 🤔
Product exists -> 200 OK.
Product doesn’t exist -> 200 OK, body: null.
Frontend shows a blank page.
Monitoring says everything is healthy.
Nobody gets an alert.
Same endpoint. Same code.
Zero errors anywhere.
What’s wrong? 🤔
Vikash Singh Tomar retweeted
Everyone’s building AI features.
Almost nobody is testing them.
With normal code, a test passes or fails.
With AI:
-> Same input, different output.
-> “Works” depends on who’s reading it.
-> It’s fine in the demo, wrong in production.
If you can’t measure whether your AI feature got better or worse after a change, you’re not engineering it.
You’re hoping.
Everyone’s building AI features.
Almost nobody is testing them.
With normal code, a test passes or fails.
With AI:
-> Same input, different output.
-> “Works” depends on who’s reading it.
-> It’s fine in the demo, wrong in production.
If you can’t measure whether your AI feature got better or worse after a change, you’re not engineering it.
You’re hoping.
Vikash Singh Tomar retweeted
(1/3) - AIBEAT
An open-source framework for testing LLM security and agent behavior, with PromptBeat for adversarial testing and AgentBeat for tracing what actually happens during execution.
Vikash Singh Tomar retweeted
Backend developers don’t get paid for writing code.
They get paid for what happens when the code meets reality.
Reality is:
→ Users who click twice.
→ Networks that drop mid-request.
→ Data nobody told you could be empty.
→ Traffic nobody planned for.
Anyone can write the happy path.
The job is everything else.
Backend developers don’t get paid for writing code.
They get paid for what happens when the code meets reality.
Reality is:
→ Users who click twice.
→ Networks that drop mid-request.
→ Data nobody told you could be empty.
→ Traffic nobody planned for.
Anyone can write the happy path.
The job is everything else.
Vikash Singh Tomar retweeted
Same paste. Two outcomes.
Left: your API key goes straight to an AI tool.
Right: SecureIntent catches it before you hit send.
On-device detection. Chrome & Firefox. Free to start.
Which developer are you? 👇
secureintent.ai
Vikash Singh Tomar retweeted
Me: let's build an AI agent to save 10 hours a week
The agent: reads .env, prints my API key, pushes it to logs
Me: spends 12 hours rotating credentials and investigating the incident
AI is incredible 💀
Vikash Singh Tomar retweeted
Your Tech Lead says:
We don't need Redis. The database can handle the traffic.
What's your response? 👀
Your Tech Lead says:
We don't need Redis. The database can handle the traffic.
What's your response? 👀