tl;dr in tech - Issue #76

Cynefin For Developers#

By: Liz Keogh

tl;dr: Liz Keogh introduces the Cynefin framework, which categorizes problems into 4 domains (obvious, complicated, complex, and chaotic) and a fifth domain, disorder, for unclear situations. Software engineers can use this framework to better understand and approach problem-solving.

ICER Image Compression Algorithm#

By: Unknown

tl;dr: This GitHub repository offers a C library implementation of NASA’s ICER image compression algorithm. ICER is a progressive, wavelet-based algorithm designed for data loss resistance, making it suitable for encoding images transmitted over unreliable channels like satellite radio communications. A valuable resource for software engineers working with image compression or communication systems.

Demand And ETR Forecasting At Airports#

By: Uber Engineering

tl;dr: Uber’s engineering team tackles the challenge of balancing supply and demand at airports by building new models for demand forecasting and effective queue length on the Michelangelo platform. They integrate these models with the Driver app to optimize resource allocation. A fascinating read for software engineers interested in demand prediction and resource management.

GitHub Copilot X: The AI-Powered Developer Experience#

By: Thomas Dohmke

tl;dr: Thomas Dohmke introduces the evolution of GitHub Copilot into an AI assistant with chat and voice capabilities. Copilot will also be integrated into pull requests, the command line, and docs to answer questions about your projects. A must-read for software engineers excited about AI-enhanced development experiences.

Building A Great Relationship With Your Boss#

By: Paulo André

tl;dr: Paulo says, “If I could pick one skill, and one skill only, this would be it,” emphasizing the importance of understanding your manager’s challenges and needs. So go ahead, learn to read your boss’s mind (or just ask them questions).

Uptime, Status Pages, And Transparency Calculus#

By: Lawrence Jones

tl;dr: Lawrence believes that transparent communication in past incidents is more valuable than just focusing on uptime. Let’s face it, incidents happen, so let’s be honest about them and work together for a brighter future. 🌤️

Cleaner Unit Tests With Custom Matchers#

By: Jamie King

tl;dr: Jamie reminds us that “using custom matchers in your tests can help make your assertions cleaner and less ambiguous.” Level up your unit testing game and make your code shine like a diamond. 💎

I’m Now A Full-Time Professional Open Source Maintainer#

By: Filippo Valsorda

tl;dr: Filippo shares his journey to becoming a full-time open source maintainer, earning an income competitive with senior software engineers. Although he’s not ready to recommend everyone follow suit, he hopes his story can inspire and inform others. 🚀

Reversing UK Mobile Rail Tickets#

By: Anonymous

tl;dr: Ever wondered what’s inside your mobile rail ticket’s barcode? This author delves into the data and discovers that it can reveal a surprising amount of detailed tracking info about your train travels. 🚂

Asynchronous Computing At Meta: Overview And Learnings#

By: Sayak Kundu, Artem Denisov

tl;dr: The Meta team has built a platform for serverless asynchronous computing that provides a wide range of capabilities, including load balancing, rate limiting, and quota management. Learn how they make async computing as easy as pie. 🥧

SQL Should Be Your Default Choice For Data Engineering Pipelines#

By: Robin Linacre

tl;dr: Robin argues that “SQL should be the first option considered for new data engineering work.” With its robustness, speed, and readability, SQL is the go-to choice for data pipelines, whether they’re big or small. 🗃️

That’s it for this week! Keep learning, stay curious, and don’t forget to have fun. See you next time! 🎈