You asked for longer rants, so here are longer rants! After almost 10 years I'm back to blogging. Thanks for the encouragement.
Link below in the thread 🔻
It's amazing (in a depressing way) how many unit tests are still just testing that a mock returns the exact thing you set it up to return . Please stop.
If today you find yourself typing 'as a father of daughters' or 'now that I have daughters' stop right there. Instead spend the time actively listening. The stories of inequality and abuse are everywhere.
It is in the interests of big AI CEOs and investors to spout fabulous assertions like this. This serves 3 purposes: hyping the tech they're selling, distracting from immediate questions about accountability by shifting to a philosophical discussion, implying we need to accept it.
Our System Design 101 GitHub repo has just reached 18,000 stars in 4 days. It's probably one of the fastest-growing repos in history.
Thanks to everyone who has starred, forked, or contributed to the repository!
What's included in the GitHub repository:
- 100 byte-sized system concepts with visuals.
- Real-world case studies.
- Tips on how to prepare for system design interviews.
Topics included (and many many more):
- SOAP vs. REST vs. GraphQL vs. RPC
- HTTP 1.0 -> HTTP 1.1 -> HTTP 2.0 -> HTTP 3.0 (QUIC)
- CI/CD Pipeline Explained in Simple Terms
- 8 Data Structures That Power Your Databases
- Top caching strategies
- What does a typical microservice architecture look like?
If you like our content, consider starring the repo: https://t.co/wB7lUh2Gol
Writing more efficient code / designing efficient systems is a great way to improve the sustainability of software, I suspect there's a much bigger gain to be had in not building features that nobody needs / uses or are a vanity project of someone with a fancy job title...
"If we reduce the number of employees for better short-term financial results, employee morale will decrease, I sincerely doubt employees who fear that they may be laid off will be able to develop software titles that could impress people"
- Satoru Iwata
https://t.co/hYHxim9wQM
That is if you want high speed, you must build high quality systems. If you want high quality systems, you must build them quickly as a series of small changes.
This is what the data says, and when you stop and think about this, the reasons are pretty clear.
11/17
Unpicking the idea of “Rockstar developers” and comparing them to how effective, high-performing, teams work 🆚
Watch the FULL video HERE ➡️ https://t.co/xj4FTxmKHS