4 ms·
1/ Work backwards from results. Start with an outcome that you want and then figure out what minimal change in the code will produce that outcome. 2/ Have a re
by asimjalis 5y ago
1/ Work backwards from results. Start with an outcome that you want and then figure out what minimal change in the code will produce that outcome.
2/ Have a reproducible process (could be manual) to test that the change you made did not break things.
3/ Spend time on things where you can produce results quickly. Bail on things that are taking too long.
4/ Take walks and think about what is going on. Are you solving the right problem? Is there a different approach? Should you switch jobs?
- chousuke 5y agoI'd like to add to point 1 a plea not to do the thing where people don't understand existing code so they copy it, partially modify the logic and then add branching to choose the correct version. It's fine in moderation to do this, but it increases your maintenance burden faster than it solves issues if you don't ever refactor.