MYMike Younginblog.unplugit.fi·2d ago · 8 min readKnowledge must be usable beyond its sourceA strategy can make perfect sense in the room where it was written and still be almost useless everywhere else. The people in that room remember the discussion, the rejected alternatives and the diffi00
OFOluwaseyi Fatunmoleinfreecodecamp.org·Sep 1 · 26 min readFeature Modularization in Flutter: How to Combine Clean Architecture and Domain-Driven Design for Self-Contained, Scalable FeaturesAs an engineer working on a small team, your current structure could fly. But what if your team, all contributing to the same codebase, reaches 20 or more people at scale? You'll need careful design t00
MYMike Younginblog.unplugit.fi·Sep 1 · 9 min readAlignment Needs Bounded OwnershipWhen organisations talk about alignment, the conversation often moves towards shared goals, shared terminology and common ways of working. That sounds reasonable. It can also lead to a harmful conclus00
MYMike Younginblog.unplugit.fi·Aug 18 · 9 min readSoftware development has always been an alignment problemThe phrase alignment problem is now strongly associated with AI safety. In that discussion, the concern is whether an AI system behaves consistently with human values and intent. That is not the subje30
WOWasinjesu Osokoinwasinjesu-osoko.hashnode.dev·Aug 12 · 3 min readBuilding Products Businesses Actually Pay For: Domain-Driven Design in PracticeMost enterprise software projects fail not because of slow frameworks or buggy code, but because of a fundamental disconnect: developers write code for developers, while businesses pay for solutions t10
MYMike Younginblog.unplugit.fi·Aug 12 · 8 min readAI-assisted development needs boundariesMost writing about AI-assisted development seems to settle into three positions. There is the productivity account, where an agent is judged by how quickly it turns a ticket into code, the prompting a42KS
MYMike Younginblog.unplugit.fi·Aug 6 · 9 min readInternal, External, and Contract Models Should Not Be the Same ThingDiscussions about model separation often end up being discussions about boilerplate. One object arrives at a service boundary, most of its fields are copied into another object, and a similar conversi01M
OFOluwaseyi Fatunmoleinfreecodecamp.org·Jul 16 · 31 min readThe Observer Design Pattern Handbook: Event-Driven Architecture & Domain-Driven Design in DartEvery application, at some point, has to deal with a fundamental challenge: something happens, and several other things need to react to it. A user logs in, and the app needs to save a token, cache th00
RKRemco Koedootinremcokoedoot.hashnode.dev·Jun 26 · 7 min readDomain-Driven Design: Understand Before You BuildThere is a moment in almost every software project where something goes quietly wrong. Not a bug. Not a production incident. Something more subtle. The team is building fast, the tickets are moving, t00
JJubsindreaded-developer.hashnode.dev·Jun 25 · 12 min readOne Model to Rule Them All: Domain-Driven Design, The Fellowship of the CodebaseI want to tell you about the day I realized our UserManager class had 47 methods. Forty. Seven. It handled login, password resets, profile updates, billing, email preferences, audit logs, and — I am n00