Nikhil Nagdev

@cyrilXBT Claude

I spent 6 months learning Claude Code the hard way. Every mistake. Every workflow that did not work. Every prompt I had to rewrite 10 times before it clicked. I turned all of it into a free masterclass: THE CLAUDE CODE MASTERCLASS. Zero to shipping your first project alone. No CS degree. No team. No guesswork. Inside you get: - The reframe that changes how you use Claude Code forever - The CLAUDE .md template that makes every session 10x more powerful - The 4-layer prompt architecture that scales to any project - MCP server setup nobody is teaching yet - The 6-phase sequence to go from idea to deployed in a weekend - 10 ready-to-run workflows you can copy right now The people who read this tonight will be building things next week that most developers still cannot do with a team. I should be charging $199 for this. It is free. Comment CLAUDE and I will send it to you directly. RT if you know someone who needs to see this.

@VicVijayakumar How do you dev test ? Through agents or manually

I'm now able to tell my agent “we are going to work on JIRA-1234” and it goes and pulls down the task, makes me a plan, I say yeah okay that looks good, and it generates the commit. I run an AI review from a different session, it finds 4 issues of varying priorities, I paste it to my original agent and say validate these findings and fix them if necessary, it creates a fix, I run another review, no more high priority issues found. I open up the code in an IDE to go over it before pushing it up for human review. Looks fine I guess, nothing crazy. I try to understand everything before I push it up for review because if this breaks, it's still my name on it. I say why did you make this one change, it gives me a reasonable explanation for why. It says something codebaity like "if you want I can suggest 2 more ways you could really tighten up this work to prevent some rare but possible regressions". I'm smart enough to not fall for it. Code pushed up, task moved to in-review. I didn't write any of it, this is not my accomplishment. Users won't care who wrote it if it works. A lot done in 20 mins but it felt soulless.

@akshaymarch7 This Pretty much summarizes my day

I’ve become pretty bullish on AI lately. Not in a hype way. Just from using it every day while working. Honestly, it’s hard to imagine going back to how we used to work earlier. Small things first… writing boilerplate code, basic functions, quick scripts. Earlier this used to take time and break your flow. Now it’s just… done in seconds. But the bigger shift for me has been in thinking. When I’m starting something new, I don’t feel stuck anymore. I just ask questions, explore ideas, get a rough direction, and then build on top of it. It’s like having someone to bounce thoughts with all the time. Debugging has also changed a lot. Instead of staring at the screen for hours, I explain the problem, share context, and it often points me in the right direction much faster. And honestly, one underrated use… learning. You can literally ask “explain this like I’m new to it”, or “give me a simple example”, or “what am I missing here?” and you get instant help. Earlier this would take multiple blogs, docs, videos. Of course, you still need to understand what you’re building. That part doesn’t go away. But if you’re not using AI properly right now, you’re probably moving slower than you need to. This is not just another tool. It’s becoming part of how we work. The engineers who learn to use it well are going to have a very unfair advantage. Curious how others are using it daily.

@livingdevops Great summary 🔥

Kubernetes is beautiful. Every Concept Has a Story, you just don't know it yet. In k8s, you run your app as a pod. It runs your container. Then it crashes, and nobody restarts it. It is just gone. So you use a Deployment. One pod dies and another comes back. You want 3 running, it keeps 3 running. Every pod gets a new IP when it restarts. Another service needs to talk to your app but the IPs keep changing. You cannot hardcode them at scale. So you use a Service. One stable IP that always finds your pods using labels, not IPs. Pods die and come back. The Service does not care. But now you have 10 services and 10 load balancers. Your cloud bill does not care that 6 of them handle almost no traffic. So you use Ingress. One load balancer, all services behind it, smart routing. But Ingress is just rules and nobody executes them. So you add an Ingress Controller. Nginx, Traefik, AWS Load Balancer Controller. Now the rules actually work. Your app needs config so you hardcode it inside the container. Wrong database in staging. Wrong API key in production. You rebuild the image every time config changes. So you use a ConfigMap. Config lives outside the container and gets injected at runtime. Same image runs in dev, staging and production with different configs. But your database password is now sitting in a ConfigMap unencrypted. Anyone with basic kubectl access can read it. That is not a mistake. That is a security incident. So you use a Secret. Sensitive data stored separately with its own access controls. Your image never sees it. Some days 100 users, some days 10,000. You manually scale to 8 pods during the spike and watch them sit idle all night. You cannot babysit your cluster forever. So you use HPA. CPU crosses 70 percent and pods are added automatically. Traffic drops and they scale back down. You are not woken up at 2am anymore. But now your nodes are full and new pods sit in Pending state. HPA did its job. Your cluster had nowhere to put the pods. So you use Karpenter. Pods stuck in Pending and a new node appears automatically. Load drops and the node is removed. You only pay for what you actually use. One pod starts consuming 4GB of memory and nobody told Kubernetes it was not supposed to. It starves every other pod on that node and a cascade begins. One rogue pod with no limits takes down everything around it. So you use Resource Requests and Limits. Requests tell Kubernetes the minimum your pod needs to be scheduled. Limits make sure no pod can steal from everything around it. Your cluster runs predictably.

