[deleted]
Get better at Googling
121–130 of 297 posts
Re: Get better at Googling
#122I was one of the first few cohorts at the first "coding bootcamp" by Shereef Bishay called Dev Bootcamp.
This was the first skill they taught us and they told us the exact same thing.
"You are in the business of learning, learning fast is going to be your greatest skill."
Another insightful principal that I am reminded of often.
"Businesses rarely fail because of a specific technical hurdle, more commonly they fail because the team fails."
This was back in 2013, he was spot on with almost everything he taught us.
Re: Get better at Googling
#123I was one of the first few cohorts at the first "coding bootcamp" by Shereef Bishay called Dev Bootcamp. This was the first skill they taught us and they told us the exact same thing. "You are in the business of learning, learning fast is going to be your greatest skill." Another insightful principal that I am reminded of often. "Businesses rarely fail because of a specific technical hurdle, more commonly they fail b…
When I started my professional career in 2000, Google was my secret weapon. It's also one of the things that kept in the areas where I've specialized, as my personal ability to find information on the internet is much better than dealing with intra-corporate dreck.
Re: Get better at Googling
#124Sometimes Stackoverflow own's search is better than Google.
Re: Get better at Googling
#125Earlier quoted context omitted.
How do you find the docs? Do you just keep a giant list of bookmarks for every project and sdk you might use? Or, do you Google the docs?
Yes I keep bookmarks or often document the links in my brief of the project. Or I've used the links so much I know the site path to get to a doc. You're trying to find a hole in my logic, but you're ignoring what I'm saying: Searching the web isn't an important skill, just as going to the library to research isn't an important skill. The skill is reading, research, and organizing research itself. Google just makes it…
You're right that the real skill is not googling, but it seems like you're doing the same thing as everyone else. You don't have all the syntax and functions memorized, so you have to look things up occasionally, ya? You just skip Google and go straight to the docs. Googling is so quick though, any efficiency lost over clicking a few links seems minimal and not worth arguing about.
Re: Get better at Googling
#126Google is okay for research on how other people have achieved something. But generally these days I am of the opinion it just teaches you bad habits. I really wish people would just read the docs instead of just googling. I am working on a large typescript solution and almost every error in the application is due to the original developers not reading the docs and instead just googling stuff from stack overflow. Also…
DDG uses Bing.
Re: Get better at Googling
#127Google is okay for research on how other people have achieved something. But generally these days I am of the opinion it just teaches you bad habits. I really wish people would just read the docs instead of just googling. I am working on a large typescript solution and almost every error in the application is due to the original developers not reading the docs and instead just googling stuff from stack overflow. Also…
> I really wish people would just read the docs instead of just googling. I am working on a large typescript solution and almost every error in the application is due to the original developers not reading the docs and instead just googling stuff from stack overflow. It's a bit more complicated than that. I do read the docs, but using the web is essential for me, for a few reasons: - nowadays, a dev doesn't work on a…
> best practices may not be obvious even when reading the docs
I am right now working on a project because of the googling stuff has led to the worst practices at the moment. I have worked on many projects where people haven't bothered reading the docs and I have seen the same pattern for over a decade.
Whereas if they had read the docs the best practices would have been immediately apparent. So that argument hold no water with me.
> one can't assume that in a big doc, it's obvious where the solution for a problem is, which may force to read way more than expected
I want people reading more. Which was part of my overall point. People don't read enough. They go for the quick solution (which is copy and paste from stack overflow) produce something which is usually quite bad and then you normally have to redo that work because the moment you try to change something (due to changing requirements) the whole thing falls to pieces.
I've been guilty of it too. It is a bad habit that is produced through laziness.
I literally wrote docs at a previous place and people kept on asking for help on IM. I wrote the document so I wouldn't have to answer the same questions many times. People getting into bad habits and not looking for or writing docs literally causes a hell of a lot more issues that you would see at first glance.
> Thinking about it, the major problem seem to me unprocessed copy/paste, rather than "googling instead of RTFM'ing".
I would rather have a unprocessed copy and paste then what you get in reality which is a "copy pasta". There are minor bits changed which make it difficult to recognise where it may have originally come from, which makes it difficult to know the original developer's intent.
Re: Get better at Googling
#128Discussion on a far more comprehensive article (though perhaps aimed at more in-depth needs) the other day:
Re: Get better at Googling
#129[deleted]
Re: Get better at Googling
#130I was one of the first few cohorts at the first "coding bootcamp" by Shereef Bishay called Dev Bootcamp. This was the first skill they taught us and they told us the exact same thing. "You are in the business of learning, learning fast is going to be your greatest skill." Another insightful principal that I am reminded of often. "Businesses rarely fail because of a specific technical hurdle, more commonly they fail b…
When I started my professional career in 2000, Google was my secret weapon. It's also one of the things that kept in the areas where I've specialized, as my personal ability to find information on the internet is much better than dealing with intra-corporate dreck.
It's 100% a competitive edge to be able to adopt new technology faster than others. "The future is here it's just not widely distributed yet". Kudos to you for recognize that early on.
It's funny that hiring for this skill it still uncommon.