/Management

Cathedral Vs Bazaar People Management

- Ben Balter tl;dr: The cathedral and the bazaar are two contrasting styles of people management, inspired by the open source movement. The cathedral style is more hierarchical, controlled, and standardized, while the bazaar style is more decentralized, autonomous, and collaborative. As a manager or as someone who is managed, you should know which style you prefer, and which style your manager prefers. 

featured in #479


Measuring Engineering Velocity On A Software Team

- Zach Zaro tl;dr: Zach Zaro, CEO and cofounder of Coherence, reviews the history and state of the art of velocity. Measuring engineering velocity is a valuable exercise for software teams aiming to improve their processes and deliver value consistently. By understanding its nuances and potential pitfalls, teams can use velocity as a tool for growth and continuous improvement rather than a blunt instrument of judgment.

featured in #479


Want to Be a Better Leader? Stop Thinking About Work After Hours.

tl;dr: "It’s not uncommon for managers to continue thinking about their job, even after the official workday is over. This may involve ruminating about an issue with an employee, trying to think of a solution to a client problem, or creating a mental to-do list for the next day. But new research shows that this tendency may not be beneficial, particularly for people new to a leadership role. In fact, constant rumination leads managers to be more depleted and less able to show up as leaders — something even their employees can pick up on."

featured in #479


Software Quality

- Abi Noda tl;dr: "Google‘s Engineering Productivity Research team subscribes to the belief that no single metric captures developer productivity. Instead, they break developer productivity down into three dimensions: speed, ease, and quality. Anytime they’re measuring one of the three dimensions (for example, how long it takes for code reviews to be completed), they also measure the other two to surface potential tradeoffs." Quality is broken down into 4 areas - Process, Code, System and Product, which Abi dives into. 

featured in #478


Enhance Your Authentication: Exploring the Simplicity and Security of Passwordless Login with Next.js and Clerk!

- Nick Parsons tl;dr: Discover the simplicity of passwordless authentication with magic links—enhanced security, streamlined user experience, and compliance benefits. Clerk's Next.js App Router tutorial simplifies implementation for accessible authentication.

featured in #478


The 30 Best Pieces Of Advice In 2023

tl;dr: "We present our collection of little tactics, resonant reminders and operating principles to guide you in the following roundup of the 30 best pieces of advice we heard in the past year. Take them with you as we’re thrust forward into all that 2024 has ahead:" (1) Hit refresh on your interview questions for manager candidates. (2) Set goals by trying to tell a story. (3) Opinions come at a cost — spend wisely. (4) Balance the core product with new bets by looking to the horizons. (5) Pinpoint where you’re delivering feedback as a manager. 

featured in #477


Unlocking the Power of Your Permissions: Clerk's New Authorization Helpers

- Colin Sidoti tl;dr: Clerk Introduces Enhanced Authorization with has(), protect(), and <Protect> for tailored user permissions and security. Make Customizing Access a Breeze. Get Serious About Access Management!

featured in #477


Factors That Can Affect The Development Time Of Your MVP

tl;dr: The concept of a Minimum Viable Product has emerged as a beacon for startups and entrepreneurs. However, the development time required to breathe life into the MVP is an intricate equation, influenced by a multitude of factors. In this blog post Match.dev team summarizes non-obvious factors that can negatively affect the development time of your MVP.

featured in #477


How to Write Great Tech Specs

- Nicola Ballotta tl;dr: Nicola covers: (1) What a tech specs document is, why it's important, and why it can sometimes be challenging to create one. (2) How to create outstanding tech specs. (3) A Notion system for creating tech specs. (4) Tips from both his own experience as well as the communities.

featured in #476


How We Work Asynchronously

- Ian Vanagas tl;dr: Besides being difficult to pronounce, being asynchronous means people can work autonomously and on their own schedule, even if other teams members aren’t immediately available. This post shares PostHog's not-so-secret strategies for working asynchronously across 11 countries.

featured in #476