Hey, I’m Shrijit — I’m building at the crossroads of Web3, AI, and Full-Stack Development.
Here you’ll find:
✨ Cool AI & blockchain updates
💻 Bite-sized dev tips
🛠 My own builds (wins & fails)
If you love tech or just want to see what’s next — welcome ⚡
Got asked this in a system design interview:
LLM costs $0.40/query.
100K queries/day → $40K/day.
Logs show ~60% are just variations of the same ~200 questions.
Yet we generate a fresh response every time.
How would you cut cost by 60% without users feeling it’s cached?
I’ve been testing out the patterns from https://t.co/MSjFjey7Eu and they are a total game changer for agentic workflows.
It makes building complex autonomous agents feel way more structured and manageable. Definitely worth a look if you're building in this space. #AIBoom
Claude now connects to the tools creative professionals already use.
With the new Blender connector, you can debug a scene, build new tools, or batch-apply changes across every object, directly from Claude.
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.
Hey
@X algorithm,
I'm looking to
#connect with the people who are interested in :
- Frontend
- Web3
- Backend
- Full stack
- DevOps
- Leetcode
- AI/ML
- Data Science
- Freelancing
- Startup
Launching your MVP this week? Read this before you regret it. 🧵
Most founders don’t fail at launch…
They fail 48 hours after launch.
Here’s the exact 6-step pre-launch checklist we’re using before shipping our app:
- Observability (Don’t fly blind)
If users hit bugs before you see them → you lose.
→ Setup Sentry (errors)
→ Setup PostHog (user behavior)
- Security (People WILL try to break your app)
→ Validate every input (NoSQL injection is real)
→ Add rate limiting (bots are faster than you)
→ Lock CORS properly
- Auth Edge Cases (Silent killers)
This is where apps randomly break.
→ JWT expiry
→ Refresh tokens
→ Google/Auth data mapping
- App Store Reality Check ⚖️
If you're building a social/dating app:
Apple/Google WILL reject you without:
→ Delete Account
→ Block User
→ Report System
(No exceptions.)
- Stress Test BEFORE users do
Your API isn’t ready just because it works locally.
→ Simulate load (k6 / Artillery)
→ Test 500+ concurrent users
→ Watch DB choke in real time
- Legal + SEO (Most people ignore this)
→ Privacy Policy + Terms = mandatory
→ Setup Google Search Console
→ Start ranking from Day 1
We’re shipping our MVP this week.
This checklist probably saved us weeks of chaos.
Bookmark this. You’ll need it. 🚀
#buildinpublic #startup #webdev #indiehackers
Vibe Coding lessons I learnt the HARD WAY ( Extended Edition )
Bookmark this to 10X your workflow
DO's (What Actually Saves You Time)
> Use ready-made auth (Clerk / Supabase Auth)
> Use Tailwind + shadcn/ui for UI
> Use Zustand / Server Components for state
> Use tRPC / Server Actions for APIs
> Deploy with Vercel one-click
> Use Prisma + managed Postgres
> Validate with Zod + React Hook Form
> Use Stripe for payments
> Add Sentry / error tracking early
> Set up analytics (PostHog / Plausible)
> Store secrets in env files
> Use UploadThing / Cloudinary for files
> Set up preview deployments
> Use component libraries (Radix / shadcn)
> Write a README from Day 1
> Keep folders clean and modular
> Add onboarding + empty states
> Use Lighthouse / performance tools
> Use a monorepo or clear app structure from the start
> Document your env vars in .env.example
DON'Ts (What Burns Your Time & Energy)
> Don't build auth from scratch
> Don't write raw CSS for everything
> Don't over-engineer state management
> Don't build custom APIs too early
> Don't deploy manually
> Don't write raw SQL everywhere
> Don't build your own payment system
> Don't roll your own search engine
> Don't skip logging & monitoring
> Don't hardcode API keys
> Don't DIY file uploads
> Don't push straight to main
> Don't build realtime systems alone
> Don't ignore performance
> Don't assume users "will figure it out"
> Don't postpone refactoring forever
> Don't rely on memory for decisions
> Don't chase "perfect" before shipping
> Don't skip error boundaries and fallbacks
> Don't forget a health check endpoint