Technology
Do Googlers Need to Google Code Stuff Frequently?
Do Googlers Need to Google Code Stuff Frequently?
Googlers, like many professionals in tech, frequently use Google to find information resources and solutions related to coding and development. This could include looking up documentation, searching for coding best practices, troubleshooting errors, or exploring new technologies and frameworks. The fast-paced world of technology makes it crucial for developers to stay updated and/or troubleshoot regularly, sometimes on a daily or weekly basis, depending on the project and the challenges faced.
Unique Challenges with Internal Tools
But what about Googlers themselves? In many ways, Googlers have their own set of challenges when trying to find relevant information. It is remarkably hard to find information about Google's own technology, thanks to the unique structure of their internal search engines. These tools, one for code and one for documentation, are designed to find what exists about the company’s technology. However, just like external searches, they can be lacking in terms of thoroughness and organization.
The internal documentation at Google can be challenging to navigate, and it isn’t well-organized. This problem isn’t unique to Google and Google does it better than most.
Revisiting the Frequency of Google Searches
Interestingly, despite the challenges, I have found that I don’t Google for coding-related stuff as much as I used to. This may sound counterintuitive given that I have only been working at Google for a year and three months. However, there are specific factors that contribute to my reduced search frequency:
Niche Language Usage
My primary language for work is Dart. Being a niche language mostly used within Google, there isn’t much to look up. Additionally, I often hear and read about additions to the language before they happen, thanks to the internal communication channels within the company.
Using an Integrated Development Environment (IDE)
I use IntelliJ for work, which provides comprehensive code completion. With this, I can easily view an object's API without needing to perform an external search. Furthermore, tools like Chrome DevTools and IntelliJ's project-wide search and go-to-definition features allow me to hunt down the cause of an exception within our codebase, all without leaving the IDE.
Learning from Experience and Documentation
Using fewer languages has also contributed to my reduced need for external searches. In school, I was often using several different languages in a single semester, but now it is primarily Dart, with occasional use of Java. Adding to this, my deep understanding of Dart has allowed me to use resources like DartPad, an online playground for Dart, to test and understand code.
Advisory Note
It's important to note that the act of Googling for code is not inherently bad. However, it's crucial to use it as a means to learn and understand solutions rather than just copying and pasting code. The intent of this article was to highlight the skills and situations that might lead to decreased searching, rather than implying that Googling should be avoided.
Conclusion
In summary, while the need to Google for coding-related information exists, Googlers can reduce their reliance on external searches through the use of internal tools, specific work languages, and comprehensive understanding of the tools and languages in use. This approach not only helps in saving time but also in gaining a deeper understanding of the technologies used within Google.