June 2025 Summaries

Over a three-year period as a founding engineer, the author discovered that their practice of conducting code reviews only once a day significantly hindered team productivity. Initially believing that batching reviews would preserve deep focus time, the author realized that this approach led to cumulative delays as engineers juggled multiple tasks while awaiting feedback. This resulted in frequent context switching, which consumed mental energy and complicated the task of recalling details about past work. Insights from Google's research revealed that faster code reviews improve perceptions of the review process, transforming potentially obstructive feedback into constructive guidance. To address this, the author suggests integrating code review requests as priority interrupts between focused work sessions, instead of batching them, to enhance team velocity and collaboration. This approach is particularly crucial in distributed work environments and with the increasing use of AI-generated code, where timely human oversight is essential for maintaining quality. By prioritizing code review as a collective responsibility, teams can achieve greater productivity and code quality, as demonstrated by the author's experience and the influence of a former coworker, Tom McIntyre.

AI-powered coding assistants like Cursor can be enhanced significantly through the use of Cursor Rules files, which provide persistent, system-level instructions tailored to a project's specific patterns, best practices, and constraints. These files serve as onboarding documentation for AI, using direct and positive instructions to guide coding conventions on style, naming, preferred patterns, and deprecated practices. Concrete examples and project-specific context further aid in making AI suggestions more relevant and effective. It's crucial to keep these rules concise, targeted, and updated based on feedback to ensure they remain effective. Centralizing guidelines into a single source of truth can transform AI's utility, elevating productivity by reducing repetitive corrections and enhancing focus on task-specific work. Investing in well-crafted rules files not only improves AI output but also contributes to a cohesive and efficient development process, enabling teams to maximize the benefits of AI integration through better alignment with project needs and consistent code quality.

Engineering dashboards are essential tools for tracking the performance of both individual developers and teams, offering insights into productivity, efficiency, and project health. While team dashboards provide a high-level view of collective output and strategic decision-making, individual dashboards focus on personal contributions, work patterns, and areas for growth. These dashboards integrate with various development tools to deliver real-time data and advanced visualizations, aiding in the identification of bottlenecks and optimization of workflows. Platforms like Weave use machine learning to analyze engineering work, offering customizable dashboards that align engineering output with business objectives. The synergy of using both individual and team dashboards allows for a comprehensive understanding of engineering effectiveness, facilitating better decision-making and continuous improvement. The choice of metrics and strategy should align with team objectives, maturity, and culture, ensuring the data supports growth rather than fostering competition or micromanagement. Ultimately, dashboards serve as tools to promote transparency, accountability, and a culture of continuous improvement within engineering teams.

Software teams are often under pressure to deliver quickly, but prioritizing speed without considering team well-being can lead to adverse effects such as burnout and reduced code quality. To enhance team velocity sustainably, engineering leaders should adopt a balanced approach involving clear metrics, sustainable practices, and the use of modern analytics tools like Weave, which offer a comprehensive view of team performance. Team velocity, a key metric in Agile development, should be understood as a reflection of team health, process efficiency, and goal clarity, rather than just a numerical target. Consistency in sprint lengths and structures is essential to maintain a reliable workflow, while regular retrospectives provide a platform for addressing challenges and celebrating achievements. Additionally, investing in skills development and automating repetitive tasks can empower engineers, boost morale, and increase capacity for high-value work. By focusing on setting clear goals, maintaining a consistent cadence, and fostering a healthy team culture, leaders can improve productivity without causing burnout, using analytics platforms to provide actionable insights for continuous improvement.

Engineering leaders can significantly enhance team performance and project success by utilizing real-time analytics dashboards, which transform complex data into actionable insights, leading to up to 30% faster project delivery and fewer bottlenecks. Effective dashboards go beyond mere data display by revealing patterns, highlighting risks, and assisting in decision-making, ensuring that teams remain aligned and productive. Essential dashboards for engineering leaders include those that measure engineering efficiency, track project delivery progress, analyze team performance, and understand the impact of AI tools, with platforms like Weave setting new standards in engineering analytics. These tools provide a balanced view by incorporating frameworks such as DORA Metrics and the SPACE Framework to avoid focusing on single metrics, thus supporting a comprehensive understanding of team dynamics. By leveraging machine learning for advanced analytics, these dashboards help identify hidden strengths and weaknesses, monitor AI tool adoption and impact, and proactively detect and resolve bottlenecks, ensuring that engineering efforts align with business goals and drive continuous improvement.

