i been calin it the #dddfl for kicks - the domain driven design feedback loop
ubiquitous language <-> domain model <-> design <-> code
now i think team structure needs to be in it to account for conways law 🤔
getting crazy pushback 'gainst knowledge crunching n other #ddDesign habits. methinks def due to org culture;
so new ish:
ubiquitous language <-> team structure <-> domain model <-> design <-> code #dddfl
refactor one part, refactor all parts
so team structure should also be readily changeable refactorable; alongside the model; cus the teams' structures and the relationships between them should change along with deeper insight gained about bounded contexts, services, applications, code-bases, projects or what have you
new ish:
account for large scale structure
ubiquitous language <-> team structure <-> domain model <-> large scale structure <-> design <-> code
Domain Driven Design (DDD) made plain broke down to the bone gristle. cus i need that science to level up my code, but miss me with all the stuffy acronyms and jargon. 🧵
domain
- the actual problem
- what we're trying to solve with the code for the user
- the set of problems that the users ask the developers to solve
- the subject matter
domain driven
- problem focused
- to stay focused on the actual problem
For me, when the need for a new language, library, framework, shiny thing, etc pops up - i find that i usually take the same general steps
and the 7-bullet list i jotted down in my notes became this thread:
1. pick a language, any language. or framework, library etc.
no tech is perfect. don't sweat it the choice too much. they all have pros and cons - but do try to pick one that has good community adoption so you can get help when you run into blockers
"Always implement things when you actually need them,
never when you just foresee that you need them." - Ron Jeffries
i feel attacked 🙄
(over-abstraction is one of my guilty pleasures) 😅
like, sometimes i'll take that advice to "code to the interface" to the extreme, just cus i can, and i'll make everything an interface. what you can do with polymorphism and dependency injection is fun ...
but man is it an over-abstraction time suck when trying to just focus on "keeping it simple" KISS minimum viable product. gotta draw the line somewhere and make concrete classes and move forward ...