😭😭

Those who know, know

RT @joshibipin: 🖥️🛠️ “Simple” in enterprise .NET is not about fewer lines of code. It’s about surviving change. 🔗 Read more: https://t.co…

Do not keep looking for beginner-friendly content, because for harder topics, there is none. Also, they often optimize for feeling smart rather than becoming smart. Try to build a habit of reading, watching, and absorbing detailed information and concepts. This will not only help you move away from being spoon-fed, but it will also make you better at abstract thinking. I believe abstract thinking will become crucial in the coming decade, as the world shifts toward solving more complex and ambiguous problems that are not easily visualized and comprehended. We are seeing an early sign of the drift with you-know-what. Extrapolating from here, I would say it is going to be increasingly vital for us to think beyond the obvious. The people who will navigate that well are not the ones who found the best beginner guide. They will be the ones who learned to sit with the hard stuff until it made sense.

I feel the tech industry will have spiky teams in the future, i.e., teams with candidates who are 5/5 in some areas rather than 3/5 across everything. A candidate who holds 5/5 in databases and 2/5 in low-level design is more valuable than someone who is a solid 3/5 across the board. The 3/5 person seems to be a safe bet, but it would be nearly impossible to drive outsized impact with a fully balanced individual. The thesis is simple - extreme strengths are rare and hard to develop. A 2/5 weakness can often be coached up to a 3/5 with time. But you cannot coach someone into being exceptional at something. So, as the world becomes more aggressive and cutthroat, well-rounded candidates will create an impedance mismatch. They fit everywhere but excel nowhere. A team of 3/5 generalists will be competent (no doubt), but highly unlikely to be remarkable. The better bet would be to hire people with sharp edges, pair them with teammates whose spikes complement their gaps, and coach up the soft spots over time to become average. Exceptional ones have never looked balanced on paper.

Node.js is moving to one major release per year starting with Node 27! 🚀 ✅ Simpler: Every release becomes LTS. ✅ Predictable: Version numbers now align with the year. ✅ New: A 6-month Alpha channel for early testing. Read why we’re evolving: bit.ly/4rnosLg

Hear me out. Crazy idea. What if we took one billion and just… did some good. Right now. Instead of investing it in AI to maybe do some good one day.

MSSQL extension of VSCODE is going in a good direction. I hope it won't be killed like Azure data studio. Capability of taking backups and showing execution plans makes it different from other extensions. #microsoft #vscode #mssql

Link: erikej.github.io/dacfx/dotne…

Linux users: "I like to type out commands!" Also, Linux users:

Is Traditional Software Engineering Dead? “Does this mean that traditional software engineering is dead? Absolutely not. Software engineers—even the ones who are not necessarily tuning or training AI models—these are now among the most leveraged people on earth. Sure, the guys who are training and tuning models are even more leveraged because they’re building the tool set that software engineers are using. But software engineers still have two massive advantages on you. First, they think in code, so they actually know what’s going on underneath. And all abstractions are leaky. So when you have a computer programming for you—when you have Claude Code or equivalent programming for you—it’s going to make mistakes. It’s going to have bugs. It’s going to have suboptimal architecture. So it’s not going to be quite right. And someone who understands what’s going on underneath will be able to plug the leaks as they occur. So if you want to build a well-architected application, if you want to be able to even specify a well-architected application, if you want to be able to make it run at high performance, if you want it to do its best, if you want to catch the bugs early, then you’re going to want to have a software engineering background. The traditional software engineer is going to be able to use these tools much better. And there are still many kinds of problems in software engineering that are out of scope for these AI programs today. The easiest way to think about those is problems that are outside of their data distribution. For example, if they need to do a binary sort or reverse a linked list, they’ve seen countless examples of that, so they’re extremely good at it. But when you start getting out of their domain—where you have to write very high-performance code, when you’re running on architectures that are novel or brand new, when you’re actually creating new things or solving new problems, then you still need to get in there and hand code it. At least until either there are so many of those examples that new models can be trained on them, or until these models can sufficiently reason at even higher levels of abstraction and crack it on their own… And remember: there is no demand for average. The average app—nobody wants it, at least as long as it’s not filling some niche that is filled by a superior app. The app that is better will win essentially a hundred percent of the market. Maybe there’s some small percentage that will bleed off to the second-best app because it does some little niche feature better than the main app, or it’s cheaper, or something of the sort. But generally speaking, people only want the best of anything. So the bad news is there’s no point in being number two or number three—like in the famous Glengarry Glen Ross scene where Alec Baldwin says, “First place gets a Cadillac Eldorado, second place gets a set of steak knives, and third place you’re fired.” That’s absolutely true in these winner-take-all markets. That’s the bad news: You have to be the best at something if you want to win. However, the set of things you can be best at is infinite. You can always find some niche that is perfect for you, and you can be the best at that thing. This goes back to an old tweet of mine where I said, “Become the best in the world at what you do. Keep redefining what you do until this is true.” And I think that still applies in this age of AI.”

sqlQuery redd.it/1rd82vn

why limit yourself to someone else's preference and curation? go build a db go build a web framework go write a file system go build an operating system go build a prog language go write a webserver go build an ORM go build an agent build whatever excites you you have all the resources in the world to build literally anything you want. why follow a roadmap!

I've been working on something big. After months of planning and restructuring, I'm excited to reintroduce my .NET Web API Zero to Hero course – completely FREE and designed to take you from fundamentals to production-ready APIs. What's inside: - 12 Modules - 125 Lessons - 60 Hours of Content Topics covered: → REST API Best Practices & Middleware → Entity Framework Core (18 lessons!) → CQRS, MediatR & Design Patterns → Performance & Caching Strategies → HTTP Clients & Resilience with Polly → Background Processing with Hangfire & Quartz → File Handling & Cloud Storage → JWT, OAuth, Cognito & Security Best Practices → Clean Architecture, DDD & Vertical Slice → Observability with OpenTelemetry, Seq & Grafana → Testing & CI/CD → Docker & Deployment to AWS 25 lessons are already live. Starting January second week, I'll be publishing 3-4 new lessons every week until the course is complete. This isn't just another tutorial series. This is the course I wish I had when I started my .NET journey. Every lesson solves a real problem. Every pattern is battle-tested. If you're a .NET developer looking to: ✅ Land your first .NET job ✅ Level up from junior to mid/senior ✅ Build production-grade APIs with confidence This course is for you. Start here: codewithmukesh.com/courses/d… To get notified of new articles, do join my .NET Newsletter: newsletter.codewithmukesh.co… Bookmark it. Share it with your team. Let's build something great together. Happy Coding :)

Dotnet Core API Crud With Mysql and Dapper ravindradevrani.com/posts/do… #dotnet #aspnetcore #csharp

Error Handling in SQLite: Best Practices sqliteforum.com/p/error-hand… #sqlite #sql #database

As a person grew up on mountains of Uttarakhand. I am very attached to it. We must stand up to #SaveAravali — before it is too late.

LeftJoin and RightJoin in Ef Core 10 ravindradevrani.com/posts/le… #dotnet #aspnetcore

It is okay to learn code by mistakes ravindradevrani.com/posts/le…