|
|
|
|
|
by b5n
1467 days ago
|
|
I'm a bit older so ymmv, but I rarely end up on SO. If I'm trying to figure something out most of my time is spent in the reference/documentation/source. If the docs lack examples and I'm having trouble visualizing a particular feature I might look to another project that consumes the same lib for examples. I encourage my younger colleagues to do the same. SO can be a great starting point, but it's in your best interest to take what you've found and then consult the docs/source (depending on what you're working on). Many times you'll find a better fit for your particular solution than what was presented on SO, and at the very least you come away with a more complete understanding. If you have a solid grasp on something trivial you've copied, I might jest a bit, but have no real problem that it was yanked. If you don't understand it and it 'just worked', that's gonna set off some alarms. |
|
But at a higher level there's principles that you need to understand in order to write robust code where you can't google the answer. And most SO/wikipedia answers to anything non-trivial will not be robust. And then there's the "ungoogleable" problems where you just need to roll up your sleeves and fix it. That can sometimes be broken down into tasks which are google-able by asking what kind of tool you need in order to investigate the problem -- and then using google to go find a tool that does that and learn about it.