3 ms·
But do I really need or want to know, remember and understand the nuances of each and every of my problems? For example, we have a lot of legacy Delphi code.
by Deestan 16y ago
But do I really need or want to know, remember and understand the nuances of each and every of my problems?
For example, we have a lot of legacy Delphi code. Delphi 7 has a bug in which it gives incorrect compiler warnings for some of it. I don't care one bit about the history, details and nuances of the bug. The 2 hours I don't spend examining that are 2 hours I can spend learning something useful instead.
- RiderOfGiraffes 16y agoExactly - it's not binary. It's not yes or no. It's not everything or nothing. * There are cases where the fastest thing to do is ask your colleagues. * There are cases where the fastest thing to do is ask your friends (if you have any). * There are cases where the fastest thing to do is ask Google. * There are cases where the fastest thing to do is ask StackOverflow. But there are times when it's best (and not necessarily fastest!) to work on it for a while to see if you can either solve it, or at least get your mind around it enough to understand the solution when it comes. The very best programmers/engineers/employees/founders/people know when it's which case from the above.