Skip to main content

The Power of Deep Code Insights

Jina Na
AppDynamics

The rise of technologies like cloud computing and automated delivery pipelines has enabled teams to deliver software at breakneck speed. In fact, top tech companies deploy software hundreds, even thousands of times per day, raising the bar for digital services. To stay competitive, organizations in every industry must match the pace of innovation set by these digital-native companies.

However, it's challenging to maintain heterogeneous applications and ensure that service is not only available, but also delighting users and driving business outcomes. From the front-end experience to back-end architecture, a web of third-party services, legacy data centers and a distributed, multi cloud infrastructure are supporting the application.

If you're unable to effectively manage these complex application environments, your business is impacted — an outage leads to poor user experience which leads to lost business and impact to your organizational productivity and resources. Take for instance what recently happened with the Iowa caucus app. Coding issues led to significant delays in counting and reporting important primary results, which led other states, such as Nevada, to pull two previously developed apps for their own primary elections, losing out on tens of thousands of dollars.

This example shows that while deployment velocity has increased exponentially, traditional approaches to troubleshooting fall short when it comes to equipping developers (and IT teams) with enough information to pinpoint the root cause of application code issues.

In fact, according to Stripe Research, developers spend roughly 17.3 hours each week debugging, refactoring and modifying bad code — valuable time that could be spent writing more code, shipping better products and innovating. The bottom line? Nearly $300B (US) in lost developer productivity every year.

What happened in Iowa is just one example of how developers are often blamed for code level issues, issues that with the right level of insight could reveal what's causing a bug in production before impacting the digital experience for customers.

So what's the solution and what opportunities would developers suddenly benefit from if they spent more time writing code and less time debugging?

The Aha Moments — What Code Level Insights Bring to Life

The job of a developer is never ending given business priorities and product roadmaps. For those battling issues in monolithic environments or in highly distributed, microservices-based applications, code level insights greatly improve software delivery efficiency by enabling developers to spend less time debugging and more time delivering world-class software.

Specifically, today, once developers ship their code, access to the application and data is restricted. This means that most dev teams are forced to rely on time and resource intensive logging to collect the critical data needed to understand the cause of any performance impact.

Instead of this time intensive, often manual process, by leveraging code-level insights, developers are able to capture critical data and context, on-demand. This level of insight, means, developers have access to data and can collect the necessary information when they need to in order to pinpoint what's causing an issue. As a result, developers have witnessed a decrease in MTTR, improving the overall IT efficiency of their teams, a tighter alignment between Operations and Development teams and according to recent studies, a 25 percent improvement in developer productivity, freeing up valuable time to focus on releasing new features.

Armed with time back, developers can focus on building market-differentiating products that drive user experience, customer satisfaction, and business priorities. This is especially key for organizations competing with younger, digital-native companies.

Jina Na is Associate Product Marketing Manager at AppDynamics

The Latest

Many organizations describe AI as strategic, but they do not manage it strategically. When AI plans are disconnected from strategy, detached from organizational learning, and protected from serious assumptions testing, the problem is no longer technical immaturity; it is a failure of management discipline ... Executives too often tell organizations to "use AI" before they define what AI is supposed to change. The problem deepens in organizations where strategy isn't well articulated in the first place ...

Across the enterprise technology landscape, a quiet crisis is playing out. Organizations have run hundreds, sometimes thousands, of generative AI pilots. Leadership has celebrated the proof of concept (POCs) ... Industry experience points to a sobering reality: only 5-10% of AI POCs that progress to the pilot stage successfully reach scaled production. The remaining 90% fail because the enterprise environment around them was never ready to absorb them, not the AI models ...

Today's modern systems are not what they once were. Organizations now rely on distributed systems, event-driven workflows, hybrid and multi-cloud environments and continuous delivery pipelines. While each adds flexibility, it also introduces new, often invisible failures. Development speed is no longer the primary bottleneck of innovation. Reliability is ...

Seeing is believing, or in this case, seeing is understanding, according to New Relic's 2025 Observability Forecast for Retail and eCommerce report. Retailers who want to provide exceptional customer experiences while improving IT operations efficiency are leaning on observability ... Here are five key takeaways from the report ...