Weave introduces an innovative approach to measuring engineering team performance by leveraging large language models (LLMs) and domain-specific machine learning, offering a more objective and standardized alternative to traditional story points. Story points have been criticized for their subjectivity and inconsistency across teams, failing to capture the true quality and impact of work. In contrast, Weave evaluates pull requests and code reviews based on complexity, scope, and quality, providing real-time insights into team performance that are less susceptible to manipulation. By tracking actual output and quality rather than mere activity, Weave's analytics platform helps identify where teams allocate their time, offering comprehensive dashboards for easy review and analysis. It integrates with popular tools like GitHub and Jira, allowing seamless incorporation into existing workflows, and is particularly beneficial for distributed teams or organizations with multiple squads. This shift to AI-driven analytics allows for more effective resource allocation, improved code quality, and enhanced team collaboration, marking a significant advancement in engineering management practices.

Engineering teams increasingly rely on AI-powered analytics to enhance productivity, track performance, and streamline workflows. Over 70% of engineering leaders use these tools to gain insights into team dynamics and project outcomes. AI-driven platforms, such as Weave, leverage large language models and domain-specific machine learning to provide real-time analysis of code commits, pull requests, and project management data. These tools offer features like automated metric tracking, real-time bottleneck detection, and AI-powered sprint planning, integrating seamlessly with existing tools such as GitHub and Jira. By focusing on outcomes rather than mere activity, AI analytics platforms help engineering managers identify strengths, weaknesses, and potential risks, enabling proactive decision-making. As AI continues to evolve, it promises deeper insights into team operations and more effective support for engineering teams, with AI adoption metrics becoming crucial for understanding productivity impacts.

Engineering leaders often struggle with choosing the right analytics tools to effectively measure team productivity and identify underlying issues. While platforms like Jellyfish are popular for tracking high-level metrics like DORA and R&D cost capitalization, they often lack the qualitative insights necessary to fully understand developer challenges and improve workflows. Alternatives to Jellyfish, such as Weave, LinearB, Swarmia, Pluralsight Flow, Code Climate Velocity, and Plandek, offer varied strengths, including a focus on blending qualitative and quantitative insights, enhancing developer experience, and providing customizable and actionable data. Each platform presents unique advantages and limitations, ranging from integration capabilities and customization options to ease of adoption and focus on team dynamics. Selecting the right tool depends on a team's specific needs, including workflow complexity, size, and the desired balance between performance metrics and developer well-being. Ultimately, the key is to choose a tool that aligns with the team's goals and fosters continuous improvement.

Engineering teams are increasingly turning to AI-driven analytics, with 65% of organizations exploring these technologies to enhance software development processes and meet the growing demand for faster, high-quality software delivery. Traditional metrics like lines of code or commit counts fall short in capturing the complexities of modern development, prompting the rise of advanced engineering analytics platforms such as Weave. These platforms employ large language models, machine learning, and real-time data streaming to provide deeper insights into team performance, identify bottlenecks, and improve productivity by analyzing code review quality and AI tool usage. The shift towards data mesh architectures decentralizes data ownership, facilitating cross-functional collaboration and informed decision-making. Established frameworks like DORA, SPACE, and CORE 4 offer various perspectives on measuring productivity, but platforms like Weave aim to fill gaps by integrating with tools like GitHub and Jira, unifying data, and offering comprehensive insights. As engineering analytics continue to evolve with AI and machine learning, teams that adopt these tools gain a competitive edge in optimizing processes and responding proactively to challenges.

