Vaishnav

AI addict

[Vaishnav @0xztp]

@karthikponna19 You can send it to my USDT address

0x16e3d646F42fC04063e01f566c8558c1BAd3a3E4

[Vaishnav @0xztp]

solo built a centralized exchange with a real-time matching engine

skinned it like super mario because normal UIs are boring

this is what overengineering a side project looks like ↓

[Vaishnav @0xztp]

Kimi 2.7 came in 2nd place on a math test, beating most other AIs but losing to Fable 5

https://t.co/nGiRqgYwFy

[Vaishnav @0xztp]

China's new AI (GLM 5.2) beat the US-banned Fable 5 on key benchmarks at a fraction of the cost, showing that banning AI doesn't stop competitors
https://t.co/mrb1R6Fo9k

[Vaishnav @0xztp]

OpenRouter launched Fusion API

it combines multiple cheaper AI models together to match the smartest AI (Fable 5) at half the price.

Three budget models working as a team beat top solo models like GPT-5.5 and Opus 4.8.

Teamwork wins

https://t.co/1c7ColNo6U

[Vaishnav @0xztp]

Kimi K2.7 Code just got a HighSpeed mode and it's 6x faster now
https://t.co/JueGMOxFJH

[Vaishnav @0xztp]

@importdhruv my dad's knows a guy

[Vaishnav @0xztp]

is he JSON mandela ?

[Sagar🇮🇳 @sssaaagar]

Reality. Potential

[Vaishnav @0xztp]

@amritwt Where Ronaldo gets injured

[STONERS R US 🍃 @_StonersRUs_]

World Cup 2026 🏆

[Vaishnav @0xztp]

@amritwt Real

[Vaishnav @0xztp]

Before you build ANYTHING, ask yourself these 5 questions:

1️⃣ Who actually has this problem?
2️⃣ Will they pay to fix it?
3️⃣ What’s the smallest version I can test?
4️⃣ How will I know if it’s working?
5️⃣ What happens if no one cares?

Skip this checklist → waste months building the wrong thing.

Do it first → save yourself the heartbreak. 💔

[Vaishnav @0xztp]

@ohshinbhat can you reffer me at your company sorry ex company plss

[Vaishnav @0xztp]

10. Run a post-launch review Track the KPIs from

step 1. Did it actually work?

If something broke → run a blameless postmortem.

Don't blame people. Fix the process.

[Vaishnav @0xztp]

9. Set up observability Logging.

Metrics dashboards.

PagerDuty-style alerts.

SLAs (Service Level Agreements) and SLOs (Service Level Objectives) define how reliable you promise to be.

You should know it's broken before your users do.

[Vaishnav @0xztp]

8. Ship with canary releases (Gradual Rollout) Never flip 100% on at once.
Use feature flags.
Roll out 5% → 25% → 100%.
Watch error rates.
Roll back instantly if something's off.

[Vaishnav @0xztp]

7. Use a staging environment A near-identical copy of production.

Deploy here first.

This is your QA (Quality Assurance) layer.

Test like it's real —> because it almost is.

[Vaishnav @0xztp]

6. Set up CI (Continuous Integration) Tests, linter, type checker auto-run on every push.
Nothing merges if the pipeline is red.
Zero exceptions.

[Vaishnav @0xztp]

4. Set up the scaffolding (Project Skeleton)
Repo structure, CI/CD pipeline , linting, testing framework, env configs (dev/staging/prod).

All before feature code.
Feels slow.
Pays for itself in 48 hours.

[Vaishnav @0xztp]

5. Build with PRs (Pull Requests) Small commits.
One thing per PR.

Every PR gets a code review.

Write unit tests WITH the code, not "later."

Later = never.