Neo Kim's Linkedin Analytics

If you want to reduce latency, learn these 12 rules: What would you add to the list? —— 👋 PS - If you enjoyed this post, you'll love my free newsletter on system design. Join 140,000+ engineers and get the powerful system design template: → https://lnkd.in/eWAp5ZwE ——— ♻ Repost to help others learn system design. ➕ Follow Neo Kim for more.

I struggled with system design until I learned these concepts: 1 Redis Use Cases ↳ https://lnkd.in/ekJMjMG3 2 Idempotent API ↳ https://lnkd.in/erMkqwq4 3 Saga Design Pattern ↳ https://lnkd.in/eFXC4-aJ 4 Protocol Buffers vs JSON ↳ https://lnkd.in/egcFxe2t 5 How JWT Works ↳ https://lnkd.in/ek9_BTUc 6 How Consistent Hashing Works ↳ https://lnkd.in/eUP9DbCg 7 Service Discovery ↳ https://lnkd.in/eCYYwQfU 8 Monolith vs Microservices Architecture ↳ https://lnkd.in/e3EBtg_v 9 What Happens When You Type a URL Into Your Browser ↳ https://lnkd.in/eusuDn5z 10 Microservices Lessons From Netflix ↳ https://lnkd.in/eZSM3CRB 11 How Websockets Work ↳ https://lnkd.in/euHDJUfH 12 Modular Monolith Architecture ↳ https://lnkd.in/edUqkCKR 13 Bloom Filters ↳ https://lnkd.in/e2duES7s 14 How Databases Keep Passwords Securely ↳ https://lnkd.in/edd8-N5k What else should make this list? —— 👋 PS - Get my system design playbook on newsletter signup (it's free): → https://lnkd.in/eWAp5ZwE ——— ♻ Repost to help others learn system design. 👤 Follow Neo Kim for more.

If you want to become good at system design (in 1 month), learn these case studies: 1 How YouTube Supports 2.49 Billion Users With MySQL ↳ https://lnkd.in/efmJw4Dx 2 How Google Ads Supports 4.77 Billion Users with SQL ↳ https://lnkd.in/efnSvwJp 3 Slack Messenger Architecture ↳ https://lnkd.in/eATMDjrK 4 How Meta Achieves 99.99999999% Cache Consistency ↳ https://lnkd.in/e88kUZAm 5 Bitly Shortener Architecture ↳ https://lnkd.in/evFTZVQq 6 Real Time Gaming Leaderboard Architecture ↳ https://lnkd.in/edfTDq5R 7 How to Scale an App to 10 Million Users on AWS ↳ https://lnkd.in/eU736g9Q 8 How Cloudflare Supports 55 Million Requests per Second With 15 Postgres Clusters ↳ https://lnkd.in/eEQP6Apw 9 Distributed Counter System Design ↳ https://lnkd.in/eGwaA62J 10 Pastebin Architecture ↳ https://lnkd.in/eZpfaVjc 11 How Stripe Prevents Double Payment Using Idempotent API ↳ https://lnkd.in/erMkqwq4 12 How Amazon S3 Achieves 99.999999999% Durability ↳ https://lnkd.in/eutGiK35 13 How Uber Finds Nearby Drivers at 1 Million Requests per Second ↳ https://lnkd.in/eeqH9Hjh 14 How PayPal Was Able to Support 1 Billion Transactions a Day With Only 8 Virtual Machines ↳https://lnkd.in/eqcb7MpP What else should make this list? —— 👋 PS - Join 150,000+ engineers and get my system design playbook for free: → https://lnkd.in/eWAp5ZwE ——— ♻ Repost to help other software engineers learn system design. 👤 Follow Neo Kim for more.

How nginx handles 1M connections on a single server (in just 8 sentences): What else should make this list? —— 👋 PS - I wrote a detailed article on nginx in my newsletter (with visuals): → https://lnkd.in/dJ_Z3vhs ——— ♻ Repost to help others learn system design. 👤 Follow Neo Kim for more.

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 3 git push ↳ It lets you upload commited changes from the local repository to a remote repository 4 git fetch ↳ It lets you download changes from a remote repository, without applying them locally 5 git merge ↳ It lets you combine changes from one branch into another 6 git pull ↳ It lets you fetch and then merge changes from a remote repository into the local branch 7 git diff ↳ It lets you see the changes not staged or commited yet 8 git diff HEAD ↳ It lets you see changes between the current working directory and the latest commit 9 git status ↳ It shows you the current state of the working directory and staging area 10 git branch ↳ It lets you see all local branches 11 git checkout ↳ It lets you create a branch or switch between branches 12 git log ↳ It shows you commits in the current branch with extra details 13 git stash ↳ It lets you temporarily save uncommited changes and apply them later 14 git rebase ↳ It lets you apply commits from one branch to another 15 git reset ↳ It lets you undo changes in the working directory and move back to a specific commit 16 git revert ↳ It lets you undo changes by creating a new commit 17 git cherry pick ↳ It lets you apply commits from one branch to another ——— - Working directory ↳ It's the directory where you make changes to the files - Staging area ↳ It lets you control which changes go into a commit - Local repository ↳ It's the version of a project stored on the local machine of a user - Remote repository ↳ It's the version of a project stored on a server, such as GitHub What else should make this list? ——— 👋 PS - Get my system design playbook on newsletter signup (it's free): → https://lnkd.in/eWAp5ZwE ——— ♻ Repost to help other software engineers learn git. 👤 Follow Neo Kim for more.

Give me 2 mins—I'll teach you how Big O works: • Big O tells how much slower a code gets as the input increases. • There are best, average, and worst cases for a specific algorithm. • Also there are Big Os for time, memory, and storage efficiency. • Big O helps to understand which data structures or algorithms have better performance. • Big O shows the growth rate and not the actual speed. So it's important to test the input data. What else would you add? —— 👋 PS - If you enjoyed this post, you'll love my free newsletter on system design. Join 140,000+ engineers and get the powerful system design template: → https://lnkd.in/eWAp5ZwE ——— ♻ Repost to help others write good code. ➕ Follow Neo Kim for more.

How to write clean code. Learn these 6 rules: 1 Separation of Concerns (SOC) ↳ Break down a complex program into smaller units. ↳ Each unit should focus on a specific task. 2 Document Your Code (DYC) ↳ Write code for your future self and others. ↳ Explain complex code sections with comments and documentation. 3 Don't Repeat Yourself (DRY) ↳ Don't waste time writing the same code again. ↳ Instead use functions, modules, and existing libraries. 4 Keep It Simple, Stupid (KISS) ↳ Simple is hard, but better. ↳ Readable code > clever code. 5 Test Driven Development (TDD) ↳ Write a failing test first. ↳ Write code to make the test pass. ↳ Then clean up the code without changing behaviour. 6 You Ain't Gonna Need It (YAGNI) ↳ Build only essential features. ↳ Don't build features you think you might need later. The bottom line: ↳ Leave the codebase cleaner than you found it. What’s your golden rule for clean code? —— 👋 PS - Want my System Design Playbook for free? Join 150,000+ software engineers in my newsletter: ↳ https://lnkd.in/eWAp5ZwE ——— ♻ Repost to help others write clean code. 👤 Follow Neo Kim for more.