/Management

Listen Or Speak

- Mike Fisher tl;dr: Mike, former CTO at Etsy, discusses how he navigates leadership styles - the under-importance of listening, the over-emphasis on speaking, and examples of how effective leaders leverage both. “While I still prefer a leadership style of listening before speaking, other than in emergency situations, the convergence of speaking and listening are complementary forces in leadership. The dynamic balance between the two crafts a leader who not only inspires but also empowers. Such leaders create environments where dialogue thrives, ideas flourish, and consensus is reached without compromising the vision or the drive needed for action.” 

featured in #491

A Guide To Organization Modeling In Authentication

tl;dr: Organization modeling is a crucial part of building authentication and authorization into applications. However, once SSO and various user-organization relationships are thrown into the mix, the logic can become complex to manage. For developers building this in-house, there are important nuances and implementation details to consider.

featured in #491

The Management Team

- Joel Spolsky tl;dr: “Stop thinking of the management team at the top of the organization. Start thinking of the software developers, the designers, the product managers, and the front line sales people as the top of the organization... The “management team” isn’t the “decision making” team. It’s a support function. You may want to call them administration instead of management, which will keep them from getting too big for their britches.” Managers are administrators who aren’t supposed to make hard decisions but enable others to do so. 

featured in #490

Empty Questions

- Ed Batista Jennifer Ouyang Altman tl;dr: “All too often our questions aren't truly open and honest inquiries. They may be loaded questions, freighted with biased assumptions. They may be leading... or simply be statements in disguise. The problem with these questions is that they're never as clever or well-hidden as we think they are. They feel hokey and theatrical.” Jennifer prompts us to ask empty questions, which release preconceived notions of what the answer is, not forcing an agenda or trying too hard. Empty questions come from a place of empowering, expanding and elevating. Examples are provided. 

featured in #490

Add More Rigor To Your Reference Calls With These 25 Questions

tl;dr: 25 questions including: (1) How does this person compare to the best you’ve ever seen in the role? (2) On a scale of 1 - 100, how would you rank this person? (3) On a scale of 1-10, how do you rate XYZ on specific trait or ability? (4) Can you tell me about a project that would have failed without the candidate? (5) What haven’t I asked that, if you were me, you would want to know about this person?  

featured in #489

How To Measure The Impact Of Generative AI Code

- Ben Lloyd Pearson tl;dr: What’s the ROI of your GenAI code? By the end of 2024, GenAI is projected to generate 20% of all code – or 1 in every 5 lines. Learn how to use PR labels to get telemetry on GenAI code, allowing metric tracking that compares AI-generated code against unlabeled PRs. With this free automation, you can track the ROI of your GenAI investments and identify potential security and compliance risks.

featured in #489

How To Hire Low Experience, High Potential People

- Tara Seshan tl;dr: “After 1000+ hours of interviewing candidates, making many mistakes in hiring and firing, and closely imitating the best possible behaviors of my “hiring savant” managers, this is what I’ve learned about separating the wheat from the chaff in order to find amazing yet unconventional people.” Tara provides a guide for finding such folks. 

featured in #488

A Guide For Notification Systems

- Sam Seely tl;dr: A complete guide for what to consider if you're evaluating whether to build your own notification system or use a third-party vendor.

featured in #488

Accelerating Code Reviews With Nudges

- Abi Noda tl;dr: In 2020, the code review team at Meta discovered that 85% of developers were satisfied with the code review process in general. They were less satisfied with the speed with which their code was reviewed. This inspired a core hypothesis that the NudgeBot could decrease code review time in 3 ways: (1) The time a diff waits in the ‘needs review’ status. (2) The number of diffs that take over 3 days to close, this timeframe was chosen because they were only nudging diffs after 24 hours. (3) The time to first action. 

featured in #488

What Type Of Interruptions Impact Developer Productivity Most?

- Lizzie Matusov tl;dr: Research shows that: (1) Self-interruptions i.e. voluntary task switching is more disruptive than external interruptions. (2) Developers self-reported that external interruptions are more disruptive than self-interruptions. (3) Contextual factors such as time of day are a stronger determinant of how disruptive an interruption might be than task-specific factors. (4) Switching between programming and testing tasks, compared to other development tasks, makes developers more vulnerable to interruptions.

featured in #487