4 ms·
But don't underestimate the importance of reading as a skill! It's incredibly frustrating to see devs make stupid mistakes and spend time trying to get somethin
by jspash 5y ago
But don't underestimate the importance of reading as a skill! It's incredibly frustrating to see devs make stupid mistakes and spend time trying to get something to work when the answer is right in front of their nose.
I see this too often. A developer (usually more towards the junior end) who think they can just chug through any problem. Trying this, then that, then google, then that again. When, if they would just stop and think through the problem - and use their eyes - they would see the solution was there all along.
- filmgirlcw 5y agoTotally agree. I’ve definitely made this mistake myself (we all have) and the lesson is definitely to stop, think, read the code and that usually helps with the solution (or at least makes it easier to hone in on what to google)
- manuel_w 5y agoI sometimes see this with C++ compiler errors. People don't even try to understand them. They just change some random things and copy/paste some snippets from Stack Overflow, and finally request help instead of just investing a few minutes to actually understand what the compiler has problems with. Yes, g++ compiler errors are heard to read, but often the needed information is right there.