Dev confession.
Everybody in my department thinks I am a genius programmer.
I am just a better googler who knows how to apply things.

Professional googler.

Major requirement of becoming a developer is being a good googler

A long time ago on a project far far away, I didn't realize there was a src folder, and made my changes in the build folder instead... And to makes matters worse, I asked a co-worker -- an ex-Googler -- for help with the issue I was working on.

Rarely have I been more embarrassed.

Lol programmer === master googler
#HateBeingCalledIT
#DeveloperNotComputerRepairMan

Not Sure,
If I am a good programmer
or a good Googler :P

I just developed full iOS app without previous knowledge on iOS.

Am I a good developer, or a good Googler ?

Am I a developer or a professional Googler?

Teacher asks the class:
"How do you become a good developer?"

All the students starts talking about algorithms, problem solving or working in a team.

He nods and starts writing on the board. w w w. g o o g l e . c o m
He then leaves the classroom.

So here I am years later, a master googler and a expert stack overflower.

For being a student and working as freelancer you need to be pro googler, otherwise you'll fail in both.

Agree?

What should I do to practice being a "good coder" vs a "code Googler" who slaps other people's code into the site just because "it's enough to get the damn thing working"?

I feel really overwhelmed with all that Ive learned thus far. At this point I feel width with know depth when it comes to my knowledge of websites.

I've been messing around with html/css/js for a while and played with plenty of other languages,pre-processors, frameworks, etc. I never went to school for programming and have done work for small businesses independently for some time. Most of what I know comes from codecademy treehouse and similar sites. I can refer to Google on a lot of things but I feel like there are habits that I should be implementing so I don't have to re-do things later. I love the book apart series but I still feel like it's missing the foundational knowledge that I'm looking for.

After all of the time I've spent going through courses I feel like my experiences have given me solutions to build a few things and now I'm just jamming those solutions onto whatever I can until something I like comes on to the browser.

It's really easy to sit down and bang my head against the keyboard until something comes out that looks the way I want it to. However, I know there is way more going on that could help me make better decisions. I just feel like I'm missing something. Maybe it's experience, or maybe it's just the lack of commroddery from working alone and not being able to approach problems with a team.

I hate pulling up my css file and feeling like it's rubbish, and feeling like I don't completely understand things like flex, or display, or position. I've been pushing at this for a while but I don't think I've found a resource that has really made me feel like I'm anywhere close to being a competent coder.

There are tons of watch and learn and do type classes that show you how to make stuff, but I guess what I want to know now is why we make it that way.

At some point do you just sit down and read the MSN start to finish?

I wonder sometimes if my brain has been reprogrammed because I grew up in Google world and don't actually have to solve anything for myself. I read about a guy who locked himself away for hours with books on code and he just sat there and wrote his code on paper until he was confident that he was getting it right.

There was this tech guy in our project. I don't really know how techy nor what his role was, but I do know he was a techie.

Lately we'd noticed he was behaving more and more managerish. Orchestrating resources over slack, scheduling meetings, the managerial slang... Bulletpoints... It was obvious what's going to happen - he was striving for a manager's chair. Cool. He seemed like a guy who can indeed do this well. And the fact that he's a techie was promising - he should understand so many things.

Boy did that come around and bite us in our asses. Turns out this guy is a googler. If we are working on some case [as we always are] he jumps in and offers his opinion, although he is far from our technical area. We explain how/why it is not a good idea. Then he does some googling and comes back with a different idea! And insists on testing it out... FTR, a single test in our project could take from 1 to 6 hours. And he's a manager now!! We can't just ignore his requests...

Allright, we do that testing. Results are far from satisfying. We continue investigating. He does as well. We'd like to try something out, but there he comes with a new idea! And ofc we are asked to test it out as well.

Our own testing is postponed again.

A few days like this one pass by. In a daily meeting we are blamed for taking that long to do our investigation and we are questioned as engineers.

Superb...

Honestly? I'm having second thoughts about this new role. It's supposed to be fun and challenging and all, but this kind of shit is just too much...

As a professional googler (who has recently included the skill on his resume too), I wanna ask you all, what googling tips and advices you got you wished others that you're working with knew?
I'll start with one simple and clear one myself:
Start with a wide search, then narrow it down with including and specially excluding keywords. don't start too specific as you might not be familiar with the language of the subject and the way it's addressed.

Which is the best Android Project Structure 😂 we beginners always wonder and the experts tell us to Google, am I a wrong googler