Spring is bootiful but so is your domain
summary
Claim: domain knowledge raises developer value by producing more maintainable code, better module boundaries, clearer communication, and product influence. Uses collaborative techniques like design level event storming and canvases like business model canvas. Example: a mortgage scoring engine validated with 5,000 Excel test cases reveals that developers’ assumptions—not specs—ship to production; refactoring to reflect business clusters takes two days and makes a new requirement immediate. Also cites event storming, example mapping, and explicit assumption capture.
AI-written summary · about
chapters (65)
- 0:00Introduction
- 1:28Business and money
- 2:03About me
- 2:16Spring Technologies
- 2:27Sorry not sorry
- 2:46Motivation
- 3:23Dont be afraid
- 3:36You will be more valuable
- 3:57Better modularization decisions
- 5:50Better communication
- 6:43Better code
- 7:03Market expectations
- 7:28User experience
- 7:56The key to incremental architecture
- 8:46There is another quote
- 8:56Who has heard about that book
- 9:39What does that mean
- 10:35Alignment between software and
- 10:51What goes into production
- 11:44Story time
- 12:14Organizational setup
- 12:29Reading the specification
- 12:46Starting point
- 13:18Rules
- 14:54Scoring engine
- 15:05Acceptance test
- 16:09New requirement
- 18:08Im stupid
- 18:35Risk Managers
- 19:08Mental Model
- 19:35Refactoring
- 20:07Key learnings
- 22:28Eventstoreman
- 22:43Knowledge crunching methods
- 23:35Design level event storming
- 23:48Unit tests
- 24:24Grouping rules
- 24:40Group Domain Concepts
- 26:13Business Model Canvas
- 27:16Melissa Perry Escape the Build Trap
- 28:07Modularization Options
- 29:54Value Proposition
- 30:51GitHub repository
- 31:10Startup process
- 31:37Communication
- 31:48Hotel room
- 32:27Class names
- 32:42Language leaks
- 33:32Empathy
- 34:28Software Architecture Elevator
- 35:07Communication is important
- 35:26Tech enabled organizations
- 35:56Product thinking
- 37:03Product rating
- 37:41Digitalization
- 38:45Efficiency
- 39:04Improvement
- 39:26Purpose
- 40:22Business Tech
- 40:42Build it you run it
- 41:15Digitalisation
- 41:58Developers understand the business
- 42:32Wrap up
- 43:49Questions
- 47:27Abuse
related talks
27m'The Art of Software Development'
42mThe Monster Coming Over The Hill
25mHow to Leverage Domain Expertise
33mWhat it takes to become a great developer!
51mThe Art of Software Development
26mHow open-source made me a better developer
20mFailing Can Be Good! Bringing a Growth Mindset to Every Project
27mBeyond developer