Technology leaders across the federal landscape are facing, and will continue to face, an uphill battle when it comes to fortifying their digital environments against hostile and persistent threat actors. On one hand, they are being asked to push digital transformation ... On the other hand, they are facing the fiscal uncertainty of continuing resolutions (CR) and government shutdowns looming near and far. In the face of these challenges, CIOs, CTOs, and CISOs must figure out how to modernize legacy systems and infrastructure while doing more with less and still defending against external and internal threats ...

Reliability is no longer proven by uptime alone, according to the The SRE Report 2026 from LogicMonitor. In the AI era, it is experienced through speed, consistency, and user trust, and increasingly judged by business impact. As digital services grow more complex and AI systems move into production, traditional monitoring approaches are struggling to keep pace, increasing the need for AI-first observability that spans applications, infrastructure, and the Internet ...

If AI is the engine of a modern organization, then data engineering is the road system beneath it. You can build the most powerful engine in the world, but without paved roads, traffic signals, and bridges that can support its weight, it will stall. In many enterprises, the engine is ready. The roads are not ...

In the world of digital-first business, there is no tolerance for service outages. Businesses know that outages are the quickest way to lose money and customers. For smaller organizations, unplanned downtime could even force the business to close ... A new study from PagerDuty, The State of AI-First Operations, reveals that companies actively incorporating AI into operations now view operational resilience as a growth driver rather than a cost center. But how are they achieving it? ...

In live financial environments, capital markets software cannot pause for rebuilds. New capabilities are introduced as stacked technology layers to meet evolving demands while systems remain active, data keeps moving, and controls stay intact. AI is no exception, and its opportunities are significant: accelerated decision cycles, compressed manual workflows, and more effective operations across complex environments. The constraint isn't the models themselves, but the architectural environments they enter ...

Like most digital transformation shifts, organizations often prioritize productivity and leave security and observability to keep pace. This usually translates to both the mass implementation of new technology and fragmented monitoring and observability (M&O) tooling. In the era of AI and varied cloud architecture, a disparate observability function can be dangerous. IT teams will lack a complete picture of their IT environment, making it harder to diagnose issues while slowing down mean time to resolve (MTTR). In fact, according to recent data from the SolarWinds State of Monitoring & Observability Report, 77% of IT personnel said the lack of visibility across their on-prem and cloud architecture was an issue ...

The Power of Deep Code Insights

Jina Na
AppDynamics

The rise of technologies like cloud computing and automated delivery pipelines has enabled teams to deliver software at breakneck speed. In fact, top tech companies deploy software hundreds, even thousands of times per day, raising the bar for digital services. To stay competitive, organizations in every industry must match the pace of innovation set by these digital-native companies.

However, it's challenging to maintain heterogeneous applications and ensure that service is not only available, but also delighting users and driving business outcomes. From the front-end experience to back-end architecture, a web of third-party services, legacy data centers and a distributed, multi cloud infrastructure are supporting the application.

If you're unable to effectively manage these complex application environments, your business is impacted — an outage leads to poor user experience which leads to lost business and impact to your organizational productivity and resources. Take for instance what recently happened with the Iowa caucus app. Coding issues led to significant delays in counting and reporting important primary results, which led other states, such as Nevada, to pull two previously developed apps for their own primary elections, losing out on tens of thousands of dollars.

This example shows that while deployment velocity has increased exponentially, traditional approaches to troubleshooting fall short when it comes to equipping developers (and IT teams) with enough information to pinpoint the root cause of application code issues.

In fact, according to Stripe Research, developers spend roughly 17.3 hours each week debugging, refactoring and modifying bad code — valuable time that could be spent writing more code, shipping better products and innovating. The bottom line? Nearly $300B (US) in lost developer productivity every year.

What happened in Iowa is just one example of how developers are often blamed for code level issues, issues that with the right level of insight could reveal what's causing a bug in production before impacting the digital experience for customers.

So what's the solution and what opportunities would developers suddenly benefit from if they spent more time writing code and less time debugging?

The Aha Moments — What Code Level Insights Bring to Life

The job of a developer is never ending given business priorities and product roadmaps. For those battling issues in monolithic environments or in highly distributed, microservices-based applications, code level insights greatly improve software delivery efficiency by enabling developers to spend less time debugging and more time delivering world-class software.

Specifically, today, once developers ship their code, access to the application and data is restricted. This means that most dev teams are forced to rely on time and resource intensive logging to collect the critical data needed to understand the cause of any performance impact.

