4 ms·
I’m not smart enough to program quickly and correctly in Clojure. I think it follows the same ethos Rich Hickey has about unit testing being “guard rail driven
by almost_usual 4y ago
I’m not smart enough to program quickly and correctly in Clojure. I think it follows the same ethos Rich Hickey has about unit testing being “guard rail driven development”. I watched him talk about this a decade ago at Strange Loop.
To understand your whole program all the time at scale is probably something Rich Hickey is capable of but I definitely am not.
- Spivak 4y agoWorking in a huge Ruby codebase, I know not the same, but still super super dynamic my approach is 1. If I don’t understand what code does just delete/noop it and see what tests fail. 2. Write my assumptions into new tests to be very loud people if someone wants to break them. Easier said then done with frameworks/callback patterns that want to call my code from god knows where but really powerful when you’re pulling a value. 3. In the case of callback spooky object at a distance stuff be strict about what you accept and fail loud.