Prashant Yadav

Users can now auto-connect plugins when they log in to Claude, with MCP servers that accept Claude as a trusted issuer. If you’re building plugins for Claude, add support so users get started faster and stay connected without re-authorizing.

The worst investment I did is buying a property of Godrej- big brand bigger, bigger fraud. Bought a property in 2023, they told we will get possession in 2026 mid, forget the possession, they are telling they want to add additional floors and that too 8-9 floors, without adding any extra plot to the project. From past 3 months the CRMs has bullied, disturbed, bribed and what not for us to sign the consent form to modify the RERA, as a person who works a full time job, this kind of harassment takes a toll on mental health, as now I am paying full EMI and possession not sure when they are going to give(maybe 2028(Rera date)), the constructions they have left in mid. For Phase1 owners also they are pushing the handover deadline. This is so disappointing! and now I am stuck, so whenever you decide to buy a property in Godrej, think 100 times before.

If AI makes you 10x faster at coding, why is your team not shipping 10x faster? Amdahl's law has the answer... The law says the overall speedup is capped by the part you did not speed up. With `p` as the fraction of the work you accelerate and `s` as the speedup on that fraction, speedup is computed as attached. Now plug in some numbers. Say writing code is 30% of the time from idea to production, and AI makes that part 10x faster. The overall speedup is 1 / (0.7 + 0.03), which is about 1.37x. Even if coding is half of the cycle, you get about 1.8x. These numbers are illustrative, so use your own, but the shape stays the same. The rest of the cycle is still there: - Figuring out what to build - Aligning product, design, and other teams. - Code reviews, which are now more than ever - CI and CD takes the same wall time as before. - Debugging and incidents, where code that nobody on the team wrote line by line takes longer to understand. In fact, it can get worse than Amdahl predicts. Faster code generation increases the load on every stage after it, so the review queue grows and the bottleneck shifts. A team that writes 10x more code with the same review capacity is just building a bigger queue, unfortunately So if you want the team to actually ship faster, measure the whole path from idea to production and find where work waits. Then apply AI there too: review, test generation, flaky test triage, deploy safety checks. Otherwise, you have optimized the part of the system that was never the constraint. Speeding up the typing was always the easy part :)