News for hackers. Stuff that matters.
Re:The Tao of Programming (1987) by _hardwaregeek on Monday January 28, 2019 @11:17PM (#19023723)
I really get 4.4 for some reason:

> True, sometimes there are difficult problems. I see them coming, I slow down, I watch silently. Then I change a single line of code and the difficulties vanish like puffs of idle smoke.

I've started to debug like this. Sure, I also actively debug by adding print statements and manipulating my code. But there's something to be said about just thinking and waiting for the answer.

Re:The Tao of Programming (1987) by BossingAround on Tuesday January 29, 2019 @03:25AM (#19024706)
Interesting. Generally, what I do as the first step is immediatelly connect a remote debugger and debug the piece of code that I think is problematic (which is correct in around 90% of the times for me). Then, the answer is generally trivial. I started doing this because it felt way more time efficient than staring into the code and trying to think what goes wrong over there.
Re:The Tao of Programming (1987) by yellowapple on Tuesday January 29, 2019 @03:00PM (#19029347)
I've found that sometimes there's additional benefit to the "take a step back and think about what the code is actually doing" step, in the sense that doing so helps gain better knowledge about how the code actually works and often reveals opportunities to simplify the design (sometimes in such a way that ends up inadvertently fixing the problem, though admittedly it'll more often just introduce more bugs ;) ).