2 ms·
Working 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
by Spivak 4y ago
Working 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.