QA Wolf Exits Stealth With An End-To-End Service For Software Testing
tl;dr: QA Wolf has exited stealth, securing $20 million for its platform that automates and ostensibly streamlines the process of testing web-accessible software apps.featured in #398
Three-Bucket Framework For Engineering Metrics
- Abi Noda tl;dr: “CEOs don’t know or care about the technicalities of engineering measurement; what they really want is a way to have confidence that you’re accountable for the millions of dollars they are spending on engineering.” Abi argues that you should be concerned about 3 types of metrics as an engineering leader: (1) Business impact: Current or planned projects, and project roadmap. (2) System performance: Reliability, speed and user experience. (3) Developer effectiveness.featured in #397
featured in #397
Recognition And Rewards At Work
- Lara Hogan tl;dr: “What we recognize is what we reward,” and we often reinforce behaviors accidentally e.g. when ask a team to demo an upcoming release, add a Slack emoji high-five response to a comment, we are recognizing something we like about someones behavior and signaling to those around us that we want to see more of that behavior. Lara provides us with an exercise to establish how we are recognizing and rewarding our teams and reports.featured in #396
Inside Uber’s Move To The Cloud: Part 1
- Gergely Orosz tl;dr: Gergely covers: (1) The history of Uber’s data centers. (2) Challenges of operating your own data centers - hard drives, ODM woes, and the automation of data center maintenance. (3) Incentives and pull factors from Covid-19, the Postmates acquisition, and CapEx and OpEx costs. (4) Cloud basics. A primer on data centers, regions, and availability zones. What these mean for public Cloud providers and businesses like Uber.featured in #396
Project Management For Software Engineers
- Kevin Sookocheff tl;dr: Kevin discusses the 5 phases of managing an engineering project, according to Project Management Institute: (1) Initiation: Identifying and interviewing stakeholders, developing scope statement and getting approval. (2) Planning: Creating comms, project and risk management plan. (3) Execution: Schedule accountability check-ins, adjust to feedback from delivering stepping stones. (4) Monitoring and Control: Regular status reports. (5) Closure: Confirm project is done, document lessons learned, celebrate success.featured in #396
Running Your Engineering Onboarding Program
- Will Larson tl;dr: Will discusses: (1) Fundamental components of onboarding, including examples. (2) Role of executive sponsor, orchestrator, manager and buddy in a typical process. (3) Curriculum to consider including in your onboarding. (4) Why onboarding programs fail. (5) Whether to integrate with wider company onboarding. (6) When to prioritize onboarding.featured in #395
Why You Should Send A Weekly Summary Email
- Jens-Fabian Goetzmann tl;dr: The weekly email has 2 headings, with 3–5 short bullets under each: (1) “Achievements This Week” i.e. the most important things you’ve done this week. (2) “Priorities Next Week:” the most important things you want to get done the following. The benefits are: it starts the week off right, ensure progress on the things that matter, enables introspection, aligns priorities, make invisible work visible and keep a record of achievements.featured in #395
Building Your Executive Network
- Will Larson tl;dr: Will outlines several tactic for engineers to do this. “Your network is a collection of relationships, and relationships always work best when they’re built before you need them. Set a small goal, like meeting one new person each month, and slowly build your network up over time. Don’t make it your top priority, but don’t forget it either.”featured in #394
Move Past Incident Response To Reliability
tl;dr: In this guide you will learn: (1) About the current standard for incident response and analysis. (2) Where some teams get themselves in trouble with the current standard. (3) How to find your own path through the innovation and dogma of leading a company’s approach to reliability.featured in #394