Understandable that you’d want to exploit any resource that can give you answers during a time crunch.
But if given enough time, going through the pain of debugging and fixing something on your own – with at the most some documentation – is still superior.
If one has learned, knows and remembers the first principles of their domain, then knowing what to Google becomes less valuable (not saying your colleagues don’t know their stuff). You can rely on yourself for even the trickier situations you get into.
Agreed, this is what I strive for but rarely do it in practice. Somehow, you are always in a hurry, you always want the solution now!. I think this has to change, the initial time spent on the understanding the debugging process has immense long term benefits.The time to solution decreases with time, in my kind of approach it remains linear or sometimes even increase.
But if given enough time, going through the pain of debugging and fixing something on your own – with at the most some documentation – is still superior.
If one has learned, knows and remembers the first principles of their domain, then knowing what to Google becomes less valuable (not saying your colleagues don’t know their stuff). You can rely on yourself for even the trickier situations you get into.