I struggled to merge code until I learned the pull request workflow: 1. Merge Request
↳ Write code on a separate git branch to isolate changes.
↳ Get instant review and suggestions using the CodeRabbit VSCode extension.
↳ Commit code with a clear commit message and push it to the remote repository.
↳ Open a pull request from the current branch into the target branch.

I struggled with git until I learned these 17 commands: 1 git add
↳ It lets you add changes from the working directory into the staging area

2 git commit
↳ It lets you save a snapshot of currently staged changes in the local repository, with a message

If you want to become good at system design, then learn these case studies: 1 How PayPal Was Able to Support 1 Billion Transactions a Day With Only 8 Virtual Machines

newsletter.systemdesign.one/p/actor-model

How to become good at system design (in 4 weeks).

Learn these case studies: 1 How PayPal Was Able to Support 1 Billion Transactions a Day With Only 8 Virtual Machines

newsletter.systemdesign.one/p/actor-model

How to become a world-class software engineer (in 6 months).

Read these 12 books:

How to master system design (in 1 month or less).

Learn these case studies: 1 How Google Ads Was Able to Support 4.77 Billion Users With a SQL Database

newsletter.systemdesign.one/p/cloud-spanne…

I struggled with system design until I learned these concepts (not joking): 1 How Idempotent API Works

newsletter.systemdesign.one/p/idempotent-a…

System Design Interview's Red Flag List.

If you’re making these 5 mistakes… we need to talk:

If you want to become good at system design (not kidding), learn these case studies: 1 How PayPal Was Able to Support 1 Billion Transactions a Day With Only 8 Virtual Machines

newsletter.systemdesign.one/p/actor-model

If you want to become a world-class software engineer (in 6 months), read these 12 books:

19 white papers you must read as a software engineer (all free):

1. MapReduce
2. TAO
3. Bitcoin
4. Google File System
5. BigTable
6. CAP Theorem
7. Kafka 8. Chubby
9. Log Structured Merge Tree
10. Google Spanner
11. Consistent Hashing
12. Out of the Tar Pit
13. The Part-Time Parliament
14. Raft

How the browser changes video quality automatically while streaming.

I spent hours studying about it, so you don't have to.

Here's what I learned (without the fluff): A popular video streaming protocol is HTTP Live Streaming (HLS)

Imagine HLS as a standard for adaptive bitrate video streaming

It allows the client to change video quality based on network conditions

9 useful GitHub repositories every software engineer should bookmark (you'll thank me later): 1 System design

github.com/systemdesign42…

Give me 2 minutes, and I'll teach you how databases keep passwords securely (not kidding): • The server transforms the password using a hash function to create the fingerprint.

• The database stores only the fingerprint, and not the password.

• The hash function is one-way, so the password cannot be obtained from a fingerprint.

6 books I wish I read at 22 as a junior engineer (I'm not kidding): 1. The Simple Path to Wealth

I didn't know what to do with money in my early 20s.

So I put everything in the savings account and lost on inflation and opportunity costs.

I learned the hard way it doesn't matter how much I earn if I'm financially uneducated.

This book taught me everything I wish my school had taught me.

If you want to become a world-class software engineer (I'm not kidding), read these 8 books:

What else should make this list?

1. The Pragmatic Programmer

It'll teach you the core software development process. 2. Designing Data-Intensive Applications

It'll teach you distributed systems.

If you want to become good at system design (I'm not kidding), learn these case studies: 1/ How Uber Computes ETA:

newsletter.systemdesign.one/p/uber-eta

System Design 101

How to scale a website to 1 million users:

// 🧵 • Prelaunch:

↳ Use a static web framework to save costs

• 10 Users:

↳ Use a single virtual machine to run the entire website for simplicity

• 100 Users:

↳ Use separate virtual machines to run the backend and database to prepare for scale

If you want to get started with system design, learn these concepts: 1/ Redis Use Cases:

↳ newsletter.systemdesign.one/p/redis-use-ca…

If you want to become good at system design (in 1 month), then learn these case studies: 1. How YouTube Was Able to Support 2.49 Billion Users With MySQL:

↳ newsletter.systemdesign.one/p/vitess-mysql

5 harsh truths I wish I knew at 22 as a junior software engineer: 1. Most work is debugging code and attending meetings:

I built a fancy Android app for my university project.

It was fun because I built it from scratch by myself.

But I had to deal with a project having a million lines of code at work.

Also 1,000+ engineers worked on the same codebase.

So I spent a ton of time debugging people's code and attending meetings.