@ravikiran_dev7 @grok filter this list with list of companies which provides working from home policy

𝗨𝗻𝗱𝗲𝗿𝗿𝗮𝘁𝗲𝗱 𝗰𝗼𝗺𝗽𝗮𝗻𝗶𝗲𝘀 𝗽𝗮𝘆𝗶𝗻𝗴 30+ LPA 𝗶𝗻 𝗜𝗻𝗱𝗶𝗮 Atlassian 40–70 LPA Postman 35–60 LPA BrowserStack 30–50 LPA Chargebee 30–45 LPA Hasura 35–60 LPA Razorpay 30–45 LPA Juspay 30–50 LPA Groww 30–45 LPA Cred 30–50 LPA Snowflake 50–90 LPA Databricks 45–80 LPA Confluent 40–70 LPA Twilio 30–50 LPA Okta 25–45 LPA Elastic 30–50 LPA Palantir 35–60 LPA CrowdStrike 30–55 LPA Figma 30–50 LPA Redis 25–45 LPA MongoDB 25–45 LPA HashiCorp 25–45 LPA Brex 30–55 LPA Plaid 30–55 LPA Stripe 35–60 LPA Coinbase 30–55 LPA Airbnb (India roles) 30–50 LPA Workday 20–35 LPA ServiceNow 20–35 LPA Skyscanner 20–35 LPA Tower Research 80 LPA – 2 Cr DE Shaw 50 LPA – 1 Cr Goldman Sachs 30–45 LPA Everyone runs after FAANG… but the real bag is scattered here. Bookmark this before it disappears 📑

@arpit_bhayani I hope more and more people in corporate learn this

Once you are in the system (team or company) and thinking deeply, you will start to notice inefficiencies and gaps. You will see decisions being made that feel wrong. But instead of putting your point across bluntly (as if you know everything), it is extremely important to raise it thoughtfully. What I have learned over the last decade is that tone matters more than the content, at least at first. Challenge decisions, yes, but do it with kindness and clarity. Do not assume others missed something; assume they had different inputs. One of the things I became good at is framing - I started framing my inputs as additions, not corrections. It changes how they are received. When offering feedback or questioning a choice, be mild in tone but sharp in reasoning. Of course, sharpness must come from preparation, so gather as much context as possible before making an argument. Here's how I "do my homework." - understand the context and constraints - explore alternatives and their trade-offs - anticipate counters and prepare - cite metrics, issues, or past incidents - keep it brief but loaded with substance - state assumptions and ask clarifying questions - suggestions should back team or product goals Be as detailed as possible, because that builds trust. Over time, your feedback will not just be heard, but it will be sought. The goal is not just to "win" arguments; it is to move the team forward and chase the same north star.

@archiexzzz I don't even remember when was the last time I wrote code by myself Seriously miss those days 😭

i have lost meaning. nothing feels difficult anymore. earlier, there was so much joy in writing code by hand - finding problems, staying awake for hours just to solve that one silly bug buried deep in the code. coding gave me a lot of joy, but with agentic coding, writing code by hand no longer makes sense - not because i want it that way, but because of the pressure from everyone around you. why struggle for hours when you can finish everything at 100 toks/sec? it has left a dent in that joy i once carried. i wish i could go back to writing pure code with my own hands - no agentic coding at all - but there is no time for that. features need to be shipped quickly, and if you don't keep up, you get crushed by others who do. some might say, "you still have to read the code and figure out if it's correct." that's true, but reviewing something is very different from actually writing it. the neurons fire differently for both - and they fire far more when your fingers are hitting those keys on the keyboard. maybe the craft isn't dead, but it is slowly being asked to wait in the corner - and for those of us who fell in love with the process, not just the output, that silence is louder than any compiler error ever was.

