/Management

Why You Should “Design It Twice"?

- Eliran Turgeman tl;dr: “The core message is that you shouldn’t just go with the first design that comes to mind. Instead, come up with at least two different designs even if you have to force yourself. No matter how confident you are, you’ll make better decisions when you compare options side by side.”

featured in #550


Be Plainspoken

- Andrew Bosworth tl;dr: Andrew discusses the superpower of being plainspoken. “Our desire to maintain harmony can cause us to be indirect about uncomfortable truths. Our desire to influence can cause us to pre-emptively address every arcane objection. Our desire to impress can cause us to use more language than necessary. And the expectations we have internalized about corporate communication often cause us to write in a way we never would to our friends.”

featured in #549


Scope Management 101

- Kent Beck tl;dr: (1) Plan incrementally. The team, every week, must be prepared to decide what to do that week. Some planning processes are so painful, or require the sign-off of such overworked people, that contemplating planning weekly causes sweat to bead on foreheads. Learn how to plan lightly as to tactics & resolutely as to goals. (2) Deliver incrementally. The team must be prepared to support production while developing. This in turn requires rock solid reliable tidying & prioritizing the fixing & preventing of defects.

featured in #549


Multi-Tenant vs. Single-Tenant IDaaS Solutions

- Daniel DeGroff tl;dr: “The choice depends on your business model and requirements. Regulatory compliance, security, data management, and upgrade control are important considerations that will ultimately define the most effective solution for your company. Which trade-offs are you willing and able to make? Read some of the most important considerations below and decide which approach fits your business.”

featured in #549


How To Add An Onboarding Flow For Your Application

- Roy Anger tl;dr: Streamline your app's onboarding with Clerk’s customizable session tokens, publicMetadata, and Next.js Middleware. Implement a seamless experience with minimal code.

featured in #549


The Impossibility Of Making An Elite Engineer

- Kent Beck tl;dr: “While all elite engineers face these contradictions, there are as many paths through them as there are engineers.” Kent discusses the pattern he’s seen elite engineers take on with the following: (1) Longevity and diversity of projects. (2) Success and failure. (3) Mentored and self-directed. (4) Urgency and slack. 

featured in #549


The Impossibility Of Making An Elite Engineer

- Kent Beck tl;dr: “While all elite engineers face these contradictions, there are as many paths through them as there are engineers.” Kent discusses the pattern he’s seen elite engineers take on with the following: (1) Longevity and diversity of projects. (2) Success and failure. (3) Mentored and self-directed. (4) Urgency and slack. 

featured in #548


Your Company Needs Junior Devs

- Doug Turnbull tl;dr: “Coaching junior employees becomes its own force multiplier for innovating at scale. It’s not about the added labor, it’s about a psychologically safe culture that values teaching and learning, and the innovation that this unlocks.”

featured in #548


Implementation Challenges Of A Homegrown SCIM Solution

tl;dr: SCIM provisioning is a table stakes feature that nearly every enterprise customer requests. It enables secure and automated user lifecycle management, allowing users to be seamlessly onboarded and offboarded from applications. But building SCIM in-house is incredibly complex. There is a ton of fragmentation you have to deal with because each identity provider (Okta, Azure, etc.) has different ways of interpreting the SCIM protocol.

featured in #548


Founders Create Managers

- Camille Fournier tl;dr: “The only solution to this is to think early and often about the systems of accountability you have to set up. This is much, much harder than micromanaging details, because every system of accountability you set up will eventually be gamed. So in addition to accountability, you need to foster a strong, ethical company culture that encourages transparency while allowing for some mistakes.”

featured in #548