EBEsanju Babatundeintundehub.dev·12h ago · 4 min readCQRS in .NET: Separating Reads from Writes Without OverengineeringCQRS gets a reputation as an "enterprise architecture" pattern that's overkill for most applications, and honestly, that reputation is often deserved. I've seen teams adopt full CQRS with separate rea00
EBEsanju Babatundeintundehub.dev·3d ago · 3 min readSecuring ASP.NET Core APIs with JWT and OAuth2Security is the part of API development where "it works" and "it's actually safe" can look identical right up until someone finds the gap. I've worked on fintech and insurance platforms where a missed00
EBEsanju Babatundeintundehub.dev·4d ago · 4 min readMentoring Junior Developers: What Actually Works?I've mentored developers on nearly every team I've led, and I've made most of the mistakes you can make while doing it. The biggest one, early on, was thinking mentorship meant having the answer ready20
EBEsanju Babatundeintundehub.dev·5d ago · 3 min readGraphQL APIs in .NET: When It's Worth the ComplexityGraphQL gets pitched as a universal upgrade over REST, and I don't buy that framing. I've built both REST and GraphQL APIs in production, and the honest answer is that GraphQL solves specific problems20
EBEsanju Babatundeintundehub.dev·Aug 10 · 4 min readDesigning RESTful APIs Developers Actually Enjoy UsingEvery API is a user interface. The users just happen to be developers instead of end customers, and that distinction gets forgotten more often than it should. I've integrated more third-party APIs tha10