@DrNimoYadav @dhruv_rathee

Arnab: Don’t watch Dhurandhar, Dhurandhar is a fiction, we don’t want to see Akshaye Khanna Dancing, if anyone has guts in Bollywood please make a movie Unnao Rape case, make a movie on real crime. Arnab has just exposed RW propaganda of Dhurandhar and gave his support to Dhruv Rathee. Historic 😭😭

@javainterviewer Some interviewers want their own answers that they have prepared

I’ve been interviewing a lot recently, and one thing stood out clearly: System design interviews are wildly inconsistent. Interviews are half luck, you never know who you’ll get. At Amazon, Apple, and Google, the system design rounds felt collaborative. Interviewers asked clarifying questions, gave hints, challenged assumptions, and wanted to understand how I think , not catch me being wrong. Even when the design wasn’t perfect, the goal was reasoning, not perfection. But in many small and mid-sized companies, the experience was very different. It often felt like the interviewer was waiting for me to fail. Eg. one: I was asked to design an Instagram-like app for iOS and Android at a startup. I suggested React Native, reasonable for cost and speed. Immediately, before discussing anything else, I got: “What if the feed has 1000 posts offline? That’s too heavy.” I explained valid approaches: FlatList, unloading from memory, progressive rendering, caching. No discussion. “No, that’s wrong.” Call ended halfway. If there was a specific concern, why not explain it? Eg. two: I designed a normalized database schema based on given requirements. They said: “No, we want a flattened table. We don’t like joins.” I had heard the problem 10 minutes ago. How was I supposed to know their internal bias? They could have framed it as a constraint, instead, my entire design was declared wrong. Then there’s distributed systems. Some interviewers come in with a fixed architecture in mind, Kafka, queues, DLQs, rate limiters, even when the problem is simple. Ask someone to “count clicks,” and if you don’t say Kafka, you fail. A Redis counter would work just fine, but buzzwords matter more than reasoning. In those rooms, system design isn’t about scale or trade-offs. It’s about guessing what the interviewer personally believes in. The hardest part? Many of these interviews offer zero guidance. No follow-ups. No clarification. No pushback. In real engineering, you build something workable first, then refine as constraints emerge. In these interviews, you’re expected to guess all constraints upfront, which is unrealistic. At this point, I often start by listing multiple approaches and watch which one makes the interviewer nod. Otherwise, it’s not engineering, it’s mind reading. I actually enjoy system design. I just wish more interviews tested thinking instead of luck. -------------------- Check out my Java+Spring boot+Microservices+Design Patterns+System design ebook curated for interviews from here matamgi.com/java-interview…

@striver_79 Golden lines "Team health first"

Launch (New Gen TUF) has been postponed, reason 👇 - Unexpected bugs in final testing - Multi-device checks: mobile to monitors - Team health first, not over-pushing - Design updates + data-migration delays The last 18 months taught me one thing, don’t rush unless you’re 100% sure. We’re sticking to that this time. Thank you, we will make it this week surely.

@sriniously The freedom to do anything and everything is what creates joy ig

