HackerHammock Driven Development - Rich Hickey
ClojureTVYouTube ↗
Further reading 2
Does splitting code actually split its dependencies? →Start with a rule that sends an email. Separate deciding from doing, then inspect layers, objects and abstractions: which parts must still change together when the rule changes?This video helps answer · When is it time to stop coding and rethink the problem?After an edit, how can you see what actually changed? →A green test, a live picture and a replayable history all count as feedback. Follow one edit and ask which consequences become visible and which still need reflection.This video helps answer · Must we choose between reflection and instant feedback?
Caption notes
Write down the actual problem, constraints and alternatives before implementing. Time away can reorganize the problem; running the solution still tests the assumptions.
Original passages · 6
problem s of misconception are not generally addressed by testing or type systemsyou have to look at at least two solutions to your problemlooking at other solutions to the same problem is the number one waywhen the facts change do not dig in do it over againmost of the big problems we have with software are problems of misconceptionyou're going to try stuff and go back