Gemini's Development Practices - How to Create Sustainable Software

Hello! This is Gemini.
My Resume Guide from a CTO who has reviewed 10,000 resumes, featuring my unique perspective and insights, is now open!

📍Go to the Resume Guide by a CTO who has reviewed 10,000 resumes!!🔥

Course Introduction

Facts revealed by 10,000 resumes

There is no common formula for a passing resume, but
failing resumes have repeating patterns.

10,000 people have 10,000 different charms.
However, many people often fail the document screening process because of resumes that do not properly capture their unique appeal.

I hope you don't give up because of your resume.

Based on the patterns discovered while reviewing over 10,000 resumes,
I will point out the do's and don'ts, as well as the reviewer's perspective, one by one.

What you will learn

Section 1. 15 Things You Should Not Do

Most resumes are ruined not because they are lacking, but because effort was put in the wrong direction. Things included because they seemed like they would look good, show sincerity, or because leaving them out felt like a loss are actually becoming the reasons for document rejection.

In this section, we will point out the bad habits that many people unknowingly repeat one by one.
Once you learn them, there will definitely be things that make you think, "I was doing that too."

Section 2. 14 Things You Should Do

Now that you have removed what not to do, it is time to focus on how to fill the space. There is a clear difference between simply listing your history and creating a resume that actually gets read.

In this section, we will guide you through the practical steps to create a resume that catches the reviewer's eye and moves you to the next stage. A small shift in perspective can make your resume look completely different.

Section 3. The Perspective of the Document Reviewer

If you want to write a good resume, you must first understand the perspective of the person reading it. Reviewers read resumes in a different way and in much less time than you might think.

In this section, we reveal the perspective of a CTO who has reviewed 10,000 resumes. The moment you understand "how my resume appears to a reviewer," your entire perspective on writing a resume will change.

Section 4. Experiencing with Real Resumes

This is a section where you can directly verify what you've learned in theory through actual resumes. It is a time to look at the resumes of current developers together and feel which parts are lacking and which parts are good.

The difference between a good resume and a disappointing one is truly felt when you see it with your own eyes rather than just hearing an explanation. This is a time to personally experience the concepts learned earlier through real-life examples.

Section 5. Appendix

This section is for those who might still have lingering concerns after the lecture, such as, "But my situation is a bit different... what should I do in this case...?" It covers a variety of topics, including concerns about job searching in the AI era, challenges faced by newcomers, and the dilemmas of developers whose experience is limited to improving legacy systems.