|
Tuesday 12th March’s issue is presented by Datadog |
 |
Full-Stack Observability & Security Built For Scale
See inside any stack, any app, at any scale, anywhere with Datadog’s intuitive, real-time observability and security platform.
Enable end-to-end visibility into cloud applications with effortless deployment, minimal maintenance, and an unparalleled breadth of coverage. |
|
|
How To Give Actionable Feedback On Work Output — Wes Kao
tl;dr: “Super Specific Feedback is extremely concrete feedback primarily on work output. The goal is to strengthen the work product to get it closer to ship ready, and to help the feedback recipient improve their craft and judgment over time.” Wes provides 16 ways to give actionable feedback, starting with: (1) Get “permission” and sell why getting lots of feedback benefits them. (2) Explain the “why.” (3) Avoid the shit sandwich i.e. be intellectually honest and direct, and support it with evidence. (4) Share positive feedback so they know what to continue doing. (5) Aim to be tactical, actionable, concrete, and specific.
Leadership Management |
 |
|
What If We Rotate Pairs Every Day? — Kieran Murphy, Gabriel Robaina
tl;dr: “We developed a lightweight methodology to help teams reflect on the benefits and challenges of pairing and how to solve them. Initial fears were overcome and teams discovered the benefits of frequently rotating pairs. We learned that pair swapping frequently greatly enhances the benefits of pairing. Here we share the methodology we developed, our observations, and some common fears and insight shared by the participating team members.”
Management PairProgramming |
|
|
The DevSecOps Maturity Model
tl;dr: A blueprint for assessing and advancing your organization’s DevSecOps practices to detect vulnerabilities and deliver digital services with more confidence.
Promoted by Datadog Management DevOps |
|
|
How To Find Great Senior Engineers — Ken Kantzer
tl;dr: Ken finds it hard to gauge experience when hiring and has developed 3 strategies to help: (1) Case Studies: Prepare a 1-2 page story that lays out, a particular technical scenario in deliberately broad brushstrokes, and then ask the candidate to figure out what they’d do. (2) Three Why’s Technique: Practice of asking someone to describe something, and then pressing them three more times for more details. (3) Ask them to Break the Rules: A more specific instantiation of a famous interview question “What important truth do very few people agree with you on?”
Hiring Management |
|
|
|
“Learn the rules like a pro, so you can break them like an artist.”
― Pablo Picasso
|
|
|
How HEAD Works In Git — Julia Evans
tl;dr: Julia ran a poll asking people how confident they were that they understood how HEAD works in Git. The results were a little surprising... people were unconfident about their understanding. “Usually when people say that a topic is confusing when I think it’s not, the reason is that there’s actually some hidden complexity that I wasn’t considering. And after some follow up conversations, it turned out that HEAD actually was a bit more complicated than I’d appreciated!”
Git |
|
|
The Self-Rendering Eval Shirt
tl;dr: The free t-shirts companies give away to developers are everywhere and, with a few exceptions, most are pretty boring: usually just a logo on a t-shirt. In this post, see how StackBlitz’s co-founder broke this mold with a t-shirt design that incorporated the StackBlitz logo constructed with *actually valid* JavaScript code that is the source code of the image itself.
Promoted by StackBlitz JavaScript Entertaining |
|
|
Modern Git Commands And Features You Should Be Using — Martin Heinz
tl;dr: “Most people only ever touch the most basic of commands, such as add, commit, push or pull, like it's still 2005. Git however, introduced many features since then, and using them can make your life so much easier, so let's explore some of the recently added, modern git commands, that you should know about.” Martin presents Switch, Restore, Sparse Checkout, Worktree and Bisect.
Git |
|
|
The 2038 Problem
tl;dr: “”The 2038 problem" relates to an issue with how Unix-based systems store dates and timestamps. Most Unix systems use a 32-bit signed integer to represent the number of seconds since January 1st, 1970. This is known as the Unix epoch or Unix time. The core of the issue is that a 32-bit variable can only store integers up to 2147483647. Once the system clock ticks past this at 03:14:07 UTC on January 19, 2038, it will integer to overflow, setting its value to −(231).”
TimeData |
|
|
How To Lose Control Of Your Shell — Thorsten Ball
tl;dr: “A few weeks ago I was hacking on language server support in Zed, trying to get Zed to detect when a given language server binary, such as gopls, is already present in $PATH.” Thorsten shares how a seemingly harmless shell command led to catastrophic consequences.
Shell |
|
|
Most Popular From Last Issue |
|
|
Bruno: OS IDE for exploring APIs.
Flyde: Visual programming for developers.
Gleam: Language for type-safe, scalable systems.
Hatchet: A distributed, fault-tolerant task queue.
Luminal: Deep learning library that uses composable compilers.
|
|
Click the below and shoot me an email!
1 = Didn't enjoy it all // 5 = Really enjoyed it
1 … 2 … 3 … 4 … 5 |
|
|
|