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 #2

tl;dr: So, you want to learn how to code? Here’s What You Need To Know to get started. This is basically a list of Joe Karlsson’s favorite programming books, talks, podcasts, newsletters, websites, and general tips for learning more about programming.

tl;dr: “SingleStore holds the designation of being the world’s fastest unified database for data-intensive applications. As per the company’s management, the true north star of the company is to deal with all kinds of data without workload segmentation.”

tl;dr: We’ve all been in meetings discussing a challenge with one vocal engineer, who is opinionated and likes to share ideas. It’s wrong to assume that, because no one objects, a consensus has been reached or that one engineer’s decisions are correct. “In some cultures, people won’t speak up unless someone passes them the ball and mentions their names explicitly.”

tl;dr: “Denigma explains code in conversational English. Powered by machine learning.”

tl;dr: Managers fear under utilizing resources so they orchestrate processes to put all engineers to work, simultaneously. In practice, this creates issues as projects invariably don’t go to plan and resources cannot be reallocated easily. Jacob recommends a slacklog - “a backlog of things which can happen, but don’t need to happen.” These are ideas generated by the eng team, easily transferable between members, which can be added to the process to create resource flexibility.

tl;dr: “Step-by-step we’re going to break down a high-level task of creating the self-parking car to the straightforward low-level optimization problem of finding the optimal combination of 180 bits (finding the optimal car genome).”

tl;dr: A great analysis of the current state of the ecosystem. It is a collection of opinions from a pragmatic builder’s perspective. It is focused away from economics and the financial mechanisms of the chains themselves.