tl;dr:"Terminology matters and we can do better than 10x. We can be specific. Skills are not homogeneous, and people can quickly improve their craft as long as we don’t treat talent like some mythical quality."
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:Adam discusses the difference between line and staff software engineers, where a line engineer is core to the mission and staff is a supporting role. Although roles can be similar in either context, this variable is important to consider as it will directly impact your experience. Adam outlines how, as well as pros and cons of both.
tl;dr:"Tim is a very senior technical lead, and he’s good at his job. The problem put to him is: how do we make sure this doesn’t happen again?" Adam describes the problem - from a technical and organizational perspective - as well as what leads Tim to the common solution that doesn't actually solve the problem.
tl;dr:Adam tells the tale of two developers - one who lacks self-confidence, the other overly confident. "Confidence hides two different concepts behind a single word" - (1) Confidence in yourself. (2) Confidence in an outcome. You want to be "confident in yourself - but appropriately uncertain about the world." He suggests avoiding the phrase "I don't know," implying a lack of self-confidence and saying "let me look into that."
tl;dr:(1) Broot is a "better version" of tree (2) Funky “takes shell functions to the next level by making them easier to define, more flexible, and more interactive.” (3) FZF is a command-line fuzzy finder, and more.