featured in #522
featured in #522
featured in #521
Structuring Engineering Organizations
- Otto Hilska tl;dr: How you split your software organization into teams can make or break developer experience and productivity. Your organization structure should allow each team to make decisions about a clearly defined product area. After reading this blog post, you’ll know how to balance the four defining factors of a team: outcomes, features, people, and architecture.featured in #521
featured in #521
How To Build Engineering Strategy
- Mirek Stanek tl;dr: “In this article, I will explore tools and techniques to help you build a long-term engineering strategy. Some work best at the organizational level, where Product and Technology collaborate on their challenges. Some can also be successfully applied at the team level and can inspire the rest of the organization from the bottom up.”featured in #520
featured in #520
Unexpected Anti-Patterns For Engineering Leaders — Lessons From Stripe, Uber & Carta
- Will Larson tl;dr: “Anytime you apply a rule too universally, it turns into an anti-pattern.” The key to effective engineering leadership, Larson argues, lies in figuring out which scenarios are worth deliberately defying conventional logic, and when to simply follow the rules. “ Will discusses his tonics for the following anti-patterns: (1) Shying away from micromanagement. (2) Pushing back on flawed metrics. (3) Serving as the umbrella for your team.featured in #519
Signposting: How To Reduce Cognitive Load For Your Reader
- Wes Kao tl;dr: “Signposting is using key words, phrases, or an overall structure in your writing to signal what the rest of your post is about. This helps your reader quickly get grounded, so their brain doesn’t waste cycles wondering where you’re taking them.” Wes shares how to implement this when writing about complex ideas.featured in #518
featured in #518