Lately, as a developer, especially with the advent of agentic ai tools, there's no denying that the amount of "joy" in writing code at work has significantly gone down. I mean yes, we are more productive than ever, we have more power and time to build anything we want, but iykyk. Which brings to my point of this post. I was never into building personal software, meaning, creating tools/automation workflows for MYSELF. I never felt the need and it always was a drag. So this is a particular unexplored area of life that is proving to be the number one contributor to bring that "joy" back, with this feeling of building software for yourself that nobody else will ever use, or rather I won't LET anybody use. So embarrassing. When you are the only user, you make a lot of "interesting" tradeoffs, not the ones I would be proud to discuss amongst my peers in any professional setup. Things like, skipping the auth layer, why? Well, because if you don't trust yourself in your own machine, then my friend you have a bigger problem at hand. There will be this VERY important CLI flag that you use all the time, but instead of making it a default, you depend on your zsh suggestions and auto-completions to write it out for you, who cares. And man don't get me started on the db schemas and indices? Index? What's that? And the classic, git push origin main. God, the satisfaction I get from that, EVERY SINGLE TIME. Personal software also frees you to be maximally weird. I have a script that parses my browser history, runs it through embedding models, and clusters my research sessions. It's held together with string and shell scripts. It would never pass code review, lol, I would fire me if I saw that code in ANY kind of context. But it's grown to be so useful to me in a way that polished tools aren't, because I built it around my exact mental model of how I work. The reason for this feeling, for the most part, is professional software development often optimizes for the wrong things. Well not really wrong, they are the necessary evils, but wrong in this context. We build for hypothetical users, imaginary scale, theoretical maintainability by future developers who may never exist, atleast in the initial phase. Personal tools revert this formula. You build for one real user with real needs right now. And the needs that you have a 200% understanding of. So build something small and ugly for yourself. Use it every day. Let it evolve based on actual friction and use rather than anticipated requirements. You'll develop intuitions that no tutorial can teach you and also find a little more joy.

@hijunedkhatri Where can I find these jobs

Contract roles are misunderstood in India. And it’s costing real opportunities. I was hiring for 3 US-based companies. One had payroll set up via Rippling. The other two didn’t. All roles were full-time, long-term, and well-paid. But since they were on a “contract,” We lost 3 great candidates. Total CTC lost: ~₹1.8 Cr. Why? Because “contract” in India still means: - Not a real job - Risky for future roles - Likely to get lowballed later But that’s not the case. US companies use Rippling or Deel when they don’t have an entity in India. It’s still a serious full-time job. Just different paperwork. Why do you think contract roles are misunderstood in India?

@va_a14 Salesforce india is remote ?

Companies paying more than 40 LPA+ for SDE 1 role, and offers complete remote option. I am able to find these companies, continue in the comment - Confluent - Coinbase - Atlassian - AirBnb - Coursera - Bloomreach - Salesforce - Twitter (X) - Pinterest

@iamstake @MartinGarrix @edsheeran Already innnn

if rewind repeat it actually drops this year, i’m throwing a listening party for all the 2015 EDM kids who never got closure 🫡 @MartinGarrix @EdSheeran

@striver_79 Somehow somewhere there is always a single point of failure 🥲

AWS Outage (US-EAST-1): Explained Simply 1️⃣ Started with a DNS issue - AWS services couldn’t talk to each other. 2️⃣ This broke DynamoDB, which many other services depend on. 3️⃣ EC2 launches & Lambda jobs started failing due to the chain effect. 4️⃣ AWS fixed the DNS issue, but some services are still catching up. It’s a reminder of how one small issue can impact half the internet. ⚙️ Full read: health.aws.amazon.com/health/status

@rajtoday Why doesn't authorities visit trains or stations at rush hour ?

Automatic door closing trial on regular EMU suburban local train in presence of outgoing General Manager of Central Railway. #MumbaiRailway #Mumbai

Rapists are in garlands Educators are in jail This is what Modi has done to India #ISupportSonamWangchuk

@vjsinsights I feel we should promote more hybrid work culture it's the proper balance

Remote work has perks, but in person / hybrid benefits are hard to ignore, especially early in your career: 1. Onboarding, debugging, knowledge transfer, design reviews, and critical issue resolution are all smoother in person. 2. Networking + visibility opportunities are greater. 3. Social bonding (team lunches, coffee chats) happens more naturally. 4. Remote roles are fewer, and policies can change anytime. Everyone’s situation is different. Make sure you weigh the pros and cons against your own goals.

@petergyang @grok is this true

So let me get this straight - if you're on H-1B you now can no longer visit your family internationally without your employer paying you $100K to come back to the US?

@MYK12397 @grok answer all these

advanced #golang interview problems that separate senior go developers from the rest: These aren't your typical "what's a goroutine?" questions. Real production scenarios that every Go developer should master 👇 1. suppose your tests pass locally but fail randomly in CI. Race conditions are detected but you can't reliably test concurrent code. How do you write bulletproof tests for goroutines handling simultaneous bank transfers?