2 ms·
Completely agreed on the "slow down and really read" part. Googling for immediate answers on Stack Overflow is not reading and doesn't lead to understanding. I
by pavlov 10y ago
Completely agreed on the "slow down and really read" part.
Googling for immediate answers on Stack Overflow is not reading and doesn't lead to understanding. It's "fast food calories" for your mind, and if one solves every problem that way, it's like eating at McDonalds for every meal.
- Strom 10y agoGoogling for immediate answers on Stack Overflow definitely leads to understanding in my case. The trick is to not just immediately paste the code, but to dig into it and understand why that specific set of instructions is the solution. A bit of reverse engineering if you will. It tends to be faster than reading through all the docs (which contain too much info about things you won't need right now) and inventing the wheel yourself.
- marktangotango 10y agoI don't know why you're being downvoted, this is a good insight. Particularly in the Java Enterprise world, the documentation can be very wordy, and of the form 'indoctrinate you into this way of thinking'. A barebones example from someone who knows the framework can be much more illuminating than pages of prose.