Re:Am I really a developer or just a good Googler?
by evli on Wednesday April 02, 2014 @02:08PM
(#7517657)
I think that is some value in doing that, for learning. But as a professional, with deadlines and money involved. Wouldn't google be best?
Re:Am I really a developer or just a good Googler?
by the_cat_kittles on Wednesday April 02, 2014 @02:21PM
(#7517779)
right- there is a time to learn and a time to earn. though, accreting a bunch of solutions that you may not appreciate can sometimes screw you in the later term
Re:Am I really a developer or just a good Googler?
by incision on Wednesday April 02, 2014 @02:48PM
(#7517992)
>"But as a professional, with deadlines and money involved. Wouldn't google be best?"
I actually meant to say something about this in my original post.
There's definitely something to be said for going straight for a solution if you write code for a living.
Though, I'd be hesitant to say Google is best without a qualifier. It's a great tool and incredible reference, but you'd have to think about the value and potential liability of a developer who is committing Googled code he/she doesn't fully understand.
Re:Am I really a developer or just a good Googler?
by mordocai on Wednesday April 02, 2014 @02:17PM
(#7517739)
That was my first thought as well. I think that it is a great idea to experiment when working on personal projects/something with little to no deadlines. However, when the project is due yesterday and you come across something you don't know how to do... I have to say google is best.
Re:Am I really a developer or just a good Googler?
by ritchiea on Wednesday April 02, 2014 @02:34PM
(#7517888)
I have grown a lot in the last few months by consulting library code & documentation first when I hit a road block & only turning to Google/Stackoverflow if I hit a weird error message I don't understand or shit really hits the fan. One major benefit of opening up the source code when I'm using a library is it often sparks my interest to return to that library later just to learn more about how it works.
Once I decided I really wanted to learn to write code I just plain stopped with the copying and even referencing anything beyond docs or a thorough book.
I work to create a functional implementation of whatever it is I'm looking for, no matter how naive, convoluted or narrow my solution ends up being.
Only once that's done do I go about searching out solutions. Sometimes I'm delighted to find that what I've come up with comes very close to established solutions, other times I learn some new, concise way of going about the problem.
In any case, that first sort of experimental phase is incredible for informing everything that comes after. I'd say experiencing 100 less than optimal ways to do something is far more valuable than memorizing a single optimal solution.
Thing is, around the web, this sort of approach seems pretty ripe for ridicule as the Internet standard response is something like this [0].
There's a culture against discovery and creation. You either come out of the womb writing clever, idiomatic code and using or the hottest framework/library or you're an idiot.
0: http://harthur.wordpress.com/2013/01/24/771/