Bryan Agam

Barangkali hidup adalah doa yang panjang dan sunyi adalah minuman keras

System Design Talks 24 - Real Time Communication [FAANG(Uber) SDE2 Interview] Problem? THOUSANDS of drivers are sending their GPS coordinates every second & THOUSANDS of riders need to see that car move smoothly on their map. Do you use polling or WebSockets?

@sanskarpan You can find it here, it's in early access. The final chapter will be available soon bytesizego.com/books/anatomy-…

Go is simple, so I ended up writing an 865-page book about how it works internally, just to see how it maintains that simplicity 😇

𝗦𝗦𝗢 (𝗦𝗶𝗻𝗴𝗹𝗲 𝗦𝗶𝗴𝗻-𝗢𝗻) 𝗲𝘅𝗽𝗹𝗮𝗶𝗻𝗲𝗱 SSO is an authentication process that allows users to access multiple apps with a single master key. This is accomplished using a central authentication server that stores the user's credentials and verifies them for each application. Here are 𝘁𝗵𝗲 𝘀𝘁𝗲𝗽𝘀 that happen if you want to access the Trello web app by using your Google account: 1. Use the Trello login web page and select Google account as a login method 2. Trello redirects the user to the Google login page 3. User is served with the Google login page 4. The user enters their Google credentials 5. Google sends authentication info to the SSO Authorization server 6. If credentials are valid, the Authorization server returns the auth token (SAML) 7. Google sends the auth token to the Trello 8. In the last step, Trello sends the token to the Google Authentication server to validate its 9. If the token is valid, Trello will allow access to the user and store the session for future interactions ✅ The 𝗯𝗲𝗻𝗲𝗳𝗶𝘁𝘀 of SSO are: 🔹 Improved user experience. Users do not need to remember multiple usernames and passwords. 🔹 Increased security. Users are less likely to reuse passwords across applications. ❌ The 𝗱𝗶𝘀𝗮𝗱𝘃𝗮𝗻𝘁𝗮𝗴𝗲𝘀 are: 🔸 Single point of failure. One of the most notable disadvantages is that SSO creates a single point of failure. If the SSO system is compromised, the attacker could access all connected applications and services. 🔸Security risks. If credentials are compromised, the security of all connected applications could be at risk. Some 𝗰𝗼𝗺𝗺𝗼𝗻 𝘁𝘆𝗽𝗲𝘀 𝗼𝗳 𝗦𝗦𝗢 are: 🔹 𝗦𝗔𝗠𝗟-𝗯𝗮𝘀𝗲𝗱 𝗦𝗦𝗢. This is the most common type of SSO. It uses the SAML protocol to exchange authentication information between the SSO server and applications. 🔹 𝗢𝗽𝗲𝗻𝗜𝗗 𝗖𝗼𝗻𝗻𝗲𝗰𝘁. This is a newer SSO type based on OAuth 2.0. It is a more straightforward protocol than SAML and is easier to integrate with web applications. And 𝗽𝗼𝗽𝘂𝗹𝗮𝗿 𝗦𝗦𝗢 𝘀𝗼𝗹𝘂𝘁𝗶𝗼𝗻𝘀 are: ➡️ Azure Active Directory ➡️ Okta ➡️ Ping Identity ➡️ OneLogin ➡️ Google Cloud Identity Platform

Computer Architecture from Scratch

If you want to learn System Design Fundamentals, Go for this playlist (100 videos):

Want to be a great backend engineer? Please learn: 1. Programming Fundamentals Language depth, Data structures, Algorithms, Concurrency, Memory basics 2. APIs and Contracts REST, gRPC basics, Versioning, Idempotency, Pagination, Error handling 3. Databases SQL, Joins, Indexes, Transactions, Query optimization, Schema design 4. Caching Redis, Cache invalidation, TTLs, Read-through vs write-through, Hot key problems 5. Async and Messaging Queues, Kafka/RabbitMQ, Retries, DLQs, At-least-once delivery, Idempotent consumers 6. Distributed Systems Basics Replication, Partitioning, Consistency, Leader-follower, Network failures, Backpressure 7. Reliability Engineering Timeouts, Retries, Circuit breakers, Rate limiting, Graceful degradation 8. Observability Logs, Metrics, Tracing, p95/p99 latency, Debugging production issues 9. Infrastructure and Deployment Docker, CI/CD, Linux basics, Cloud services, Rollbacks, Blue-green/canary deploys 10. Security Auth, Authorization, Secrets management, Input validation, Encryption, Secure defaults Bonus: 11. Engineering Judgment Know when not to overengineer, choose boring tech when it wins, optimize for systems your team can actually operate

Honestly, beginners don’t need 100 services. Start with just these: → EC2 (compute) → S3 (storage) → IAM (permissions) → VPC (networking) → RDS (database) → Lambda (serverless) → CloudWatch (monitoring) Master these → you can understand 80% of AWS.

Gue pake Claude Pro dan sering banget kena limit, jadi flow kerjaan macet. Buat yang memiliki pengalaman sama, baca deh artikel ini terus cobain. Pasca nyobain ini, gue lebih jarang kena limit dibanding sebelumnya. Thank me later!

