This is about a thought process re-introduced to the programming community by Eric Evans through the book above: Domain-Driven Design: Tackling Complexity in the Heart of Software .
- Classic Read
Resource:
Functional architecture - Mark Seemann
My one golden nugget:
functional programming vs object oriented programming when modeling the domain is mainly data and functions as opposed to entities, value objects and services.
- How To's:
Resource:
Domain Driven Development the good parts
My one golden nugget:
bounded context are at the core of developing a great domain. Micro-services and anti-corruption layers are great for defining bounded contexts.
- Biography:
Resource:
Domain Modeling Made Functional with the F# Type System
My one golden nugget:
Types can be used to represent the domain in a fine-grained, self documenting way.
Reading Lists
There are books that I reread regularly, but at the moment I read new books in trying to identify the best books to reread while trying to push my learning boundries. So far I got to organise my future reading in 6 lists, main readings for each time of the day:
- morning: classics (my definition of classics, must say)
- lunch break: how to's (programming or managerial mostly)
- evening: biographies
and 3 lists of books that look interesting but haven't got enough information for them:
For people who just wanted to know how to choose what to read by Tai Lopez' talked of principles.
Do you have a book or resource that would like to see what nuggets I can get out from for you ?