tl;dr in tech - Issue #69

Ahoy, mateys! Avast ye and hoist the mainsail, because we’re setting course for uncharted digital waters. Here are three tips to help you build a site that’ll shiver the timbers of even the toughest recruiters:

1. Keep it simple: No need to hoard all the gold and silver doubloons in your portfolio. Keep things streamlined and easy to navigate, just like the sleek lines of a well-crafted vessel.
2. Highlight your strengths: Just like a captain boasting of their voyages, make sure to showcase your most impressive projects and accomplishments. It’ll make you stand out in a sea of bland resumes and profiles.
3. Show off your personality: Aye, there be no need to be a dry landlubber! Let your unique voice and character shine through on your site, whether it be through witty quips or clever design.

So, polish your eyepatches and hoist your colors high, because with these tips, you’ll be well on your way to a top-notch portfolio website!

HTTP/3 Prioritization Demystified
- Robin Marx
tl;dr: “What exactly does prioritization mean? How does it work under the hood? Why is it important to have some control over it? and, crucially, do all browsers agree on which resources are most important?”

Overcoming The Resistance
- Paulo André

tl;dr: Paolo discusses hesitating due to one’s imposter syndrome: “How can we create the conditions to just start? How can we feel the fear… and do it anyway?”

1. Create a process… and then trust in it.
2. Use the Procrastination Pomodoro.
3. 80% is good enough.
4. Feed your own feedback loop.
5. Don’t seek to make the right decision. Make the decision right.

What If Writing Tests Was A Joyful Experience?
- James Somers
tl;dr: “At Jane Street we use a pattern / library called “expect tests” that makes test-writing feel like a REPL session, or like exploratory programming in a Jupyter notebook - with feedback cycles so fast and joyful that it feels almost tactile. Having used them for some time now this is the only way I’d ever want to write tests.”

McDonald’s Event-Driven Architecture: The Data Journey And How It Works
- Vamshi Krishna Komuravalli, Damian Sullivan

tl;dr: Here is a typical data flow of how events are reliably produced and consumed from the platform:

1. Initially, an event schema is defined and registered in the schema registry.
2. Applications that need to produce events leverage producer SDK to publish events.
3. When an application starts up, an event schema is cached in the producing application for high performance. The authors continue to discuss how data flows through the system.

Architecture Diagrams Should Be Code
- Brian McKenna

tl;dr: “Architecture code can be versioned with the code which implements it. We can write algorithms to check our architecture. I’d like to see more tools available to describe architecture as part of code, allowing us to generate as many diagrams as we want, for accurate and easy communication.”

Data Engineering Zoomcamp
Free Data Engineering course. 

What Happens When A CPU Starts

tl;dr: “Generally, when a CPU chip first receives power, it must be reset by receiving a pulse on its RESET (or RST) pin. This is because when the power supply is first powering up, even if it only takes a second or two, the CPU has already received “dirty” power, because the power supply was building up a steady stream of electricity.”

The Ugliest Pattern In React
- Sebastian Carlos
tl;dr: “Maybe the ugliness is a virtue, since it encourages us to completely change the code to enable some of the better alternatives mentioned above - After all, “adjusting state in response to rendering” will always result in code that’s difficult to understand.”