Writing good code is important than just writing code.

Hello @MyntraSupport you have messaged up the delivery of my order. It was supposed to be delivered on 12th and now doesn’t have a delivery date.

Weekend musings. #Osho

Good morning 🌞

Thoda Zyada Hack Hogaya Lagta Hai #BiharElection2025

Bal Diwas Ki Shubhkamnaen.

Thinking about building AI agents but not sure where to start? Our newest AI Agents for Beginners course is here, and this one is focused on AI Agentic Design Principles, which helps you learn how to implement simple, human-first approach to creating agents that: ✨ Boost

The most beautiful things in the world happen quietly.

API Gateway vs Load Balancer vs Reverse Proxy (explained in under 2 mins): • Load Balancer ↳ Distributes incoming traffic across multiple servers to ensure reliability and performance. • Reverse Proxy ↳ Sits in front of servers, forwarding requests while hiding server

To summarise: Most .NET performance issues in the cloud are not coding problems. They come from missed configurations, default settings, and lack of observability. Fix these five and your API will feel instantly faster. Happy shipping 🚀

5. Database connection misconfigurations Common issues: ❌ Missing connection pooling settings ❌ Not using retry policies ❌ No caching ❌ Inefficient EF Core queries Cloud databases need resilient design. One wrong setting slows the entire API.

4. Auto-scaling is off Cloud traffic is unpredictable. If your API gets a sudden spike and scaling is disabled, your app will choke. Scale by: ✔ CPU ✔ Memory ✔ Requests ✔ Custom rules

3. Application Insights is not configured properly No logs No telemetry No dependency tracking No slow-query detection You cannot fix what you cannot see. Turn it on and tune sampling.

2. No health checks enabled Add this in Program.cs: https://t.co/cUBPLXMv9n.AddHealthChecks(); Azure uses health checks to know if your instance is alive. Without it, traffic may be routed to a dead or stuck instance.

1. Running on the wrong App Service Plan Many teams deploy on the default tier and forget to size it. If your API is CPU-heavy or handles many requests, you need at least a Standard or Premium plan. A weak plan = slow responses.

5 Azure Misconfigurations That Kill .NET API Performance If your .NET API is running on Azure and still feels slow, the problem is usually not your code. Most of the time, it is a small Azure setting that nobody paid attention to. Here are 5 Azure misconfigurations that

Vibe newspaper!

What is it that cannot be copied?

Tech bro’s from the silicon capital.

Gear Cycle

Browser Wars 2025