Machine Whispering P2: Tips
Some tips I’ve wrote down lately to remind myself. Some of these use only a few words but come after a long, stressful project.
Understand high level purpose / functional objective before trying to understand/debug lower level stuff. The context of knowing overall what’s supposed to happen is very useful.
“What is expected behaviour of ___?” => Just look at the code. At least take a look at the high level function call before you bother someone. Not always as complex as you’d imagine it to be.
Follow through fully on a single piece before doing the first step for a ton of modules. It’s more work to keep having to change code in multiple places once you hit another roadblock. Doing that is like not staggering a deploy in code land. Test 1 before you release to everyone.
Break it up into the smallest pieces possible and test them as you go along. Not at the end!!