varun

i'm varun, 19. backend & devSecOps Engineer at DynTech. building CDeX while studying CS full-time. I spend my time on backend internals, infra, distributed systems, and shipping under pressure. from not knowing loops to building real systems. Just gettin started. varunnn.tech/blog/intro-blog

mind you, to this day, ISRO pays 0 rupees to undergraduate students to work there + no accomodation + no food arrangements are given I dreamed as a kid to work at ISRO, it was my literal dream as a kid, it's not viable for any kid to dream to work at a place which pays a lumpsum of 0 RUPEES to work there

@RhysSullivan hahah true af lol

this is the linkedin 'open to work' banner of github

@TimsBila didnt got one

@VarunSheesh Hello, check your DM

Everyone wants to be part of a startup. Until they realize it means actually building one. We’re 4 working professionals building a social app on the side, and we’re looking for one UI/UX designer who’s willing to collaborate, learn, and actually ship. You don’t need to give us 5 hours a day. If you can consistently spare even 30 minutes, that’s enough. We’re not looking for someone chasing a fancy title or waiting for perfect conditions. We’re looking for someone who’s curious, reliable, and wants to build alongside people who’ve already been shipping products professionally. If that sounds like you, my DMs are open. If not, keep scrolling.

@classic_servers yepp dm’s are open

@VarunSheesh can you open DM

@vibewithfidelis dm’s are open

@VarunSheesh Sounds good. Dm

@darijan___ @8xsocial github.com/Varun5711 intrested ~

We're hiring. No degree requirements. No age requirements. No endless interviews. Just 2 weeks of building together. If you like 8x and we like you, we keep building together. @8xsocial isn't for everyone. It's for people who are hungry and want to build something huge. This photo was taken yesterday at midnight while we were still in the office. If that doesn't scare you... You might be a good fit 😉

@code_bytein true, its simple if u don’t face why the particular thing was slow and why you would upgrade to another methods

Most developers learn system design backwards. They start with: Kafka. Redis. Kubernetes. Microservices. But the real order is: 1) Make it work Single server. Single database. Ship it. 2) Make it correct Add caching. Fix slow queries. Handle errors. 3) Make it fast Indexes. Connection pooling. CDN. 4) Make it scale Load balancer. Read replicas. Sharding. 5) Make it resilient Circuit breakers. Retries. Failover. Most systems never need step 4 or 5. Most developers jump straight to them anyway. Complexity is not architecture. It's just complexity.

building a social app where our main kpi is how fast we can get you to close the app and go outside is kinda funny. we’re onboarding our first users soon. if you want a spot, register for early access at talphy.com

@anurag__kochar with a vibecoded website 😭🙏

so basically it's an openrouter clone... america aajkal chup hi rehta hai 🥀

peak's backkkkkk

We have thousands of "connections" and "followers" online, but when was the last time you met someone new in real life? Every modern app is a trap designed to maximize your screen time. It’s making us isolated. That's why we built Talphy. A platform meant to get you off your phone, go check it out drop your email on the waitlist and secure early access talphy.com

Stop doing DevOps in 2026 like it’s still 2019 “I installed Prometheus, I’m done” mode. Do this instead. 1. Infra & environments - Pick one app (Django, Node, whatever) and run full infra as code: Terraform for VPC, subnets, RDS, S3, IAM, ALB. Separate dev/stage/prod. Remote state, workspaces, basic policies. - GitOps it: ArgoCD or Flux syncing a k8s cluster, PR-based changes only. Feature flags, blue/green or canary on the same app. - Break it: Rotate RDS password with zero downtime. Kill a node, test pod disruption budgets and readiness checks. 2. Observability & SRE basics - Full stack tracing/logs/metrics, not just “Grafana looks nice”: OpenTelemetry everywhere. Central log pipeline with Loki/ELK. RED/USE dashboards for one service. - Error budget for a real endpoint: Define SLOs on login or checkout. Hook alertmanager / PagerDuty. Tweak alert noise based on incidents. - Run a game day: 500s from a dependency, DNS failure, Kafka lag. Do postmortems. Improve runbooks, dashboards, and alerts. 3. Platform & AI-in-prod glue - Build a small internal “platform”: Simple API for app teams: namespace per team, default network policies, autoscaling, shared postgres, S3 buckets. Self-service templates using Helm or Backstage. - Add an LLM service like any other workload: vLLM or Ollama in k8s. GPU node pool. HPA on QPS or latency. Token usage, cost per request, and rate limiting in the gateway. - Wire it all together: CI/CD with GitHub Actions/GitLab. Image signing, basic SBOM. Canary deploys, quick rollback, feature flag switch. Keep in mind for any DevOps project: - Always have IaC, not click-ops. - Put rate limiting, caching, and health checks in front of everything. - Think SLOs first, dashboards second. - At mid/senior, focus more on k8s, load balancing, multi-tenant clusters, and infra reliability than pretty project names. Instead of paying $100 on random certs, burn that on cloud credits, RDS, EKS/GKE, and a cheap GPU box. Use Claude/ChatGPT as your pair SRE: design docs, runbooks, incident drills. Ask annoying “what if this dies?” questions until the system is boring.

Guys waitlist's is open go check it out!!🚀

@dodopayments I still prefer @Razorpay ✌🏻

Indian AI founders: stop building billing from scratch. Subscription, usage, credit, hybrid — all pre-built. Integrate in 5 lines.

Post a random picture you took on your phone.

ditch tinder and hinge, make irl connections instantly n meet irl. waitlist’s open at talphy.com

well you can go for AI engineering there’s a playlist by @sriniously backend from first principles, make notes, make projects on ur own applying the theory , then after you get a good hold in backend refer this aiengineeringfromscratch.com for AI engineering (grind dsa lil bit side by side if possible as well)

@VarunSheesh I'm so confused between choosing my domain i explored from my first year ,now I guess I like AI domain but still i do like web development too ,any suggestions pls ,now I'm entering into my third year

If you had 6 months to become job-ready in tech, what would you prioritize? DSA Projects Open Source AI/ML System Design

anyone out there who still writes code with their fingers :/

My little escape