I repeat, kalo mau punya gaji tinggi, dan diri kita yg dicari perusahaan. Harus mau ngelakuin hal kayak gini! 🫵 • Belajar hal yang market value-nya tinggi, bukan cuma yang nyaman dipelajari • Invest waktu & uang buat skill (kayak ambil sertifikasi AWS ini) • Konsisten walaupun ga ada yang liat prosesnya • Ngerti konsep, bukan sekadar hafal buat lulus ujian • Bisa translate ilmu jadi real-world impact (bukan sekadar teori) • Build credibility, biar trust itu datang sebelum interview • Main di level global, bukan cuma lokal market • Siap capek sekarang, biar nanti punya leverage lebih besar Karena pada akhirnya, perusahaan ga bayar kita karena "niat belajar", tapi karena value yang bisa kita deliver.

Anda anda, yang lulusan IT juga ikut ini juga yak? Jangan fikir yg anda pelajari di kampus indo ini sebanding sm kelas cs50 ini yak? Beda jauuuuuh!

Aku baru baca ini, Hasil survey dari Policy Research Center (Porec) Judulnya "Siapa yang diuntungkan dari Program Makan Bergizi Gratis (MBG)" Silahkan kita baca hasil penelitiannya, yang sebenernya hasilnya tidak mengagetkan namun melegitimasi dan mengkonfimasi asumsi kita.

University of Queensland bikin kursus persiapan IELTS yang bisa diakses gratis. 80+ jam materi interaktif, dibuat oleh orang-orang yang sama yang ngajar di salah satu pusat testing IELTS resmi. Bukan tips YouTube random, tapi kurikulum yang beneran dirancang untuk bantu kamu naik skor.

harusnya tinggal bilang aja : China ngasih kami 2 kemudahan: 1. Harga lebih murah. 2. Bisa ngutang nah, 2 hal ini gak ada dari penawaran kalian. Kami tahu, harga kalian lebih mahal meski kualitas lebih bagus. Tapi kan kami carinya yg lebih terjangkau. Udah gitu bisa ngutang. Maaf yah Shinyuu (親友) mas Jepang 😂

kenapa ada orang yang gampang emosi kalau ngobrol sama orang tuanya? padahal lagi gak dimarahin lagi gak ada masalah besar juga tapi bawaannya udah sesek duluan pengen cepet kelar gan pindah dari tempat secara psikologis, ini hal yang cukup umum, ayo kita bahas:

Abis ngisi kelas “Cara Baca Data Ekonomi” malah nemu paper hidden gem. Jadi salah satu paper favoritku di 2026 Isi papernya sejauh mana AI bisa dipake buat riset ekonom (ngumpulin data, membersihkan dan memproses data, analisis ekonometrika, sampe buat visualisasi) dengan bandingin semua sistem produk2 AI

kenapa coba raditya dika berani pasang tarif segede itu? karena audiencenya beda dengan yang lain. audience gede di niche edukasi atau longform content hampir pasti earning powernya lebih tinggi. dan dengan tarif segitu pun gw yakin dia tetep selektif milih client.

@_mento Betul sekali, TrueNAS, hardwarenya: - Lenovo ThinkCentre M720q Tiny PC buat servernya - TERRAMASTER D4-320 4-Bay External Hard Drive Enclosure (buat storagenya, konek via USB-C 3.2 Gen 2) - Seagate IronWolf 4 TB (x3)

Merdeka dari Google Photos sudah. Selanjutnya merdeka dari Google Drive 🙌🙌🙌🙌🙌🙌

I remember a junior engineer I worked with who genuinely thought he was a bad software engineer. Not average. But Actually bad. Why? Because every ticket took him too long. He could not debug production issues fast. He got confused in code reviews. And whenever senior engineers spoke about caching, queues, indexing, retries, race conditions, he would just go silent. So naturally he made the worst conclusion possible: "Maybe I am just not smart enough for backend work." But that was not the real problem. The real problem was much simpler. He was missing a few boring prerequisite skills that nobody had properly taught him: 1. How HTTP actually works 2. How databases really read and write data 3. How logs are used to trace a bug 4. How to read an unfamiliar codebase without panicking 5. How to break a big problem into smaller checks 6. How async code fails in real systems That is it. Not talent or IQ. Just missing foundations. So instead of telling him to "work harder" or "be more confident", we fixed the inputs. For a few months he did very basic things: - wrote simple SQL queries by hand - debugged small bugs slowly and documented the path - learned API flow end to end - traced requests from load balancer to service to database - read old incident reports - picked one concept every week and went deep on it Nothing fancy. No 10x engineer nonsense. No fake motivation. Simply repetition on the right prerequisites. And things changed! The same guy who used to freeze during debugging started finding issues before others. The same guy who thought he was "bad at coding" started writing cleaner code reviews. He used to get stuck on every production issue and now became the person people tagged for backend bugs. A year later, new joiners thought he was naturally talented. He was not. He was finally practiced. This is something a lot of people in software do not understand: A weak foundation feels like low intelligence. A strong foundation feels like talent. Many people are failing because they are trying to do senior-level work without junior-level repetitions. And the opposite is also true. Some people think they are geniuses when really they just got early exposure: better college better peers better internship better manager better starting point That lead disappears very fast if they stop practicing. Software engineering is like that. Prerequisite knowledge is intellectual capital. It can take a person from: "Maybe I am not cut out for this" to "I can probably build this" And it can also take someone from: "I am the smartest guy here" to "why is everyone catching up to me so fast?" Do not judge yourself too early. Sometimes you do not need more confidence. You need more reps on the fundamentals.