Eric Evans
Software designer
6
MENTIONS
4
EPISODES
3
PODCASTS
Search complete. 6 mentions across 4 episodes found for "Eric Evans".
Sep 17, 2026
AI Skills with Matt Pocock
M
56:06Matt PocockGUEST
Yeah.
M
56:07Matt PocockGUEST
Eric Evans' incredible book where he talks about ubiquitous language, a language, again, really deep in the agent's priors.
M
56:13Matt PocockGUEST
It understands it really well.
M
56:14Matt PocockGUEST
I sort of started toying with the idea of maybe changing GrillMe a little bit, because GrillMe is a very simple skill.
M
59:30Matt PocockGUEST
But an agent can't do that.
M
59:33Matt PocockGUEST
It starts fresh every single session, and so you need to optimize your code base for that person.
M
59:38Matt PocockGUEST
That leads you down into really interesting paths, and it turns out that software fundamentals have been saying we've been trying, trying to do that for the entire time, right? I am fully like, I dunno, uh, Eric Evans pilled.
M
59:50Matt PocockGUEST
I'm fully la- like software fundamentals pilled.
Software Architecture Fundamentals 2nd Edition, Chapter 17: Orchestration-driven Service-oriented Architecture
M
18:22Mark RichardsHOST
Why aren't we sharing you across all of these divisions? And a great goal, but poorly executed.
N
18:32Neal FordHOST
Well, exactly, and back to the origin of this question, as it leading to domain-driven design and microservices, I think it was the observation of the brittleness that led ultimately to Eric Evans saying, hey, as much of a downside as it is, you really need to keep the things about this local because the more you let it extend into your architecture, the more brittle your architecture becomes.
N
18:58Neal FordHOST
That's really...
N
18:59Neal FordHOST
I think the architectural lesson of domain-driven design is the degree of brittleness you're allowing to seep out into your architecture is how much of those implementation details you creep out.
048- Building for Betting: Why FDJ United Built Their Own Data Platform Instead of Buying One
P
20:27Phil GoddardGUEST
But data mesh ultimately is an organizational model that draws on domain-driven design.
P
20:35Phil GoddardGUEST
So domain-driven design is a software engineering philosophy introduced by Eric Evans, I think probably just over 20 years ago.
P
20:43Phil GoddardGUEST
So very clear ideas.
P
20:44Phil GoddardGUEST
You structure your systems around business domains that are in value, and those domains have clear boundaries and explicit interfaces between them.
048- Building for Betting: Why FDJ United Built Their Own Data Platform Instead of Buying One
P
20:27Phil GoddardGUEST
But data mesh ultimately is an organizational model that draws on domain-driven design.
P
20:35Phil GoddardGUEST
So domain-driven design is a software engineering philosophy introduced by Eric Evans, I think probably just over 20 years ago.
P
20:43Phil GoddardGUEST
So very clear ideas.
P
20:44Phil GoddardGUEST
You structure your systems around business domains that are in value, and those domains have clear boundaries and explicit interfaces between them.