The Daily Life Of Software Developers

- Abi Noda tl;dr: "Researchers identified 11 factors impacting developers’ assessment of a good workday. The factors were organized into three high-level factors, (1) value creation, (2) efficient use of time, and (3) sentiment." This post covers each of these factors in more depth. 

featured in #354

How Passwordless Works

- Alan Parra tl;dr: This blog post by Teleport explains how passwordless can be implemented using modern technologies such as WebAuthn, while at the same time providing a better user experience and security than the traditional password-based approach.

featured in #354

The Hierarchy Is Bullshit (And Bad For Business)

- Charity Majors tl;dr: "It took two decades, an IPO and a vicious case of burnout before she allowed herself to admit how much she hated her work, and how desperately she envied (guess who??) the software engineers she worked alongside. Turns out, all she ever really wanted to do was write code every day. And now, to her dismay, it felt too late. Why did it take Molly so long to realize what made her happy? I personally blame the fucking hierarchy."

featured in #354

What Makes Developers Unhappy?

- Abi Noda tl;dr: Large-scale study with over 2,000 developers that looked to understand the top 10 causes of unhappiness, the top 5 being: (1) Being stuck in problem solving. (2) Time pressure. (3) Bad code quality and coding practice. (4) Under-performing colleague. (5) Feel inadequate with work. And more. 

featured in #353

Resources For Navigating Complex Leadership Work

- Lara Hogan tl;dr: A resource hub for leaders and managers on 9 key topics including: (1) Influence & managing up. (2) Leading through crises. (3) Cross-functional relationships. (4) One-on-ones. (5) Hiring. (6) Meetings. (7) Feedback & performance reviews. (8) Communication & team dynamics. (9) Adapting your approach.

featured in #353

Quality Is Systemic

- Jacob Kaplan-Moss tl;dr: "Software quality is more the result of a system designed to produce quality, and not so much the result of individual performance." Jacob shares examples: (1) Well-designed testing harnesses that make it easy to write tests, and team / company culture that encourages writing good tests. (2) Easy-to-use, high-fidelity dev and staging environments. (3) Codebases that are documented, well-factored, and sufficiently commented. And more.

featured in #353

Group Dynamics: The Leader's Toolkit

tl;dr: "One of the most significant themes in my practice is the leader whose team of direct reports are experiencing difficulties working together." Ed guides us through the following tools leaders have here: (1) Logistics: ways of meeting that could be more impactful. (2) One-on-ones: feedback is normal and frequent. (3) Group facilitation: emphasis on process, as opposed to content. (4) Group observation: the group can observe. (5) Group composition: the right people are involved. 

featured in #352

On The Team As A System

- Vicki Boykis tl;dr: "The critical idea of the blog post is that developers do not work alone: building a product is a team project, and the product itself is a system. And a group of developers working on a single goal also becomes a system that works either together or at cross-purposes with itself." 

featured in #352

Compliance Simplified: Demystifying Risk Assessment

tl;dr: An information security ("InfoSec") risk assessment is not only a security best practice but also necessary to meet the requirements of the ISO 27001, SOC 2, PCI DSS, and HIPAA compliance standards. Learn more from cybersecurity and data privacy expert Matt Cooper in this short video!

featured in #352

One-On-Ones With Executives

- Will Larson tl;dr: "Often when an organization is going through some turmoil, executives think to themselves, “Ah, I should have some one-on-ones with the team so they can hear how we’re handling this.” Will advises those asked to have a 1-1 with execs: (1) If you’re not sure what’s happening, let the exec take the lead. (2) Try to figure out why the meeting is happening before you’re in the meeting. (3) Know that the executive will very likely have an agenda, but sometimes have no agenda at all, in which case it’s very helpful to have prepared ahead of time. And more. 

featured in #351