Sharing my experiences and thoughts on how I became a GDE (Google Developer Expert)
What can you gain by becoming a GDE?
Quote from Love Cat de Xiao Guo: From the stage to the stage, I became a GDE (Google Developer Expert) experience sharing summary:
GDE is a developer expert certification program carried out by Google around the world. In addition to being a GDE recognition of your technology and influence, you can also get:
Know in advance information about Google's internal product route or technical changes;
Communicate technical issues directly with Google product teams and get some Google beta qualifications;
Google event invitations, such as I/O, and travel reimbursement;
JetBrains will provide free JetBrains family buckets for all GDEs;
Can I be a GDE?
Seeing the many benefits above, you may also think in your heart when you are excited:
Can I be a GDE?
I was in the same state last year when I read Alex sharing my experience of becoming a GDE (Google Developer Specialist).
Psychological barriers are probably the biggest thing holding us back.
When I look back at the entire application process, I can say with certainty:
Yes, everyone has a chance to become a GDE
In my opinion, "GDE is Google's recognition of your contribution to a certain technology, and it pays more attention to your technical influence." This project does not examine academic qualifications, companies, and everyone has the opportunity to become a GDE.
So is it difficult for him? He does not have any threshold, as long as you love a certain technology enough and are willing to pay.
But is he not difficult? You may be wondering how technical contributions are assessed? Let me share with you my preparations for the entire application process.
How do I prepare to become GDE
When you have the will, I would recommend talking to Google DevRel (Developer Relations) first, they will be very helpful in assisting you with your application. I had great support from Lily (Google DevRel) throughout my process. You can get help by contacting your local GDG organization or active duty GDE.
We have three main parts in the whole application process
Submit application form
Community Interview (Active Duty GDE Interview)
Product interviews (Google technical/product people conduct interviews)
In essence, it is to examine the depth of understanding and contribution to Flutter. In fact, in terms of contributions, in my opinion, whether it is open source, articles, issues, or even group exchanges, they have all contributed to the Flutter community at different levels. From a quantitative point of view, it is nothing more than the number of videos played, the number of articles read, and the number of stars of open source projects. The evaluation of influence focuses on the following three aspects, which are also required to be filled in the application form at the beginning: public speaking, content creation, and open source projects
Speech is a very important part of applying for GDE evaluation, especially offline speech. Public means that relevant materials must be accessible to the outside world, and the topics of multiple speeches cannot be too similar. Before applying, I gave three speeches, namely, 2021 DevFest on Fluency Optimization, 2022 C-Talk Flutter State Management Analysis, 2022 Flutter Festival Code Generation Usage Principles The final impact data is as follows:
The speeches I attended were done in cooperation with local GDG and other community organizations. If you have ideas, you can actively contact local GDG organizations to participate, such as community talk projects, or sharing activities like Nuggets and GMTC, of course Remember that recycling data is itself a self-assessment, and active sharing is an important part of the healthy ecology of the community.
The second part evaluates content creation, broken down into blogs, books, or video tutorials, etc. This part depends entirely on personal wishes. I mainly focus on blogging. I have shared some learning records on the Nuggets since 20 years. I have output 30+ articles, 22W+ readings, and have also been forwarded by the Google official account many times. There are basic introductions, and some relatively complex analysis. The same is true in the community, there are a lot of popular content, and there are also dry goods produced in depth. But it seems to me that as long as you produce it with your heart, no matter what kind of articles are quite valuable, they can solve different kinds of needs.
And content creation I think is very important for individuals, not only on a technical level. Because in my opinion, content is actually a carrier of a person's thinking logic. This is particularly obvious from the data feedback. At present, I have an article with the highest comprehensive data. Take it to you! Flutter imitates the naked-eye 3D effect of the App. In fact, it is facing the complete mental journey of a project. At that time, it was writing articles and codes at the same time. Go through the steps of the article to disassemble the whole thing, and find solutions in turn. The article is written, the code is running, and the whole process is very smooth. If the article is not clear, the data will be much worse, so I am also trying my best to write more content that can resonate with everyone. I would like to share "The Pyramid Principle" and "Break the Ink to Find a Path" for related training. I also had a simple summary last year: my writing journey and personal growth
Therefore, creating content with heart and actively sharing it is meaningful for the individual or the entire community.
open source project
In addition to the release of keframe and bruno in open source, I think the collaboration of the Flutter Chinese community is a very bright part.
Real-time synchronization and accurate official localization data is an important part of lowering the technical threshold. Flutter.cn is currently the only Chinese data that is synchronized with flutter.dev, and is maintained by CFUG.
I also started getting involved in localization after meeting Vadaski by chance last year. Completed the translation of 10+ documents and participated in the review of multiple PRs. It was an honor to join CFUG and meet Vadaski, Alex, MeandNi, Luke
Several very thoughtful and reliable partners.
There's still a long way to go, so if you're willing, you're more than welcome to start with the Translation Workflow.
Some of my thoughts after becoming GDE
After 19 years of its peak period, it is gradually found that there are more and more voices questioning Flutter.
Lala Android Stability Management:
In order to cope with frequent changes in demand and improve R&D efficiency, Flutter and applets are used to pull the homepage and confirm the order page.
And this part is the page with the highest user usage rate, the amount of code is huge and complex. A large number of crashes are generated in the online environment,
We decided to sort out the logic and let the most important part of the code return to the original. After the refactoring went online, the crash rate dropped significantly.
These words are part of the current attitude towards Flutter, and also reflect some of the problems of Flutter, but what is the real situation? No one can tell.
But in my opinion, there is no doubt that Flutter can improve efficiency, and in some scenarios, efficiency is really the killer, and Flutter is still the first choice.
And from the data of Google play, Flutter is also the most widely used cross-platform framework.
Surely, Flutter must be the ultimate cross-platform answer? No one knows the answer, and I have the same question.
During the interview with the infra team, my leader shared a lot of insights that impressed me.
He doesn't think so, but it doesn't matter. The core competitiveness of developers must be the ability to solve problems. What problems do we face in the process of using Flutter? How is it solved? Much knowledge can be transferred when sufficient depth is reached. We can't predict what the future will look like, so think more about what you have paid and gained in this process? Furthermore, the development of a technology has a lot to do with the ecological activity of the entire community. At present, no matter the official investment or the atmosphere of the community, it is obvious.
This also dispelled my doubts. I often dived to see fluttercandies, a good discussion atmosphere and a large number of excellent open source works in leanflutter, as well as contact with aspiring and reliable partners in work and the community. If you think things are not that important, just enjoy the process.
Moreover, in today's downward market environment, it feels almost impossible for programmers to lie flat. I have come into contact with a lot of people who are more senior and more self-motivated. Therefore, I think GDE is a label for my current efforts, and it is also a spur.
"Keep a positive and open attitude, keep learning, keep sharing. Don't feel inferior or arrogant. Don't be anxious, don't lie flat. Exercise your ability to solve problems and contribute to the development of technology as much as you can. This is my current understanding."
The world needs more GDE. If you want to become GDE to influence more people, I hope my shallow experience can give you some inspiration. You can also check out other great GDE pasts:
Love Cat de Xiao Guo: From offstage to onstage, I share my experience of becoming GDE (Google Developer Expert)
Alex: Sharing my experience as a GDE (Google Developer Expert)
Guolin: Sharing my experience of becoming GDE (Google Developer Expert)
Knowledge Base Team
Knowledge Base Team
Knowledge Base Team
Knowledge Base Team
Explore More Special Offers
50,000 email package starts as low as USD 1.99, 120 short messages start at only USD 1.00