/Productivity

My Energy Is A Linear Function, Until It Isn't

- James Stanier tl;dr: Monday to Wednesday are high energy, productive days for James, but Thursday is an inflection point where he's tiring. James discusses how he's trying to rectify this: (1) Purposefully trying to work 10% slower. (2) Being stricter with notifications so there's less context switching. (3) Limiting checking messages to within working hours. (4) Deferring non-essential requests and tasks into the following week. (5) Pomodoro technique.

featured in #354


Benchmarking The Impact Of Session Recording On Performance

- Mathew Pregasen tl;dr: One of the biggest tools to arrive last decade was session recording (SR) – a screen-recording-like service that tracked a user’s activity. Typically, SR was popular with marketers and product managers as a tool to learn more about a user’s experience. Most SR providers will pledge that their products do not impact page performance - this post explores that hypothesis. 

featured in #351


How To Tool For Developer Productivity

- Kathryn Koehler tl;dr: Director of Developer Productivity Engineering at Netflix shares what kind of tooling you should focus on building, whether you should build or buy your tooling, and how to measure the success of your tooling in developer satisfaction and productivity.

featured in #345


On Workplace Productivity

- Nicole Forsgren tl;dr: A holistic framework for productivity can be summarized by the acronym SPACE: (1) Satisfaction and well-being. (2) Performance. (3) Activity. (4) Communication and collaboration. (5) Efficiency. Nicole provides 3 insights: Finding flow is key and interruptions are a drag, meetings are both awesome and terrible, and a two-minute daily reflection can help improve your days. 

featured in #345


Automate Pull Request Labels Based On Changed Files With Actions

- Lloyd Atkinson tl;dr: "That’s a lot of functionality that can be built with labels. As an example, I’ll show how to add labels automatically depending on which area of a codebase has changed. This is what I use in every project I work on as it allows maintainers oversight and awareness of the impacts of changes. It does not depend on the language or types of files - it’s based on the git diff and paths."

featured in #340


State Of Engineering Time 2022

tl;dr: The Stack Overflow memes are true: 60% of senior engineers commit 10-100 lines/week of copied and pasted code. And there is more: read the report to learn how 600 engineers (ICs and managers) spend time, from wrangling machines to wrangling people.

featured in #327


Data And System Visualization Tools That Will Boost Your Productivity

- Martin Heinz tl;dr: "As files, datasets and configurations grow, it gets increasingly difficult to navigate them. There are however many tools out there, that can help you to be more productive when dealing with large JSON and YAML files, complicated regular expressions, confusing SQL database relationships, complex development environments and many others."

featured in #327


The Fallacy Of Splitting Time

- Ben Northrop tl;dr: "There are two projects, both deemed important by the business, and both need a UI developer. Unfortunately, only one UI developer is available. Why not let the UI developer split time across both projects?" Ben explains why this doesn't work using the equation: Productive Time = Total Time - Overhead.

featured in #326


State Of Engineering Time 2022

tl;dr: The Stack Overflow memes are true: 60% of senior engineers commit 10-100 lines/week of copied and pasted code. And there is more: read the report to learn how 600 engineers (ICs and managers) spend time, from wrangling machines to wrangling people.

featured in #321


State Of Engineering Time 2022

tl;dr: The Stack Overflow memes are true: 60% of senior engineers commit 10-100 lines/week of copied and pasted code. And there is more: read the report to learn how 600 engineers (ICs and managers) spend time, from wrangling machines to wrangling people.

featured in #320