The hottest Metrics Substack posts right now

And their main takeaways
Category
Top Technology Topics

Quality Engineering Basics: Quality Metrics

QUALITY BOSS • 39 implied HN points • 25 Mar 24
🕹 Technology Software Engineering Metrics Quality Automation
  1. Metrics help show how good a product is and can lead to improvements. They can boost quality and user happiness.
  2. Bug metrics track issues like how many bugs are found after release and how long they take to fix. This helps teams focus on areas needing help.
  3. Product and automation metrics can include customer satisfaction and how well automated tests work. They help understand what's going right or wrong in the product.

The 3 Pillars of Observability in Distributed Software Systems[System Design Sundays]

Technology Made Simple • 99 implied HN points • 19 Jun 23
🕹 Technology Observability Metrics
  1. Observability in distributed software systems is crucial as they grow in complexity and scale.
  2. The 3 pillars of observability are logs, metrics, and traces, each offering unique insights into the system's operations.
  3. Combining logs, metrics, and traces is essential for building tools that enhance observability and improve system performance.

Bits, Bytes, and Bylaws: Timeless Computing Laws (Part - 2)

Wisdom over Waves • 59 implied HN points • 28 Dec 23
🕹 Technology Software Development Programming Organizational Design Metrics Management
  1. Adding more people to a late software project can make it even later due to various factors like onboarding time, increased coordination needs, and additional deployments causing outages.
  2. When a measure becomes the target, it loses its effectiveness, leading to actions like renaming variables or engaging in practices that prioritize metrics over true code quality.
  3. The structure of the software often mirrors the communication structure of the organization that designed it, showcasing the impact of company dynamics on software architecture.

Choosing the right UX metrics - Part 2

UX Psychology • 158 implied HN points • 03 Oct 22
🕹 Technology UX Design Metrics Product Management User Experience Data Analysis
  1. Identifying clear goals is crucial in choosing the right UX metrics, involving team and stakeholders can help define meaningful and actionable metrics.
  2. Mapping goals to signals helps track progress towards goals; gathering user feedback and reviews can be essential signals to measure UX success.
  3. Refining signals into specific metrics is the final step, where data scientists can assist in ensuring metrics are measured accurately; focus on key metrics and avoid adding unnecessary data.
Get a weekly roundup of the best Substack posts, by hacker news affinity:

How to calculate P/E ratio

Shivansh • 19 implied HN points • 26 Apr 24
💰 Finance Investing Stocks Valuation Metrics Market Analysis
  1. P/E ratio compares a company's stock price with its earnings per share, providing insight into investor perception and market sentiment.
  2. Calculating P/E ratio involves dividing the current stock price by the company's earnings per share (EPS).
  3. Different types of P/E ratios like trailing and forward help in assessing past performance and future earnings, aiding investors in comparing valuations and identifying trends across industries.

Choosing the right UX metrics - Part 1

UX Psychology • 119 implied HN points • 20 Sep 22
🕹 Technology UX Design Metrics User Experience Product Analytics Feature Prioritization
  1. UX metrics are vital for making evidence-based UX decisions instead of relying on opinions and beliefs.
  2. Using a combination of attitudinal and behavioral metrics can provide a comprehensive understanding of user experience.
  3. The HEART framework - Happiness, Engagement, Adoption, Retention, and Task Success - offers a structured way to select and track UX metrics for data-driven decision-making.

What does it look like to be successful here? How is my performance evaluated?

Creating Value from Nothing • 79 implied HN points • 14 Mar 24
💼 Business Performance Management Culture Metrics Tradeoffs
  1. Evaluation of performance in the Product organization focuses on inputs like quality of thinking over outputs.
  2. Avoiding using output targets to evaluate performance is important to maintain a customer-centric culture, prevent tunnel vision, and discourage risk aversion.
  3. While metrics are essential, team members are rewarded for excellent inputs rather than just meeting success criteria, emphasizing the priority of creating value for customers.

☁ How to Build an ARR Book (Part 1)

Hard Mode by Breaking SaaS • 39 implied HN points • 13 Nov 23
💼 Business SaaS Metrics Analysis Investment Training
  1. An ARR book is essential in SaaS analysis to track customer contracts and calculate key metrics.
  2. The underlying data for an ARR book comes from customer contracts, detailing customer information and contract specifics.
  3. To convert contract data into an ARR book, organize logos and periods, calculate ARR changes, and categorize them into New Logo ARR, Expansion ARR, Logo Churn, and Downsell/Shrinkage.

Evaluating Team Effectiveness with a Data-first Approach | Bhavini Soneji, Executive Leader (ex-Cruise, Headspace, Microsoft)

platocommunity • 19 implied HN points • 15 Feb 24
💼 Business Leadership Metrics Team Dynamics Execution Measurement
  1. Empowering people to discover their strengths and amplify their impact is key in leadership.
  2. When measuring team effectiveness, consider the three buckets: what (strategic value), how (execution), and who (team dynamics).
  3. Combining measurement with follow-through techniques is crucial to determine if you're measuring the right things and drive continuous improvement.

The Engineering Leader's Process for Continuous Improvement

Developing Leadership • 39 implied HN points • 25 Apr 23
💼 Business Leadership Engineering Metrics Organization Decision-making
  1. Engineering leaders have two main responsibilities: improving developer experience and delivering impact to end-users.
  2. The Engineering Leader's Process for Continuous Improvement involves identifying, discussing, deciding, aligning, acting, and measuring.
  3. It is important for engineering leaders to continuously loop through the improvement process, not just during times of issue.

Beyond Code Generation: Rethinking Dev Productivity in the Age of AI

