RAMPS - Ways to Affect Mastery | #16

"We talked about the widespread pernicious conceptual cluster we call "finish-line efficiency": the idea that software development is basically a race, w/a start, a well-marked track, and a precise finish line some distance away. Overturning this is central to engaging mastery. I'm always chary of simple mappings from software development to the physical domain. But if it resembles anything like "getting from here to there", the thing it most resembles is an exploratory expedition across an unknown continent. In a simple race, we tune to be running machines: perfect stride, optimal pathing, minimal awareness. Don't move laterally or in reverse. Don't find shortcuts. The target stays still. Fuel up before & after. We *follow* the path, we don't *create* it." Episode 16 is now live. If you have any feedback you can always tweet @GeePawHill on Twitter, or drop a voice message via the voice messages link here on Anchor. You can also read the full transcription of the podcast over on GeePawHill.org.