AI adoption in engineering is progressing rapidly, with global spending on generative AI expected to reach $644 billion by 2025, yet many companies are still struggling to fully integrate these tools into their workflows. Traditional engineering metrics like DORA and developer experience need adaptation to properly assess AI's impact, as they often fail to capture the nuances of AI-driven workflows. Key metrics in this context include AI usage, code turnover, and expert engineering hours, which help quantify AI's role in productivity and quality. Top-performing teams balance speed, quality, and developer satisfaction by linking AI usage data to outcomes such as code quality and bug rates. Frameworks like DORA and SPACE remain relevant but require integration with AI-specific data to provide a comprehensive view of performance. Tools like Weave are emerging to support teams in measuring and optimizing AI adoption, allowing for a nuanced understanding of how AI influences engineering output and decision-making.

Engineering teams integrating AI tools into their workflows are increasingly focused on measuring both the adoption and impact of these technologies to optimize performance and understand return on investment. Weave, among other analytics platforms, offers capabilities to track key metrics such as engineering productivity, AI tool usage, and the incorporation of AI into engineering workflows. By examining productivity metrics before and after AI adoption, teams can assess the impact on outcomes like code quality, review cycles, and bug resolution rates. A structured measurement framework, supported by automated data collection and continuous analysis, is essential for drawing correlations between AI usage and performance improvements. This approach ensures that teams not only accelerate development and improve code quality but also enhance developer experience and satisfaction. As AI adoption grows, organizations must implement sophisticated measurement techniques to capture its influence on engineering culture, innovation, and collaboration, ultimately enabling data-driven decisions that maximize AI's transformative potential.

In the competitive tech landscape, engineering leaders are challenged to deliver more value with fewer resources, making effective productivity measurement essential. Traditional metrics like lines of code are inadequate, prompting the adoption of comprehensive frameworks such as DORA, SPACE, and value stream metrics to evaluate team performance holistically. These frameworks assess various dimensions, from deployment frequency and mean time to recover to developer satisfaction and workflow efficiency. Tools like Weave enhance productivity measurement by providing data-driven insights into cycle time, inner and outer loop activities, and pull request metrics, enabling teams to identify bottlenecks and improve collaboration. High-quality code reviews, PR size, and stability indicators are crucial for maintaining code quality and team cohesion. Engineering leaders are encouraged to implement a balanced measurement strategy that aligns with business goals and developer well-being, using the insights gained to drive continuous improvement and foster a supportive work environment.

DORA metrics, popularized by their perceived scientific approach and backing from Google, are widely used to measure DevOps processes but are often misinterpreted as indicators of team productivity. Originating from the 2014 State of DevOps Report and later developed by the DevOps Research and Assessment group, DORA metrics include Deployment Frequency, Lead Time for Changes, Change Failure Rate, and Time to Recovery. While these metrics provide a simplified view of DevOps efficiency, they do not measure the actual productivity or value delivered by engineering teams. The limitations of DORA metrics are highlighted by their inability to account for the substance and value of work done, leading to potential misuse where teams prioritize speed over meaningful productivity. To address these gaps, the Weave tool has been developed to offer more comprehensive productivity measurements by using AI to assess the quality and impact of code reviews, individual contributions, and overall team performance, thereby shifting the focus from speed to value creation.

The shift to remote work and increased reliance on AI tools has highlighted the critical importance of deep work for software engineers, despite a cultural trend towards more frequent meetings and multitasking. The notion of deep work, popularized by Cal Newport, involves focused, undistracted engagement with complex tasks, essential for reaching a productive flow state where engineers are significantly more efficient and make fewer mistakes. However, the rise in meetings—up by 13.5% since COVID-19—and the tendency for engineers to multitask during these meetings, often results in shallow work, impeding deep work time and reducing overall productivity. The article argues that while AI tools promise efficiency, they cannot replace the need for sustained focus, as constant task-switching diminishes the quality of work. To counteract this, it suggests improving meeting culture by reducing unnecessary meetings, setting aside designated deep work time, and fostering an environment where engineers can work uninterrupted, thus enhancing both productivity and work-life balance.