From the TL;DR in Tech archive, originally sent on Substack. Some links may have died since.

tl;dr in tech by Joe Karlsson - Issue #55

beige wooden hand sculpture with orange background

Photo by charlesdeluvio on Unsplash

tl;dr: “Yet as companies far and wide try to use technology to solve the world’s ills, they grapple with an inviolable truth: there always will be more problems than engineers… that has consequences,” which Matt discusses here.

tl;dr: “My thesis is that the tooling and developer experience for programming languages is improving over time, but mainly in new languages. It goes like this: Tooling innovation happens, new languages adopt and standardize on it, and end up incrementally better than existing languages. If you add up enough of these increments, the older languages, which may have pioneered some of these innovations, seem painful and antiquated.”

tl;dr: “Visa, Mastercard, and American Express act as card networks for clearing and settling funds. The card acquiring bank and the card issuing bank can be - and often are - different. If banks were to settle transactions one by one without an intermediary, each bank would have to settle the transactions with all the other banks. This is quite inefficient.”

tl;dr: In this article, “remote development environments” refer to AWS EC2 instances where engineers make code changes and can see a running Slack application with those changes.

tl;dr: Algorithm Visualizer is an interactive online platform that visualizes algorithms from code.

tl;dr: GPU architectures are critical to machine learning, and seem to be becoming even more important every day. However you can be an expert in machine learning without ever touching GPU code. It is a bit weird to be work always through abstraction.