We all get imposter syndrome sometimes. I’m afraid at least once a week that someone will look at my code or read a blog post and realize that I’m a total fraud and have no idea what I’m doing.
One of the things that each developer asks themselves is Am I Really a Developer or just a good Googler?. It’s a valid question to ask, but one I think has a fairly clear answer.
Good is a hard word
The first stopping point is to define ‘good’. I think it’s fair to say that most developers would say that they are good, then look back at 6 month old code and wonder what ‘hack job’ wrote that.
Becoming a good developer is a path that we are on. It has branches (you can be an awesome WordPress dev and a terrible Drupal dev) that we choose to walk down as we specialize.
So ‘good’ is relative to a certain extent.
A ‘good googler’ is one that can put together the right search phrase in google to get the code that they need.
Then they take it and use it.
A ‘good developer’ is one that can put together the right search phrase in google to get the code that they need.
Then they work to understand it and see exactly how it fits in with their current work. Then they take that solution and use it as appropriate (copy/paste or maybe edited) in their current work.
I think the key difference there is understanding and it applies to more than just developers.
A good designer takes the inspiration of other sites and looks at the current project. They use elements from other designs that inspired them in the new project as it fits appropriately to the project.
A good business owner takes a look at other successful business practices and then takes a look at their business. They use the practices as appropriate (sometimes copying sometimes tweaking) in their own business.
If you just take the code from someone else and have no idea exactly how it really works, you’re a good Googler. Most of us were there once though we just didn’t stop there. At some point I realized that I was just a good Googler and from that point on worked hard to understand the code that I was using. No code that I didn’t understand went in to projects anymore.
That was the starting point of my path on the way to being a good developer.
So if you ask me if you’re a good developer or just a good Googler, you’re going to get a bunch of questions about understanding the code you’re using. Then at least I’ll know you’re on the path to becoming a good developer.