tl;dr in tech by Joe Karlsson - Issue #14
tl;dr: “Scientists keep logbooks for their findings. Why don’t computer scientists?” Conor shares an example of one and cites these benefits:
1) Enumerate where you are in the bug fixing journey.
2) Keeps you rooted when you have a stack of issues.
3) Makes your future steps clearer.
4) Documents the time and effort spent, helpful to show your team the energy you put in.
5) Documents your eventual success and how it happened.
tl;dr: “This post describes a very casual code review of a few cryptography functions used by MetaMask. It does not describe any vulnerabilities. If you’re the kind of person who likes a meandering and amateurish code review that goes absolutely nowhere, you’ll enjoy this post.”
tl;dr: Swiss Army knife for developers. An offline Windows app that helps developers in daily tasks.
tl;dr: Ankit shows us how to design such a system factoring in such scale: 1 Billion users on the application per month, 650,000 active users per second at peak, 40m messages per second at peak. “The entire application will comprise of several microservices each performing a specific task.”
tl;dr: The survival zone is when your energy is high, but negative at work. People in this zone are anxious, impatient, and self-critical. Tony shares 6 observations to avoid falling here:
1) Become a sprinter, not a marathoner.
2) Substitute self-observation for judgment.
3) When you feel bad, remember that’s not the whole story.
4) Create a safe space for yourself within yourself.
5) Take up something you enjoy doing just for its own sake.
6) Make someone else’s life better.
tl;dr: “I left Facebook (Meta) in 2021 to join a small startup called Replit. Leaving wasn’t easy, and during the process I’ve talked to half a dozen friends who were in the similar situation. I hope this post would be useful to senior engineers who are looking to leave.”
tl;dr: “Your salary negotiation - which routinely takes less than 5 minutes to conclude - has an outsized influence on what your compensation is… That makes your negotiation five very important minutes.”
tl;dr: “I guess I’m looking at this a bit like the last time I lost data due to a hard disk failure. I always knew there was a risk but until it actually happened, I didn’t take the necessary steps to protect against that risk doing actual damage. But hey, it could have been so much worse; that number could have been 10x higher and I wouldn’t have known any earlier.” Troy dives into the 17.3GB data spikes that caused his Azure bill to rocket.