featured in #231
featured in #230
Clarity Is An Underrated Skill
- Tom Gamon tl;dr: When talking about code, you'll generally refer to hundreds of lines of code so clarity is key. Some tips: (1) make the implicit explicit - avoid words like "clearly" and "obviously", (2) Be succinct, (3) Avoid ambiguous pronouns.featured in #230
The Art Of Self-organizing Engineering Teams
- Tom Sommer tl;dr: "Purpose, mastery, and autonomy are helpful concepts to enable self-organization. They allow us to guide and create alignment, set up effective processes and workflows, and provide the ability to adjust and change as needed." Tom outlines each in this post.featured in #229
We Need To Talk About Your Q3 Roadmap
- Lara Hogan tl;dr: People are "exhausted and depressed" from the pandemic, police violence, hate crimes. Burn out amongst employees is frequent. Lara outlines how adjusting your upcoming roadmap and leave policies can help.featured in #228
Forget Multi-Tasking. It's Context-Switching That Matters
- Saverio Morpurgo tl;dr: How do you juggle multiple projects simultaneously and (almost) never miss something? Usually that’s defined as multitasking, but it’s actually context-switching that’s the key. And they’re very different things.featured in #228
featured in #227
Being A Manager In Terrible Times
- Lara Hogan tl;dr: There are two primary ways we can support direct reports: proactively, by creating a supportive and safe environment, and reactively, responding to individual crises. Lara outlines both.featured in #227
How To Build Organizational Resilience
- Ryn Daniels tl;dr: An organization needs 3 things to be resilient (1) Learning skills to develop a body of shared knowledge to prevent wasted efforts of addressing the same problems. (2) Tools, processes and psychological safety to communicate effectively. (3) Slack for engineers to be able to perform both proactive and reactive work.featured in #227
Questions To Ask When Choosing A Programming Language
- Shekhar Gulati tl;dr: Shekhar outlines an approach using a decision making matrix and prompting key variables of what's valuable for the organization, such as productivity, suitability for architecture and efficiency.featured in #226