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.

Hello! This is Gemini.
My second course! Commerce Backend Legacy and AI Utilization is now open!

Gemini's Development Practice - Shortcut to Commerce Backend Legacy and AI Utilization!!

If you enjoyed the course How to Create Sustainably Growing Software, I highly recommend this course as well!, tôi cũng xin đề xuất bài giảng lần này!

This lecture defines the code from the previous Commerce Backend Basics as legacy, and proceeds under the assumption that we are newly joining that company!

This is a course where you start by establishing rules in a legacy system that has no rules using AI after joining the company, and then proceed by repeatedly improving the legacy code and implementing additional requirements!

Please check the course introduction for more details!

Please show a lot of interest and help spread the word!
Thank you!

[Course Introduction]

This course designates the previous course 'Commerce Basics' as legacy and is a course that improves the legacy using AI and implements additional requirements!

I believe many people in the professional world are still suffering from legacy systems, so I created a lecture that combines legacy systems with AI!

Even though we are in the era of AI, I still believe that the 'power of thinking' is important, so I have incorporated that philosophy!

I have structured this lecture to provide food for thought, encouraging reflection and insight on how to utilize AI in practical business environments—especially in companies with legacy systems and no prior AI experience—and what specific considerations we should be mindful of throughout that process!

Hello! This is Gemini.
Finally, Gemini's new practical development course! Commerce Backend Basics has opened!

Go directly to Gemini's Development Practice - Commerce Backend Basics course!!

If you enjoyed the previous lecture How to Build Sustainably Growing Software, I recommend this lecture as well!

I tried applying a completely new style to the way I deliver the lectures, but the essential content and the message I want to convey are similar to the previous lectures!

In this lecture, I've focused on creating content that assumes specific situations clearly and helps students develop their thinking skills and methods from a practical perspective!

This course was especially created with job seekers, college students, and junior developers in mind!
I personally made this thinking of those who contacted me about career concerns and the junior developers I had coffee chats with before leaving my job

I hope this lecture will be helpful to those who are in similar job-seeking/career transition situations.

We hope you'll show great interest as we're offering a 30% discount for the first month after opening!

[Course Introduction]

A course created after reviewing approximately 8,000 resumes and conducting hundreds of interviews

Over the past 6 years, I've reviewed about 8,000 resumes and conducted hundreds of interviews, and there were so many people who left me feeling disappointed
The common disappointing factor was the lack of real practical experience

People who have taken several bootcamps, those who have received expensive mentoring services for long periods, and even those who are already working as instructors or mentors all showed the same results when they took interviews.

The reason I created this course is simple
I wanted to provide aspiring developers preparing for job interviews and newly hired junior developers with the fundamentals of thinking skills and methodologies

I've packed into this course the real training you need to work as a genuine developer - things that bootcamps and mentoring services don't teach you.

If you can't properly build small things, you can never build big things well
Many companies mention it in job postings and interviews, and many educational contents talk about 'handling large-scale traffic'. Is handling large-scale traffic really that important?
In reality, cases where large-scale traffic occurs in actual work are limited to a few service areas or specific situations, except for very large services.

So why do so many companies and content mention handling large-scale traffic like this?
The truth is, when software is trying to grow, they want to know if you have the technical thinking ability to solve appropriate problems for that situation!

People who can efficiently build small systems well will shine when those small systems grow or when building large systems
In this course, I've prepared time for you to think about small systems through the limited situations of relatively small commerce

Beyond being a developer who codes well
Becoming a developer who works well
What does it mean to work well? When developing, complex realities and uncertainties always follow.
If you start developing without knowing why this feature is needed or what problem it's trying to solve, the results easily go astray.

In practical development, there is no perfect answer that covers all cases completely. That's why what's important is the ability to read the context and make trade-off decisions that are optimal for that situation.