This post is mostly an ad to make people click the https://calendly.com/gurkenglas/consultation link starring in my Would you like me to debug your math? post.

But writing just an ad feels icky to me, so first:

The advice that was most useful to most people

was on how to use (graphical) debuggers. The default failure mode I see in a programmer is that they're wrong about what happens in their program. The natural remedy is to increase the bandwidth between the program and the programmer. Many people will notice an anomaly and then grudgingly insert print statements to triangulate the bug, but if you measure as little as you can, then you will tend to miss anomalies. When you step through your code with a debugger, getting more data is a matter of moving your eyes. So set up an IDE and watch what your code does. And if [...]

---

Outline:

(00:16) The advice that was most useful to most people

(01:34) The ad

The original text contained 1 footnote which was omitted from this narration.

The original text contained 1 image which was described by AI.

---

First published:

Source:

Narrated by TYPE III AUDIO.

---

Images from the article:

Apple Podcasts and Spotify do not show images in the episode description. Try Pocket Casts, or another podcast app.