you’ll discover that a majority of programming is debugging – discovering errors
FWIW, this is not my experience. By leaning heavily on the compiler and making liberal use of assertions, I am able to reduce the total amount of time spent debugging to a small fraction of my total effort.
Most of my programming time is spent cycling through designs. I come up with a new design and it takes a while to flesh it out. Then, often, it turns out the design is fatally flawed in a way that was not obvious at the outset. So all the time it took to implement the design was wasted.
FWIW, this is not my experience. By leaning heavily on the compiler and making liberal use of assertions, I am able to reduce the total amount of time spent debugging to a small fraction of my total effort.
Most of my programming time is spent cycling through designs. I come up with a new design and it takes a while to flesh it out. Then, often, it turns out the design is fatally flawed in a way that was not obvious at the outset. So all the time it took to implement the design was wasted.
You aren’t working with your own code most of the time in most programming jobs.
Good point, and thanks for reminding me that I’m lucky to be in a position where I DO work with my own code most of the time.