tl;dr in tech - Issue #101

Joins 13 Ways#

By: Justin Jaffray

tl;dr: Justin dives deep into “relational inner joins.” If SQL joins are your bread and butter, then this is the Nutella spread! From “they’re not without redundancy” to different perspectives, this article offers a comprehensive look you don’t want to miss.

Readability: Google’s Temple To Engineering Excellence#

By: Brian Kihoon Lee

tl;dr: Readability is the yin to your engineering yang, folks! Brian sheds light on Google’s approach to readability, but also proposes a ‘Readability Lite’ for the rest of us mortals. Useful for anyone tired of squinting at indecipherable code.

Data Management at Scale#

By: Piethein Strengholt

tl;dr: Decentralized data management? Yes, please! Piethein tackles the concept of Data Mesh, explaining how to manage data at scale in a decentralized manner. For data aficionados who love organizing as much as crunching.

Names Should Be As Short As Possible While Still Being Clear#

By: Ben Hoyt

tl;dr: “Some developers do use names that are too short.” Naming variables? You’ll find this piece by Ben enlightening. He talks about striking the right balance between conciseness and clarity. isThisNameTooLongOrIsItJustVerboseEnough might wanna read this.

Generating Code Without Generating Technical Debt?#

By: Reka Horvath

tl;dr: Reka breaks down how GPT and other language models can help speed up prototyping but also create messier code. For software engineers dealing with the never-ending battle against technical debt, this one’s for you.

Build Times And Developer Productivity#

By: Abi Noda

tl;dr: Speed is king, especially in build times. Abi talks about how even small improvements can yield big productivity gains. So the next time you’re daydreaming while your code compiles, remember, speed matters.

Gelling Your Engineering Leadership Team#

By: Will Larson

tl;dr: For all the engineering leaders out there, Will shares his playbook on creating a well-gelled leadership team. He covers everything from diagnosing conflict to setting expectations, a must-read if you’re playing 4D chess with team dynamics.

Embracing Failure#

By: Mike Fisher

tl;dr: “Frame failures like a video game.” Mike’s unique perspective on failure offers a mental model shift. Good for engineers who sometimes (or often, no judgment here) fail and want to turn it into a learning curve.

Finding A Buddy When You’re A Team Of One#

By: Lara Hogan

tl;dr: Lone wolf devs, this one’s for you. Lara outlines ways to mitigate isolation. Peer groups, cross-team collabs, and mentorship programs are among her arsenal for fighting off the lonely blues.

Right-Sizing Your Technology Team#

No Author

tl;dr: Team size questions keeping you up? This article tackles the essentials: Do we have enough devs? Are we overpaying? Is our software delivering? Good stuff for anyone puzzled about how to size a tech team effectively.