panic()

@eatonphil 2nd edition? This is probably an opportunity for me to read this book again. Is the second edition good with more new stuff ?

I first tried to read this book in 2018 and couldn't make it through because I thought it was too hard. 8 years later it's the only book I recommend every developer reads, and I had the chance to review the 2nd edition. Join a study group, give it a read.

@Akintola_steve This is a very generic question. What kind of logs? Write ahead logs? Commit Logs? OpLog? Replication Logs? Or Logs as we know from observability perspective?.

Interviewer: Why is logging important?

all that is needed is the right set of mcp tools integrated to all the platforms (notion, GitHub, confluence, Jira e.t.c) your company uses and onboarding will be easy. There is no architectural diagram of the system? AI can generate one (simple or complex)

One of the things I so much love about AI coding tool is not how fast it can help me iterate on an idea or a task but how easy it helps to understand an unfamiliar system. The era of struggling to onboard on large and complex system will slowly fade away, 🧵

@chrisf_cpuarch I no longer write C but the knowledge of threading I learnt in C has been super useful conceptually.

Yes.

5 years in Germany already with a beautiful wife and daughter + a growing career.

Imagine if every dev falls in-love with their terminal and learns curl or any http client tool that integrates with their text editor, company’s like postman will not be making money out of things like this.

My book launched today: Technical Behavioral Interview: An Insider's Guide. A thread on why I wrote it. 🧵 geni.us/BehavioralInte…

Chapter 8 of The Anatomy of Go is ready for review. It goes into concurrency, the Go scheduler, threads, the system monitor thread, goroutine preemption, what happens at startup, how channels work, how the select statement works, and how timers work behind the scenes, a lot and a lot, with visual explanations. This is the final chapter, it is near the end of the journey.

@fmt_sprintf bytesizego.com/books/anatomy-…

I BUILT SOMETHING Not because it was easy. Not because it would make me a billionaire. But because I believe that we cannot build tools that shape humanity without EVERYONE in the room (70m+ to be exact) Technology should meet people where they are, not the other way round

@func25 Thanks

🚨 CRITICAL: Active supply chain attack on axios -- one of npm's most depended-on packages. The latest axios@1.14.1 now pulls in plain-crypto-js@4.2.1, a package that did not exist before today. This is a live compromise. This is textbook supply chain installer malware. axios has 100M+ weekly downloads. Every npm install pulling the latest version is potentially compromised right now. Socket AI analysis confirms this is malware. plain-crypto-js is an obfuscated dropper/loader that: • Deobfuscates embedded payloads and operational strings at runtime • Dynamically loads fs, os, and execSync to evade static analysis • Executes decoded shell commands • Stages and copies payload files into OS temp and Windows ProgramData directories • Deletes and renames artifacts post-execution to destroy forensic evidence If you use axios, pin your version immediately and audit your lockfiles. Do not upgrade.

almost 11 years ago i watched this talk on my lunch break. it ended up being one of the most influential videos i've ever watched. been workflow pilled ever since youtube.com/watch?v=xDuwrt…

After reading clean code pick up “A Philosophy of Software Design” it’s a perfect book that critic many things in clean code while giving better alternatives.

@_jaydeepkarale They are few issues here It uses SELECT * which might not be covering, the database may need additional row lookups after the index scan to fetch the full rows. Index order should be (user_id, status), not (status, user_id). If supported, a partial index on status = 'completed'

Since most queries look like this: SELECT * FROM orders WHERE user_id = 42 AND status = 'completed'; Your Lead suggested: "Let’s create an index on (status, user_id)." What’s your reply?

essential topics for backend engineers working with distributed systems - tcp/ip, udp socket programming - rest, grpc for service communication - kafka, rabbitmq for async messaging - concurrency in go/java (goroutines, executorservice) - thread safety and memory models - distributed databases (cassandra, mongodb) - sharding and partitioning strategies - caching patterns (redis, memcached) - consensus algorithms (raft, paxos) - distributed locks and coordination - service discovery and load balancing - circuit breakers and retry logic - distributed tracing (jaeger, zipkin) - monitoring with prometheus and grafana - oauth2, jwt for auth - ssl/tls and secure communication - rate limiting strategies - event-driven architecture (cqrs, event sourcing) - kubernetes for orchestration - cloud-native patterns - api versioning and backward compatibility start with the fundamentals, then build up to distributed patterns. most of these apply across languages and frameworks.

@orinayooye This sort of people are insufferable

I have a teammate that will always find a reason to leave a comment on a PR. Someone shared a PR to add a constants file to one of our services and he’s asking them why they’re using an array instead of loading and parsing a CSV. Omg 🤣🤣🤣

In tuning the performance of database queries a careful execution plan inspection yields more confidence than superficial benchmarks. —use the index Luke.