"don't just make the change, make it easy to make the change first, and then make the change" is probably good software practice but does not play well with being impatient and wanting rewards NOW
Conversation
Replying to
I usually follow "make all the change at once then crash and burn, realise your folly, then make it easy to make the change, then forget to make the change"
I added the last bit for dramatic effect, and I usually follow through. The crashing and burning is usually real though. I do it a few times on a branch before I know the best way to set up the change and finish it. It's important to have a culture that lets you do that though.
1
1
Show replies