3 ms·
Or find a way to exert and capture more thinking ahead of time. Language may help. May. Similar for tooling. (If you are convinced that they will both autom
by taeric 12y ago
Or find a way to exert and capture more thinking ahead of time. Language may help. May. Similar for tooling. (If you are convinced that they will both automatically help, consider that you can't just give them to a 1 year old and get results.)
It also helps tremendously to limit the scope of what you are doing. One of the reasons the "add print statements" helps so many people is that they reduced the scope of their thinking to be smaller than the entire problem. It isn't, "how can I make this whole program behave," but rather "how can I make this variable what I want it to be?"
There is a trap in this thinking, though. Many feel that if you can reduce everything down to small functions that it will be easier to deal with. This can be true, but it isn't strictly true. If each function is called from many places, then it can become hard to really understand the impact of a change.
- sebastianconcpt 12y agoThis is the voice of the experience talking. Spending "lots of time on debugging" is a signal of lots of reverse engineer that is hard (not easy), probably due to poor method naming (very common problem regardless of paradigm). Is not the language fault that you design sucks.