Maestro's Musings • 105 implied HN points • 14 Sep 23
🕹 Technology AI Software Development Productivity Metrics Collaboration
  1. Software development involves more than just writing code; it's a symphony of collaboration, communication, and coordination.
  2. Developers spend a small fraction of their day writing code; other activities like collaborating, debugging, and planning play significant roles.
  3. AI can enhance developer team productivity by focusing on automated testing, augmented code reviews, automated project management, and more beyond code generation.

The Hero Culture Trap | Sowmya Subramanian

Dev Interrupted • 9 implied HN points • 07 Jan 25
🕹 Technology Engineering Culture Metrics Business Leadership
  1. Building a good team means moving from putting out fires to being proactive. Focus on planning ahead so your team doesn’t always have to deal with emergencies.
  2. Rushing to ship new features isn't always best. Sometimes, following others and quickly adapting ideas can work better in the long run.
  3. When writing code, clear instructions lead to better results. If you’re vague, your code might end up messy and confused.

Dangerous metrics

Sunday Letters • 59 implied HN points • 20 Dec 22
🕹 Technology Software Development Metrics AI Productivity Team Management
  1. Measuring developer productivity is really hard. Common metrics like lines of code or bugs fixed often don't tell the full story and can even be manipulated.
  2. It’s important to think about how a metric could be misused before applying it. Focusing on the wrong metrics can lead to unhelpful outcomes and confusion.
  3. Organizations learn and respond to metrics, but sometimes they take things too literally. Choosing the right metrics carefully is crucial to avoid unintentional negative effects.

The Startup CTO's Handbook | Zach Goldberg

Dev Interrupted • 37 implied HN points • 20 Feb 24
🕹 Technology Engineering Leadership AI Metrics Development
  1. The core sections of The Startup CTO's Handbook include Management Fundamentals, Technical Leadership Concepts, and Hard Technology Decisions.
  2. Conducting career history interviews when hiring can reveal a candidate's mindset and how they handle challenges.
  3. Engineering leaders can stay technically relevant by reviewing pull requests and taking courses, even when not coding regularly.

How Much Data Is Too Much?

Build To Scale • 19 implied HN points • 15 Sep 23
💼 Business Metrics Decision-making Analytics Culture
  1. Focus on a small set of key metrics at the executive level to avoid conflicting views and promote progress.
  2. Be cautious of over-analyzing data and creating a culture where analysis overshadows taking necessary actions.
  3. For startups, while revenue predictability is important, it's natural to experience volatility, especially in early stages.

A Quest for Accurate North Star Metrics

Balancing Act • 19 implied HN points • 07 Apr 23
💼 Business Metrics Real Estate Blockchain Market Analysis
  1. North Star Metrics are crucial for measuring business success, but accurately comparing them to competitors can be challenging.
  2. Real estate data, particularly from the MLS, provides companies like Zillow and Redfin with precise market insights for measuring market share.
  3. Selecting and refining a North Star Metric as a business grows is essential, and leveraging industry-specific data sources can improve metric accuracy.

Standardized usability questionnaires: which one to use?

UX Psychology • 79 implied HN points • 16 Dec 21
🕹 Technology Usability User Experience Research Metrics
  1. Standardized usability questionnaires have many advantages like objectivity, reliability, and validity.
  2. There are various post-test standardized usability questionnaires available, such as QUIS, SUMI, PSSUQ, SUS, and SUPR-Q, each with unique features and applications.
  3. Choosing the right questionnaire depends on factors like the nature of the project, stage of research, goals of the study, and budget limitations.

Applying the SPACE Framework

Engineering Enablement • 23 implied HN points • 12 Jan 24
🕹 Technology Productivity Developer Tools Software Metrics Frameworks
  1. The SPACE Framework for developer productivity includes dimensions like satisfaction, performance, activity, communication, and efficiency.
  2. SPACE is useful for software organization leaders defining productivity, teams seeking comprehensive measurements, and leaders involving teams in productivity improvement.
  3. Implementing SPACE involves understanding various metrics, balancing workflow and perception measurements, and considering the holistic approach to developer productivity.

Three Dimensions of Developer Productivity

Engineering Enablement • 31 implied HN points • 01 Sep 23
🕹 Technology Developer Productivity Software Development Engineering Metrics
  1. Developer productivity can be conceptualized through three dimensions: Velocity, Quality, and Satisfaction.
  2. Leaders should clarify their goals for measuring productivity by considering stakeholders, level of measurement, and time period.
  3. Transitioning from dimensions to selecting metrics can be done using the Goals, Signals, Metrics approach.

Applying the DevEx framework

Engineering Enablement • 14 implied HN points • 01 Mar 24
🕹 Technology Developer Productivity Frameworks Metrics Data Collection
  1. The DevEx framework focuses on the lived experiences of developers by measuring feedback loops, cognitive load, and flow state to enhance developer productivity.
  2. Teams interested in using metrics to improve developer productivity, such as platform engineering teams, engineering managers, and engineering executives, can benefit from implementing the DevEx framework.
  3. To successfully implement the DevEx framework, organizations should focus on getting feedback from developers, setting targets, driving impact through projects, running experiments, and then measuring progress to improve developer experience and productivity.

Three-Bucket Framework for Engineering Metrics

Engineering Enablement • 38 implied HN points • 10 Mar 23
🕹 Technology Metrics Engineering Leadership Productivity Development
  1. Deciding what metrics to track and report to stakeholders is a common challenge for engineering leaders.
  2. Reframing the problem and using a three-bucket framework can help in choosing relevant engineering metrics.
  3. The three buckets for engineering metrics include business impact, system performance, and developer effectiveness.