Am I really a developer or just a good Googler?
&gt;&gt; Third, try programming for a day without Googling. Then two days, maybe a week. See how it feels. Remember that there was a time we programmed without copying our work.<p>It&#x27;s not usually, or even often, about copying work for me. I google because there is no freaking way I can remember all the details of linux, python, bash, regular expressions, flask, elasticsearch, redis, haproxy, postgresql, mongodb, Google Cloud Platform, kubernetes, logstash, kibana, Java... that&#x27;s a real list from my last project. If you were going to hire me for a position doing roughly the same thing, and you stuck me in a room and picked questions off a list related to those things I set out above, with the understanding that I am good enough for you if I can answer the question, and not good enough if I can&#x27;t... it&#x27;s a crapshoot. 100%. I may have spent hours preparing for the interview. You may have spent hours preparing for the interview. And then you ask me something like &quot;In an elasticsearch mapping template how would you retain the untokenized value of a string for use in a returned list of aggregates?&quot; and maybe I did that yesterday and remember, or maybe we should just both go back to whatever we were doing before we met.<p>I&#x27;m interviewing right now, and if you can&#x27;t tell it&#x27;s frustrating. I&#x27;m not valuable unless I am experienced and capable with a huge list of technologies, and hey, as a reward you the interviewer get to pick anything you want from that huge list and try to trip me up with it! ;)