I struggled with GIT until I learned these 19 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 (in 2026), learn these 18 case studies: 1. How Stock Exchange Works:

newsletter.systemdesign.one/p/stock-exchan…

If you want to get started with system design (in 2026), learn these 16 concepts... 1 Distributed Systems – A Deep Dive

newsletter.systemdesign.one/p/distributed-…

If you want to become good at system design (in 3 weeks), learn these 15 case studies: 1. How Stock Exchange Works:

newsletter.systemdesign.one/p/stock-exchan…

I stopped wasting time testing AI tools that didn’t fit, so I built my own in minutes on OnSpace.

An AI Cars Tuning Studio.

Whatever ultra-specific function you want, you can create it exactly the way you imagine.
Instead of wasting hours searching, testing, and getting paywalled, you can create the exact tool you want on OnSpace.

(Tailored to your needs and problem.)

How Amazon S3 works (explained in 2 mins or less)... 🧵 • S3 is an object store to save unstructured data like log files

• They use a microservices architecture to build S3

• They store metadata and file content separately for scale

Pull Request vs Trunk Based Development vs Stacked Diffs

(explained in 2 mins or less): Stacked diffs split big code changes into smaller diffs.
And each diff builds on the one before it.

This approach:
• Simplifies reviews,
• Allow quick reverts,
• Reduces context switching,
• Maximizes the engineer's productivity.

If you want to pass system design interviews, learn this framework: 1 Requirements

✓ Functional and non-functional requirements

✓ Daily active users

✓ Read-to-write ratio

✓ Usage and traffic patterns

10 GitHub repositories that will make you a 10x software engineer: 1 Vision agent
github.com/GetStream/Visi…

15 heuristics to ace system design interviews: 1 Latency + Global → CDN
↳ Deliver data from edge servers to lessen latency

2 Read + Bottleneck → Cache
↳ Store frequently accessed data in cache to reduce database load

If you want to become good at system design (in 30 days or less), 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

I struggled with git until I learned these 19 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 I had to scale a database, here are 6 techniques I'd consider (not joking): This is a simplified guide for scaling databases.

The right solution depends on your traffic patterns.

Don't forget, everything is a trade-off.

What else would you add?

How SQL JOINs work

(explained in 2 mins or less): 1 Inner join
↳ It returns rows with matching values in both tables

2 Full outer join
↳ It returns all rows when there is a match in either the left or the right table

If you want to become good at system design (in 1 month or less), learn these case studies: 1 How Amazon S3 Achieves 99.999999999% Durability:

newsletter.systemdesign.one/p/amazon-s3-du…

10 whitepapers that will make you a 10x software engineer: 1 Google File System
↳ It’ll teach you how to build fault-tolerant, scalable distributed storage.

2 MapReduce
↳ It’ll help you learn to process big data with simple abstractions.

If you want to become good at system design (in 1 month), 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 books:

If you're just getting started with system design, learn these concepts: 1️⃣ Core Architecture

• Monolith
↳ An all-in-one application structure that is run as a single service.

• Modular Monolith
↳ An app structured as independent, loosely coupled modules that can be deployed together.

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