With the infinite amount of tutorials and infrastructure services out there nowadays, writing code really isn't hard - Just getting things to work is much easier than ever before. This means that if you want to stand out as a software engineer, *you need to write much **better** code than almost everybody else.*
Every engineer needs high code quality, especially at Big Tech companies like FAANG where even the slightest mistake can hurt hundreds of thousands of users and cost millions of $$. After going through this course, you will:
- 🔎 Understand what good code looks like (and doesn’t look like)
- 🌱 Set up the right growth mentality around code quality
- 💻 Learn how to submit a quality pull request
- 🍝 Avoid common messy code patterns
Now you might be looking at this and thinking, *"I need to move fast, I don't have time to write the perfect code"*. This is a very understandable misconception many engineers have before getting to the highest-levels, but it couldn't be further from the truth: *When you write better code, you will actually move **faster** as a software engineer*. Don't believe us? - Take the course and find out why!
Overview
Syllabus
- Overview
- How This Course Works
- Code Quality = Engineer Quality
- The Myth About Better Code
- Having The Proper Mentality
- What ACTUALLY Makes Code Good
- Fake "Clean Code" Shortcuts
- Embrace The Pain
- Code Quality Isn't Static
- Case Study: Instagram vs. Robinhood
- Better Code Strategies
- Focus, Focus, Focus
- Sweat The Details, Call Out Edge Cases
- Case Study: Signup Form Edge Cases
- Break It Down
- Lay Out The Plan
- How To Handle Migrations
- Make It A Little Better Each Time
- Pull Requests
- One Diff, One Thesis
- Share The Context
- Have A Test Plan
- Code Review Feedback
- Common Messy Code Patterns
- Code Comment Caches
- Non-Descriptive Names
- Too Many Comments
- Everything In 1 Place
- Infinite Layers Of Nesting
- Seas Of Newlines
- Wrapping Up
- Grow Even Faster: Side Projects & Open-Source
- Continue The Learning Journey
Taught by
Alex Chiou