featured in #313
Five Measurements You Should Make And Then Ignore (Plus One To Watch Intently)
- Jessica Kerr tl;dr: "The purpose of a software team is to provide valued capabilities to customers, internal or external. To do that, our software has to be up, it has to be fast enough, usable enough — a whole slew of properties that don’t show up in JIRA." Jessica discusses 5 key properties - Availability, Security, Flow, Delight and Value - their measures, and questions they prompt.featured in #312
The Mechanics Of Software Evolution
- Kislay Verma tl;dr: "Use feature requests as a breeding ground for the next generation of the system’s architecture. By continuously evaluating what we are being asked to change, we can jump the gun and get to the next level faster and often more safely."featured in #312
Startup Getting Started? Think Pragmatic Security
tl;dr: There is an assumption that security should be the main priority for a founder when getting your startup going. Think again. Security is a tool to protect your customers and your business, and a founder’s main concern is growing that business. That’s a good thing -- here's how.featured in #312
The Workplace Perks Your Developers Actually Want
- Nicole Kow tl;dr: (1) Expanding care benefits for the young and elderly - "61% of companies are opting for more flexible childcare benefits." (2) Flexibility - "2 out of 3 workers still want a balance between complete flexibility and a predictable work schedule." (3) Focusing on mental health - "76% of respondents reporting at least one symptom of a mental health condition in 2021."featured in #312
Working With A Non-Technical CEO
- Paulo André tl;dr: "While this targets primarily VPs of Engineering, the principles and practices are entirely applicable at all levels of the org. They will help you develop solid working relationships with any non-technical stakeholders." Paulo breaks this post into: (1) Importance of starting with the end in mind. (2) Your role as a leader. (3) The mindset of an effective VP of Engineering. (4) Learn, adapt and improve.featured in #311
11 Principles Of Engineering Management
- Alan Johnson tl;dr: Principles include (1) Managing comes first, "stay out of the critical path of execution, wherever possible." (2) Facilitate wellbeing so "personal safety, dignity, and wellbeing of everyone is paramount." Make sure the quiet voices are heard. (3) Practice integrity. "Be transparent with information you can share. Be transparent about when you cannot do something. Keep your commitments. Own up to your mistakes." And more.featured in #311
Counterintuitive Lessons Learned About Devtool Pricing
- James Hawkins tl;dr: Changing your pricing has a real chance to grow twice as fast with just a few hours of work. "Here is a breakdown of the counterintuitive lesson I've learned as a cofounder."featured in #311
How To Build Remote Teams Properly
- Vadim Kravcenko tl;dr: Vadim splits the topics into four categories: (1) Onboarding. (2) Day-to-day business, discussing methods that make life easier when you don’t see your employees every day. "Small things that may seem unimportant but have a huge impact." (3) Culture, people feel happy and engaged. (4) Results, making sure the team delivers and pushes the company forward.featured in #311
Mailbag: Resources for Engineering Directors
- Will Larson tl;dr: Brie provides 10 personal templates for "more efficient progress towards your goals and make the experience of getting there more satisfying." Examples include Ongoing Stack Rank (OSR), “It’s Only The Weekend When” Post-It, “What I’m Proud Of” Scrapbook.featured in #310