part3 – Neal Ford
summary
Argues that building software around domain specific languages reduces noise and makes intent visible, contrasting Java boilerplate with select from customer and Ruby on Rails’ validates presence of :name. Distinguishes internal DSLs (Java, Groovy, Ruby) from external DSLs, and shows a concrete result: a Java fluent interface for railcar leasing where setters drop “set” and return this*, exposing business rules like tanker/milk constraints so business analysts can read and approve them — it works in practice.
AI-written summary · about
chapters (14)
- 0:00Waffle House
- 1:13Jargon
- 1:31Leetspeak
- 2:24Developers
- 2:52NonDevelopers
- 3:11Business jargon
- 3:39Domainspecific language
- 4:04Orient programming
- 4:30Java
- 5:18Coffee
- 5:43Noise
- 6:11declarative code
- 7:17types of dsls
- 8:19Example
