CARPENTERS AND CARTOGRAPHERS

on YouTube ↗25m

" summary

Argues that treating programming as craftsmanship leads to attachment and brittleness and proposes treating it first as exploration: use cartographer's mindset to discover mathematical abstractions (functor, monoid, applicative from category theory), apply DDD to extract domain algebras, then use Freeman-style interpreters to map those algebras to concrete systems. Claims this two-step — map then build — reduces waste when requirements change and makes composition lawful where object metaphors fail, so teams should map complexity before committing to carpentry.

AI-written summary · about

" chapters (5)

1. 0:00Start
2. 8:01Problems with Metaphors
3. 12:53Design Patterns
4. 14:02Capital Carpenter Mindset
5. 20:35Alfred Korzybski

" related talks

• 11mCarpenters and CartographersValentin Kasas · LambdaConf 2017
• 52mProgramming is (should be) fun!Gerald Jay Sussman · Scheme 2022
• 22mDo We Need Software Craftsmen?Christian Rauscher · WeAreDevelopers Conference Vienna 2016
• 50mRiding the wave of complexityMarkus Fanebust Dregi · NDC Oslo 2023
• 26mSolving the problems in front of youRandy Au · PyData NYC 2023
• 09mTalks with Brian Troutwine about His Code Mesh TalkAlvaro Videla, Brian L Troutwine · Code Mesh 2017
• 55mDigging into the Matrix: Practicing Code ArchaeologyArthur Doler · NDC Oslo 2025
• 34mFinding a Way OutChris Granger · Strange Loop 2013