DCDionisio Cortés Fernándezinblog.dionisioc.dev·3d ago · 25 min readSOLID Without the Acronym: It's Just Cohesion and CouplingSOLID isn't really five independent principles. It's mostly two long-standing software design ideas expressed in different ways. High cohesion — keep the things that change together, together. Low co00
CChrisinkristijan-pajtasev.hashnode.dev·3d ago · 7 min readImplementing Named Slots in React With Child Type InspectionReact is deliberately minimal. It gives you components, props, and children while leaving structural composition patterns up to you. One pattern that doesn't exist natively but comes up constantly in 00
JSJayesh Sojitrainjayesh-sojitra.hashnode.dev·6d ago · 4 min read Server Components vs Client Components (Next.js)Day 5 covered the basic split: Server Components by default, Client Components when you opt in. Today's the deeper version — exactly what each can and can't do, and how to actually decide where the bo00
Ppraveeninthecoderegistry.hashnode.dev·Sep 9 · 31 min readHow Enterprises Should Govern AI-Generated CodeSoftware engineering is undergoing an irreversible structural transition. Where developers previously designed and hand-typed logic from scratch, engineering workflows now operate alongside large lang00
OGOnkesh Guptainonkeshgupta.hashnode.dev·Sep 8 · 9 min readDesign Patterns Simplified #2: Factory MethodThe Problem You are building the payment flow for an app. First requirement: support Stripe. Simple. Somewhere in your checkout code, you write: StripeGateway* gateway = new StripeGateway(); gateway->00
LPLeon Penningsinblog.leonpennings.com·Sep 7 · 10 min readTech Debt Isn't a Backlog Problem. It's a "Done" Problem.Technical debt is usually described as a bill that arrives later for a purchase made earlier: speed bought on credit, with the cost deferred to some future date. Ask practitioners why debt accumulates00
ANAyush Nigaminayushnigam.hashnode.dev·Sep 3 · 12 min readArchitecture for Testable Code (Part 2: State & Infrastructure)In Part 1: The Core Patterns of this series, we fixed the code. We injected dependencies, isolated business logic, and made our functions strictly typed and predictable. But clean code is only half th00
OGOnkesh Guptainonkeshgupta.hashnode.dev·Sep 3 · 7 min readDesign Patterns Simplified: Creational, Structural & Behavioral - The Map Before The TerritoryYou just finished SOLID. Five principles, five "aha" moments, five checkmarks. Nice. Then you open a design patterns cheat sheet for the first time and see 23 of them. Singleton. Factory. Adapter. Dec00
ALAdam Lewisinprickles.hashnode.dev·Sep 2 · 3 min readNaming: if you have to open the body, the name isn't doneEveryone I've worked with agrees that naming matters. Almost nobody spends any time on it. The name gets picked while the code is half written and then it sticks, because renaming feels like fuss once11R
OGOnkesh Guptainonkeshgupta.hashnode.dev·Sep 1 · 8 min readSOLID Principles Simplified #5: Dependency Inversion PrincipleThe Problem You're building a NotificationService for your app. First requirement is to send notifications over email. Simple enough. You write an EmailSender class and inside NotificationService, you02N
