Wipro intelligence's HealthAl has created an Al-assisted Clinical Decision Support Systems (CDSS). Now Al and robotics can also diagnose patients in the ot as well. AI + Robotics = 🔥

Day 2 at India AI Impact Summit 2026!! Met the person who taught me DSA when I was in college when I was just trying to be better at coding. Now we’re talking AI, startups and the getting feedback for @turbodeploy from him . @nishantchahar11

Day 2 at India AI Impact Summit 2026!! Met the person who taught me DSA when I was in college when I was just trying to be better at coding. Now we’re talking AI, startups and the getting feedback for @turbodeploy from him . @nishantchahar11

I will be attending the India AI Impact Summit 2026 in Delhi that is happening between 16th to 20th February. If you are coming, comment down. Would love to catch up!!

Pune’s traffic is so baddd

400 cool 🎉

If You Know Python, You Can Become…. - Backend Developer – Build APIs, databases, and server logic - Full-Stack Developer – Backend with Python + frontend integration - Automation Engineer – Automate tasks, workflows, and reports - Desktop App Developer – Create software using

there’s nothing that can beat Apple’s devices ecosystem and Google’s app ecosystem.

only 4 left for 400. can we reach 400 today ?????

Backend feels like home. Frontend infra? Slightly less so. There’s a difference between: - Deploying a React app to Vercel in 2 clicks - Doing it on S3 + CloudFront manually My goal: make TurboDeploy feel like the first, with the control of the second. Let’s see how many

If you deploy a frontend today, where do you usually host it? - Vercel / Netlify - S3 + CloudFront - Some VPS (Nginx/Apache) - Something else Curious how many people actually use S3 in 2026.

lessgoo 🎉 day 20

Backend deploys are mostly solved. Now the next boss fight: Frontend deployment to S3 + CloudFront. New challenges: - Correct MIME types - SPA routing (no 404 on refresh) - Cache invalidation after deploy Basically: making "npm run build" actually reachable worldwide.

Day 20 of building TurboDeploy Backend deploy engine status: - Happy paths: ✅ - Most edge cases: ✅ - A few weird AWS timeouts: still chasing I’m close to a point where I can say: "If your app doesn’t deploy, I can tell you exactly why." That’s the minimum bar. Next up:

Make something cheaper, faster: usage explodes. Cars did that to travel and mobility soared. However horse population fell ~90%.

What’s your favourite logging style? - Plain text - JSON - Structured but human-readable - "Just give me anything, I’ll grep" I’m aiming for something that works in a browser UI and CLI.

lessgoo 🎉 day 19

Good logging feels boring when things work. But it feels like magic when things break. If TurboDeploy can turn a "wtf is going on" moment into "ah, line 3 tells me exactly what broke"… that alone is worth building.

I’m moving logs to a structure like: `[DEPLOY_ID] [STEP] [STATUS] [DURATION] [DETAIL]` Example: `#123 IAM_ROLE_CREATE OK 2.1s role=turbodeploy-app-123` `#123 LAMBDA_DEPLOY FAIL 4.7s reason=missing handler file` One glance should tell you: - Where it failed - How

Day 19 of building TurboDeploy Error handling without good logs is just guessing. Right now I’m fighting two extremes: - Too little logging → no idea what happened - Too much logging → can’t see the signal The sweet spot: - One clear summary line per deploy - Deep details