# developer-productivity Developer productivity concerns how software developers work and how their productivity is understood and measured. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## What does DX do? Key features, use cases, and alternatives DevFeed: [What does DX do? Key features, use cases, and alternatives]() Original publisher: [Read original article]() Author: John Crowley Published: 2026-09-09T15:53:52Z Content type: article Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [code productivity](), [developer-productivity](), [Developer experience](), [atlassian](), [Git](), [Instrumentation](), [sdlc](), [Artificial Intelligence]() Tags: [agentic](), [ai](), [atlassian](), [developer-experience](), [developer-productivity](), [engineering](), [git](), [instrumentation](), [metrics](), [sdlc](), [survey]() ### AI overview This article explains what DX does as an engineering intelligence platform. DX measures developer productivity, developer experience, delivery data, and AI's impact on codebases using developer surveys and data from Git and Jira. It describes DX's DevEx Cloud, DX Data Cloud, DX AI, and Fabric offerings, along with their research-backed metrics, use cases, limitations, and alternatives. ### Source excerpt What DX does: its engineering intelligence features, survey-based metrics, common use cases, where it stops, and the alternatives ## AI governance gaps leave developer and agent access to AI tools insufficiently controlled DevFeed: [AI governance gaps leave developer and agent access to AI tools insufficiently controlled]() Original publisher: [Read original article]() Author: Anubhav Sharma Published: 2026-08-05T01:56:41Z Content type: opinion Language: en Sources: [Nirmata]() Topics: [ai-governance](), [Security](), [Access Control](), [Authorization](), [developer-productivity](), [Monitoring](), [Large Language Model]() Tags: [access-control](), [ai](), [ai-governance](), [cloud-native](), [cncf](), [developer](), [devsecops](), [engineering](), [kubernetes](), [kyverno](), [llms](), [policy-management](), [risk-management](), [security](), [visibility]() ### AI overview The article presents aggregated responses from security leaders about AI governance in fast-moving engineering organizations. It identifies gaps in centralized access control, policy enforcement, session auditing, real-time visibility, and protection against exposing permissions or environment variables to LLMs. ### Source excerpt Three Questions We Asked About AI Governance -- And What the Answers Reveal Over the past few months, we've been having the same conversation on repeat with security leaders about AI at fast-moving engineering organizations. Different companies, different tech stacks, same three questions -- and,... The post The AI Innovation-Security Paradox first appeared on Nirmata. ## Top 3 agentic workflows for platform engineers in Port DevFeed: [Top 3 agentic workflows for platform engineers in Port]() Original publisher: [Read original article]() Author: Tomasz Skora Published: 2026-07-31T11:56:54Z Content type: article Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [Platform Engineering](), [AI Development](), [Tech Debt](), [Developer experience](), [developer-productivity](), [software-development]() Tags: [agentic](), [developer-experience](), [developer-productivity](), [platform](), [platform-engineering](), [software-development](), [tech-debt](), [workflows]() ### AI overview This article introduces agentic workflows for platform engineers, describing how AI agents can be integrated into existing software development and platform operations. The supplied excerpt focuses on autonomously resolving non-urgent engineering tasks, such as minor bugs, UX/UI issues, and refactoring, to reduce tech debt and improve developer productivity. ### Source excerpt Learn about the agentic workflows you can build in Port today and how they solve major productivity challenges. ## Top 10 developer productivity tools DevFeed: [Top 10 developer productivity tools]() Original publisher: [Read original article]() Author: Jenna Danoy Published: 2026-07-30T11:29:15Z Content type: article Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [developer-productivity](), [Developer experience](), [DevOps](), [internal developer portal](), [Software Engineering]() Tags: [cognitive-load](), [collaboration](), [developer-productivity](), [devops](), [efficiency]() ### AI overview This article presents a list of developer productivity tools intended to help engineering teams ship faster, reduce friction, and improve collaboration. It discusses tool sprawl, developer experience, cognitive load, software engineering intelligence, developer surveys, and governance or task management. ### Source excerpt Explore developer productivity tools that help teams ship faster, reduce friction, and improve collaboration across engineering workflows. ## Developer productivity insights platforms (DPIP) measure dashboards. Your DevEx problem is bigger Than that. DevFeed: [Developer productivity insights platforms (DPIP) measure dashboards. Your DevEx problem is bigger Than that.]() Original publisher: [Read original article]() Author: Zohar Einy Published: 2026-07-30T11:28:55Z Content type: opinion Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [code productivity](), [devex](), [dashboards](), [developer-productivity](), [Artificial Intelligence](), [DevOps](), [Platform Engineering](), [CI/CD](), [Large Language Model](), [Optimization](), [migration]() Tags: [agentic](), [ai](), [ci-cd](), [dashboards](), [developer-productivity](), [devex](), [devops](), [llm](), [measurements](), [metrics](), [migration](), [optimization](), [platform-engineering]() ### AI overview This developer article argues that Developer Productivity Insight Platforms (DPIP) should extend beyond measuring engineering time, resources, effectiveness, and delivery progress. It says dashboards and metrics are insufficient without workflows and self-service actions that help developers resolve identified problems. The article also highlights platform convergence, CI/CD integrations, agentic solutions, LLM support, resource optimization, and data migration, arguing that enterprise engineering needs an end-to-end platform connecting insight to action. ### Source excerpt Gartner defines DPIP as solutions that provide software engineering leaders with data-driven insights into their teams' use of time, resources, operational effectiveness and progress on deliverables. ## Platform Product Management: AI-enabled vs. AI-native capability stacks DevFeed: [Platform Product Management: AI-enabled vs. AI-native capability stacks]() Original publisher: [Read original article]() Author: Poojitha Marreddy Published: 2026-07-23T05:40:01Z Content type: article Language: en Sources: [Platform Engineering Blog]() Topics: [Product Management](), [code productivity](), [developer-productivity](), [Artificial Intelligence](), [Infrastructure as code](), [Terraform](), [DevSecOps](), [GitHub](), [Jenkins](), [Kubernetes]() Tags: [agents](), [ai](), [code](), [cognitive-load](), [configuration](), [developer](), [developer-productivity](), [devsecops](), [github](), [iac](), [jenkins](), [kubernetes](), [management](), [platform](), [product](), [productivity](), [terraform]() ### AI overview This article presents platform product management as a way to reduce developer cognitive load and improve delivery velocity. It contrasts AI-enabled capability stacks, which use AI to assist developers, with AI-native stacks, which run AI workloads; both depend on an internal developer platform but require different investments, governance, and success metrics. The article introduces the double diamond framework for discovering, defining, developing, and delivering platform capabilities. ### Source excerpt Platform PM framework: Shift from tool standardization to product thinking. Learn to build AI-enabled vs AI-native stacks to boost developer productivity ## The platform engineering reality check: Is your initiative on track? DevFeed: [The platform engineering reality check: Is your initiative on track?]() Original publisher: [Read original article]() Author: Mallory Haigh Published: 2026-07-23T05:40:01Z Content type: article Language: en Sources: [Platform Engineering Blog]() Topics: [Platform Engineering](), [code productivity](), [developer-productivity]() Tags: [developer](), [developers](), [engineering](), [executive](), [measurement](), [metrics](), [platform](), [platform-engineering](), [productivity](), [report]() ### AI overview This article presents a reality check for platform engineering initiatives, emphasizing measurement, return on investment, adoption, culture, and maturity. It reports that many platform teams either do not measure success or cannot demonstrate improvement, and recommends using metrics such as DORA, time to market, or SPACE. It also warns that funded teams may remain reactive without sufficient authority or strategic empowerment. ### Source excerpt Assess if your platform engineering initiative is on track. Learn about measurement, investment, adoption, culture, and maturity benchmarks for success. ## Samsung Electronics brings ChatGPT and Codex to employees DevFeed: [Samsung Electronics brings ChatGPT and Codex to employees]() Original publisher: [Read original article]() Published: 2026-06-21T23:00:00Z Content type: news Language: en Sources: [OpenAI News]() Topics: [ChatGPT](), [codex](), [samsung](), [OpenAI](), [Artificial Intelligence](), [AI Strategy](), [code productivity](), [developer-productivity](), [GitHub](), [coding]() Tags: [ai](), [ai-adoption](), [chatgpt](), [codex](), [company](), [developer-productivity](), [enterprise](), [openai](), [platform](), [productivity](), [samsung](), [security](), [software-development]() ### AI overview Samsung Electronics is deploying ChatGPT Enterprise and Codex to employees in Korea and across its Device eXperience division worldwide. The rollout covers technical and non-technical work, including software development, manufacturing, marketing, product development, information analysis, document drafting, and workflow automation. ### Source excerpt Samsung Electronics deploys ChatGPT Enterprise and Codex to employees worldwide, marking one of OpenAI's largest enterprise AI rollouts. ## Top 5 internal developer platform tools DevFeed: [Top 5 internal developer platform tools]() Original publisher: [Read original article]() Author: Netta Borowitsh Published: 2026-05-04T10:34:44Z Content type: article Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [internal developer platform](), [Platform Engineering](), [DevOps](), [developer-productivity](), [sdlc](), [Tooling]() Tags: [cncf](), [developer-experience](), [developer-productivity](), [devops](), [idp](), [internal-developer-platform](), [platform-engineering](), [sdlc](), [tooling]() ### AI overview The article introduces internal developer platforms as product-like systems that provide developer self-service through golden paths, reduce cognitive load, and abstract infrastructure and tooling complexity. It explains how platform engineering teams can build these platforms iteratively around common developer needs and assess their maturity using the CNCF platform engineering maturity model. ### Source excerpt Explore the top 5 internal developer platform tools to improve productivity, visibility, and developer self-service capabilities. ## CockroachDB Expands AI Assistance with Cloud Console Help and a Docs MCP Server DevFeed: [CockroachDB Expands AI Assistance with Cloud Console Help and a Docs MCP Server]() Original publisher: [Read original article]() Author: Kiki Carter Published: 2026-02-05T00:00:00Z Content type: article Language: en Sources: [Cockroach Labs]() Topics: [CockroachDB](), [Artificial Intelligence](), [coding assistant](), [MCP Server](), [Cloud](), [Documentation](), [developer-productivity]() Tags: [ai](), [ai-coding](), [cloud](), [cockroachdb](), [developer-productivity](), [documentation](), [mcp-server]() ### AI overview CockroachDB describes AI assistance across its user journey, including AskAI for learning and implementation questions. It adds AskAI to the CockroachDB Cloud Console and introduces a Docs MCP Server for coding assistance, with responses that can point users to CockroachDB documentation. ### Source excerpt CockroachDB users don't all show up in the same place or follow the same path. Some are just starting to evaluate distributed SQL. Others are deep in implementation details, or they may already be operating cloud-based clusters. A growing number are building day-to-day with an AI coding assistant open alongside their editor. ## How Booking.com Uses Backstage to Support Distributed Ownership in Its Engineering Portal DevFeed: [How Booking.com Uses Backstage to Support Distributed Ownership in Its Engineering Portal]() Original publisher: [Read original article]() Author: Matthew Pennell Published: 2026-02-02T16:26:13Z Content type: opinion Language: en Sources: [Booking.com Development - Medium]() Topics: [Backstage](), [developer-productivity](), [Tooling](), [ui]() Tags: [backstage](), [company](), [developer-productivity](), [platform](), [software-development](), [tooling](), [user-interface](), [ux-design]() ### AI overview Booking.com describes adopting Backstage for its internal Engineering Portal, where autonomous teams own different features and tooling. The article explains that Backstage's plugin-based architecture provided the flexibility needed to support the company's complex engineering environment while addressing interface inconsistency and developer friction. ### Source excerpt The necessity of imperfection: Designing for distributed ownership in Backstage Imagine an internal engineering platform -- tooling that is accessed by thousands of developers every day -- where every new feature, every piece of critical functionality, is designed, built and maintained by a different, autonomous team. For years, that was the reality of our internal tooling at Booking.com; a productive, necessary chaos. Engineers had the freedom to build and deploy exactly what they needed, but the cumulative effect was a user interface that was about as far from being a unified ecosystem as it was possible to get. The resulting friction, cognitive load, and sheer inconsistency was a silent, daily tax on developer productivity. Booking.com, like any established tech company, has a sprawling collection of internal tools. Some are commonplace across the industry, such as Google Drive, Jira, Workday, Zoom, Figma and Miro. Others are so specific to the way that we work that building them ourselves has always been the most practical option. And somewhere in the middle are systems we could build, but that would be better served by a framework which handles the fundamentals and lets us focus on the details unique to our environment. Our Engineering Portal is one of those systems: essential for governance, ownership, productivity and visibility, yet also something that thousands of engineers should be able to use easily without having to think too hard about it. There are plenty of off-the-shelf developer portals available. Port, Cycloid, Configure8, Rely and OpsLevel among others all offer their own take on managing engineering ecosystems and come with slick interfaces, integrations and (of course, nowadays) various forms of AI assistance. However, in such a mature and complex environment as Booking (approaching 30 years in business at the time of writing), the deciding factor wasn't the surface polish -- it was flexibility. After all that time layering, modernising and occasi ## Accelerating Platform Adoption with Developer Trust DevFeed: [Accelerating Platform Adoption with Developer Trust]() Original publisher: [Read original article]() Published: 2025-11-06T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [Developer Platform](), [code productivity](), [cloud-infrastructure](), [developer-productivity](), [software-development]() Tags: [chainguard-adoption-story](), [chainguard-containers](), [chainguard-images](), [chainguard-libraries](), [cloud-native](), [container](), [container-images](), [developer](), [golden-images](), [governance](), [internal-developer-platform](), [platform](), [site-reliability](), [velocity]() ### AI overview The article argues that internal development platforms need developer trust to achieve adoption. Platform teams should provide secure, standardized, and customizable paved paths that support diverse developer needs, including different programming languages and versions. It highlights the limitations of one-size-fits-most golden container images and the importance of balancing flexibility, governance, productivity, engineering velocity, and operational reliability. ### Source excerpt Chainguard helps Platform teams drive adoption with zero-CVE, customizable container images that make internal development platforms secure, fast, and trusted. ## Overclocking dbt: Discord's Custom Solution in Processing Petabytes of Data DevFeed: [Overclocking dbt: Discord's Custom Solution in Processing Petabytes of Data]() Original publisher: [Read original article]() Author: Chris Dong Published: 2025-04-09T00:00:00Z Content type: article Language: en Sources: [Discord Blog]() Topics: [data](), [developer-productivity](), [data observability](), [DataOps](), [Testing](), [SQL](), [Open Source](), [Software Engineering]() Tags: [analytics](), [blog-post](), [code](), [data](), [developer](), [developer-productivity](), [open-source](), [performance](), [productivity](), [quality](), [software-engineering](), [sql](), [testing](), [tool]() ### AI overview Discord describes scaling dbt to process petabytes of warehouse data while supporting more than 100 developers and over 2,500 models. It explains how custom extensions addressed long recompilation times, inefficient incremental processing, conflicting test tables, breaking changes, and complex calculations, improving performance, developer productivity, and data quality. ### Source excerpt Explore how Discord supercharged dbt with a tailored solution designed for performance, developer productivity, and data quality. ## Increase Engineering Productivity by 50% Through Focus and Flow DevFeed: [Increase Engineering Productivity by 50% Through Focus and Flow]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2024-06-01T05:00:00Z Content type: opinion Language: en Sources: [Tobias Mende]() Topics: [developer-productivity](), [code productivity](), [pair\_programming](), [context](), [meetings](), [Documentation](), [real-time]() Tags: [collaboration](), [collaboration-communication-continuous-deployment-developer-experience-developer-productivity-e](), [documentation](), [engineering-productivity](), [flow](), [focus](), [pair-programming](), [real-time]() ### AI overview This article discusses how focus and flow affect developer productivity and presents practical organizational ideas for improving them. It emphasizes collaboration, team or pair programming, reducing distractions and context switching, real-time reviews, and useful documentation. ### Source excerpt Increase Engineering Productivity by 50% Through Focus and Flow Creating an environment where developers can maintain focus and achieve flow can lead to a 50% increase in productivity, as research suggests. But how do we create such an environment? ## Snyk AppRisk Pro: A holistic approach to application risk management DevFeed: [Snyk AppRisk Pro: A holistic approach to application risk management]() Original publisher: [Read original article]() Author: Daniel Berman Published: 2024-05-01T12:55:00Z Content type: release Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [snyk](), [snyk-apprisk](), [Application Security](), [Security](), [Business Security](), [data analytics](), [Architecture & Design](), [developer-productivity](), [Development](), [dynatrace](), [Backstage](), [API]() Tags: [acquisition](), [analytics](), [api](), [application-security](), [aspm](), [backstage](), [blog](), [convert-paid](), [developer-productivity](), [development](), [devops](), [dynatrace](), [enablement](), [executive](), [gitguardian](), [measurement](), [observability](), [pmm](), [reporting](), [security](), [snyk](), [snyk-apprisk]() ### AI overview Snyk announces Snyk AppRisk Pro, an application security posture management offering for managing and scaling application security programs. It combines application visibility and discovery, security coverage management, and risk-based prioritization with runtime intelligence, developer-context integrations, extended security coverage, and application analytics for tracking program performance and risk. ### Source excerpt Find out how Snyk AppRisk Pro, our application security posture management (ASPM) solution, is designed to empower your application risk management programs. ## How CVEs slow down developer productivity DevFeed: [How CVEs slow down developer productivity]() Original publisher: [Read original article]() Published: 2024-04-18T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [developer-productivity](), [Vulnerabilities](), [code productivity](), [container-security](), [Containers](), [supply-chain-security]() Tags: [chainguard-images](), [common-exposures-and-vulnerabilities](), [container-security](), [cve](), [developer](), [developer-productivity](), [diy](), [false-positives](), [pain-of-cve](), [security](), [security-best-practices](), [software-supply-chain-security](), [testing](), [vulnerabilities]() ### AI overview The article explains how CVE management consumes developer time and harms productivity. It describes false positives, confusing vulnerability information, and regression-testing and dependency challenges, with particular attention to companies that build or operate containers. ### Source excerpt Tired of wasting time on CVEs? Learn how to streamline container security, boost developer productivity, and reduce risk. Data-backed insights inside. ## Tracking developer build times to decide if the M3 MacBook is worth upgrading DevFeed: [Tracking developer build times to decide if the M3 MacBook is worth upgrading]() Original publisher: [Read original article]() Author: Lawrence Jones Published: 2023-12-19T14:00:00Z Content type: article Language: en Sources: [The incident.io Blog]() Topics: [build times](), [Go Language](), [telemetry](), [Hardware](), [developer-productivity]() Tags: [build-times](), [building](), [code](), [compiler](), [developer](), [developer-productivity](), [developers](), [development](), [github](), [go](), [hardware](), [incident](), [incident-channel](), [incident-management](), [incident-response](), [local](), [outage](), [performance](), [post-mortem](), [slack-incident](), [speed](), [telemetry](), [upgrade]() ### AI overview The article describes an experiment to determine whether upgrading developers from M1 or M2 MacBooks to M3 MacBook Pros would improve productivity enough to justify the cost. The team used Go compilation speed as the key performance metric and built a custom hot-reloader to collect build-time telemetry. ### Source excerpt When our CTO said "I'll upgrade your MacBook if you can prove it's worthwhile", we embarked on a journey including (re)building a Go hot-reloader, instrumenting developer builds, analyzing compiler performance, and feeding an AI model the data until we had an answer. ## Selling DevEx Initiatives in Purpose vs. Profit-oriented Companies DevFeed: [Selling DevEx Initiatives in Purpose vs. Profit-oriented Companies]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2023-10-21T04:00:00Z Content type: opinion Language: en Sources: [Tobias Mende]() Topics: [Developer experience](), [developer-productivity](), [Development]() Tags: [culture-developer-experience-developer-productivity-engineering-excellence-organizational-design](), [developer-experience](), [developer-productivity](), [development](), [devex](), [organizations]() ### AI overview This opinion article discusses how technical leaders can communicate and advocate for Developer Experience initiatives by aligning them with organizational priorities. It contrasts purpose-oriented and profit-oriented contexts and relates DevEx to developer productivity and effectiveness. ### Source excerpt Selling DevEx Initiatives in Purpose vs. Profit-oriented Companies For years, a conversation has been ongoing on naming in the DevEx community (and within myself). Of course. Naming is hard, and why shouldn't it be any different for this domain? ## How Productivity Metrics Can Undermine Software Development Teams DevFeed: [How Productivity Metrics Can Undermine Software Development Teams]() Original publisher: [Read original article]() Author: Richard Donovan Published: 2023-10-15T20:40:16Z Content type: opinion Language: en Sources: [The Modern Software Developer]() Topics: [developer-productivity](), [Development](), [test-coverage]() Tags: [developer-productivity](), [metrics](), [test-coverage]() ### AI overview The article argues that conventional software-development productivity metrics can be harmful when turned into targets, particularly when used to assess individual developers. It says such measures can encourage gaming and fail to measure the outcomes leaders intend to assess. ### Source excerpt Welcome back to The Modern Software Developer. ## Automating Bluetooth Profile switching thanks to Copilot Chat DevFeed: [Automating Bluetooth Profile switching thanks to Copilot Chat]() Original publisher: [Read original article]() Author: Sanskar Agrawal Published: 2023-10-09T20:20:18Z Content type: opinion Language: en Sources: [Sanskar's Stuff]() Topics: [Bluetooth](), [GitHub Copilot](), [Linux](), [AI Chat](), [Command-line interface](), [developer-productivity](), [Shell]() Tags: [bluetooth](), [chatgpt](), [coding](), [command-line](), [copilot](), [github-copilot](), [linux](), [productivity]() ### AI overview The author describes using GitHub Copilot Chat to create a shell script that switches Bluetooth headset profiles on EndeavourOS. The script provides a keyboard-accessible workaround for a microphone problem, although it took about 30 minutes of back-and-forth to reach the correct commands. ### Source excerpt A task I completed that I wouldn't have (or at least, not without putting several hours into it) without Generative AI: I use an Arch-based Linux distro called Endeavour OS. It's a great OS, but lately, I've been having this issue where my computer w... ## Why We Need to Stop Measuring (Developer) Productivity -- Part 2 DevFeed: [Why We Need to Stop Measuring (Developer) Productivity -- Part 2]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2023-09-23T04:00:00Z Content type: opinion Language: en Sources: [Tobias Mende]() Topics: [developer-productivity](), [Software Engineering](), [dora metrics](), [lead time]() Tags: [culture-developer-productivity-engineering-leadership-leadership-metrics-engineering-excellence](), [developer](), [developer-productivity](), [dora-metrics](), [metrics](), [productivity](), [software-engineering]() ### AI overview This second part of an article argues that developer productivity cannot be measured directly because software output and business value are difficult to measure and may emerge with delays. It says teams can use metrics such as DORA Metrics as proxies for understanding engineering performance, but these metrics should not be used by management to measure individual or team productivity. ### Source excerpt Why We Need to Stop Measuring (Developer) Productivity -- Part 2 This is part two of my article on measuring developer productivity. In part one, we discussed the dangers of measuring productivity in general and why the need for productivity metrics for management and leadership is based on flawed assumptions. ## Why We Need to Stop Measuring (Developer) Productivity -- Part 1 DevFeed: [Why We Need to Stop Measuring (Developer) Productivity -- Part 1]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2023-09-16T04:00:00Z Content type: opinion Language: en Sources: [Tobias Mende]() Topics: [code productivity](), [developer-productivity]() Tags: [collaboration](), [command-and-control](), [communication](), [culture-developer-productivity-leadership-metrics-engineering-excellence](), [developer](), [developer-productivity](), [leadership](), [measuring](), [productivity](), [trust]() ### AI overview This opinion argues that productivity metrics are difficult and potentially harmful when used as targets, especially under command-and-control leadership. It advocates leadership based more on trust, communication, and collaboration, and introduces concerns about measuring sales and engineering productivity. ### Source excerpt Why We Need to Stop Measuring (Developer) Productivity -- Part 1 Leaders are obsessed with productivity metrics. This is at least true for leaders who learned to lead in the last century. The ones that follow a command-and-control or carrots-and-sticks leadership approach. They need to measure each department individually to make the right decisions top-down. ## Measuring Developer Experience - A Balanced Approach DevFeed: [Measuring Developer Experience - A Balanced Approach]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2023-08-05T06:00:00Z Content type: tutorial Language: en Sources: [Tobias Mende]() Topics: [Developer experience](), [code productivity](), [developer-productivity](), [retrospectives]() Tags: [culture-developer-experience-developer-productivity-metrics-engineering-excellence](), [developer-experience](), [measuring](), [metrics](), [retrospectives](), [survey]() ### AI overview The article presents a balanced way to measure developer experience by combining quantitative and qualitative methods. It discusses surveys, eNPS, retrospectives, developer productivity metrics, turnover rates, and feedback channels, while noting that individual measures have limitations. ### Source excerpt Measuring Developer Experience - A Balanced Approach Developer Experience is one of the most essential factors for high-performing teams and organizations. Thus, the obvious question is how to measure, assess and understand the status quo within your organization and team. ## Deep Work and Collaboration in Platform- and Enabling-Teams DevFeed: [Deep Work and Collaboration in Platform- and Enabling-Teams]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2023-04-01T06:00:00Z Content type: opinion Language: en Sources: [Tobias Mende]() Topics: [Developer experience](), [developer-productivity](), [developer tooling](), [CI/CD](), [Testing](), [Monitoring]() Tags: [article](), [collaboration](), [collaboration-culture-deep-work-employee-happiness-practices-team-topologies-developer-product](), [communication](), [continuous-delivery](), [developer-experience](), [developer-productivity](), [developer-tooling]() ### AI overview An opinion article explains how a developer experience team balanced deep work with the responsiveness required of a platform- and enabling-team. It describes collaboration, developer tooling, delivery pipelines, architecture, infrastructure, continuous delivery, and support for building, testing, deploying, running, and monitoring software, then introduces six mechanisms for protecting focus while handling requests. ### Source excerpt Deep Work and Collaboration in Platform- and Enabling-Teams This is the fourth and last articles of my series about deep work. The first article was about the value of deep work for peak performance. The second article was about seven tips for more deep work for individuals. The third articles was about deep work for teams. [Next page]()