Instead of this time intensive, often manual process, by leveraging code-level insights, developers are able to capture critical data and context, on-demand. This level of insight, means, developers have access to data and can collect the necessary information when they need to in order to pinpoint what's causing an issue. As a result, developers have witnessed a decrease in MTTR, improving the overall IT efficiency of their teams, a tighter alignment between Operations and Development teams and according to recent studies, a 25 percent improvement in developer productivity, freeing up valuable time to focus on releasing new features.

Armed with time back, developers can focus on building market-differentiating products that drive user experience, customer satisfaction, and business priorities. This is especially key for organizations competing with younger, digital-native companies.

Jina Na is Associate Product Marketing Manager at AppDynamics

The Latest

Many organizations describe AI as strategic, but they do not manage it strategically. When AI plans are disconnected from strategy, detached from organizational learning, and protected from serious assumptions testing, the problem is no longer technical immaturity; it is a failure of management discipline ... Executives too often tell organizations to "use AI" before they define what AI is supposed to change. The problem deepens in organizations where strategy isn't well articulated in the first place ...

Across the enterprise technology landscape, a quiet crisis is playing out. Organizations have run hundreds, sometimes thousands, of generative AI pilots. Leadership has celebrated the proof of concept (POCs) ... Industry experience points to a sobering reality: only 5-10% of AI POCs that progress to the pilot stage successfully reach scaled production. The remaining 90% fail because the enterprise environment around them was never ready to absorb them, not the AI models ...

Today's modern systems are not what they once were. Organizations now rely on distributed systems, event-driven workflows, hybrid and multi-cloud environments and continuous delivery pipelines. While each adds flexibility, it also introduces new, often invisible failures. Development speed is no longer the primary bottleneck of innovation. Reliability is ...

Seeing is believing, or in this case, seeing is understanding, according to New Relic's 2025 Observability Forecast for Retail and eCommerce report. Retailers who want to provide exceptional customer experiences while improving IT operations efficiency are leaning on observability ... Here are five key takeaways from the report ...

Technology leaders across the federal landscape are facing, and will continue to face, an uphill battle when it comes to fortifying their digital environments against hostile and persistent threat actors. On one hand, they are being asked to push digital transformation ... On the other hand, they are facing the fiscal uncertainty of continuing resolutions (CR) and government shutdowns looming near and far. In the face of these challenges, CIOs, CTOs, and CISOs must figure out how to modernize legacy systems and infrastructure while doing more with less and still defending against external and internal threats ...

Reliability is no longer proven by uptime alone, according to the The SRE Report 2026 from LogicMonitor. In the AI era, it is experienced through speed, consistency, and user trust, and increasingly judged by business impact. As digital services grow more complex and AI systems move into production, traditional monitoring approaches are struggling to keep pace, increasing the need for AI-first observability that spans applications, infrastructure, and the Internet ...

If AI is the engine of a modern organization, then data engineering is the road system beneath it. You can build the most powerful engine in the world, but without paved roads, traffic signals, and bridges that can support its weight, it will stall. In many enterprises, the engine is ready. The roads are not ...

In the world of digital-first business, there is no tolerance for service outages. Businesses know that outages are the quickest way to lose money and customers. For smaller organizations, unplanned downtime could even force the business to close ... A new study from PagerDuty, The State of AI-First Operations, reveals that companies actively incorporating AI into operations now view operational resilience as a growth driver rather than a cost center. But how are they achieving it? ...

In live financial environments, capital markets software cannot pause for rebuilds. New capabilities are introduced as stacked technology layers to meet evolving demands while systems remain active, data keeps moving, and controls stay intact. AI is no exception, and its opportunities are significant: accelerated decision cycles, compressed manual workflows, and more effective operations across complex environments. The constraint isn't the models themselves, but the architectural environments they enter ...

Like most digital transformation shifts, organizations often prioritize productivity and leave security and observability to keep pace. This usually translates to both the mass implementation of new technology and fragmented monitoring and observability (M&O) tooling. In the era of AI and varied cloud architecture, a disparate observability function can be dangerous. IT teams will lack a complete picture of their IT environment, making it harder to diagnose issues while slowing down mean time to resolve (MTTR). In fact, according to recent data from the SolarWinds State of Monitoring & Observability Report, 77% of IT personnel said the lack of visibility across their on-prem and cloud architecture was an issue ...