Science – Stacking Trades

The Developer Experience Economy

Stacking Trades — Wed, 10 Dec 2025 21:32:35 +0000

The first sign that something had changed was not a new programming language or a popular open source library. It was a slide in a board meeting. Alongside revenue, margins, and churn, a fourth chart showed up: deployment frequency and DevEx score. The message was clear. How developers felt about their tools had become a business metric.

For years, companies treated internal developer experience as a kind of housekeeping, important but rarely urgent. In 2025, it has become a competitive weapon. Research from Google and independent DevEx labs now treats productivity as a function of speed, ease, and quality, measured through a mix of telemetry and direct surveys. Gartner tracks a growing market for “internal developer portals,” and consulting firms sell playbooks for unlocking revenue growth through happier engineers. What used to be tickets in a backlog is now a line in the strategy memo.

When productivity became a product

The shift starts with a simple arithmetic problem. In the 2024 Stack Overflow Developer Survey, a majority of professional developers reported spending more than thirty minutes every day just searching for answers to work problems. That is time spent in documentation mazes, chat histories, and half-remembered Confluence pages rather than in the codebase.

At the same time, the average toolchain has grown more complex. A developer working on a single feature might interact with the source repository, a feature flag service, a build pipeline, a cloud console, an observability platform, and several chat channels before the change reaches production. Each step adds friction. Each missing script or unclear error message adds a small cost.

The result is that developer experience itself has started to look like a product surface. Companies now build internal platforms with the same care they once reserved for customer facing apps: user research, design reviews, roadmaps, and service-level objectives tailored to engineers.

The rise of the internal developer platform

Platform engineering emerged as a response to this sprawl. Rather than ask every team to stitch together its own path to production, organizations began building centralized “golden paths” that abstract away infrastructure and policy decisions. The idea is not new, but the tooling is.

Open source frameworks like Backstage, created at Spotify and donated to the Cloud Native Computing Foundation, turned the concept of an internal portal into reusable software. Backstage catalogs services, pipelines, and documentation in one place, so engineers can discover what exists and scaffold new projects with consistent templates. A growing ecosystem of SaaS platforms now wraps these ideas in managed offerings, promising faster onboarding and reliable standards without the pain of building everything in house.

Analysts have started to quantify the trend. Gartner defines internal developer portals as the front door to reusable components, tools, and knowledge, and projects that by 2028 most organizations with platform engineering teams will offer one, up from about sixty percent in 2025. What was once a niche initiative now looks like the default infrastructure pattern for serious software companies.

“Developer experience used to be what was left over after the tools were chosen. Now it is the thing being designed.”

Metrics move into the boardroom

Once internal platforms are in place, leaders want to know if they are effective. This has led to a surge of frameworks that aim to measure not just lines of code or tickets closed; they also focus on the real experience of delivering software.

Google’s productivity researchers have described an approach that blends survey data with system metrics to capture speed and ease in a way that developers recognize as real. Academic and industry teams have published frameworks such as SPACE and DevEx that frame productivity across satisfaction, performance, communication, and flow. More recently, the Core 4 model has tried to unify these ideas into a concise set of outcomes that leadership can track without turning engineers into KPI collectors.

Consultancies and vendors have leaned into the story. Deloitte describes DevEx as a lever for product innovation and operational efficiency. Studies aggregated by DevEx tooling companies suggest that organizations investing in better developer workflows see significantly faster time to market and improved customer acquisition. HashiCorp cites McKinsey research that links strong developer experience to higher operating margins. The numbers are imperfect, but they share a direction. Developer friction is now described not as “annoying” but as a drag on revenue.

AI tools and the new bottleneck

The timing is not accidental. As AI coding assistants spread through the industry, the cost of writing syntax has fallen. According to recent survey data, more than eighty percent of developers now use or plan to use AI tools in their workflows, yet many still spend large chunks of the day hunting for context and debugging almost-right suggestions. The bottleneck has shifted from typing code to orchestrating the environment in which that code runs.

That is where internal platforms matter. An AI tool can write a microservice, but the organization still needs an opinionated way to connect that service to authentication, observability, and deployment. A cluttered CI system or inconsistent staging environment can erase the gains of even the best assistive model.

The companies that benefit most from AI coding tools are often the ones that already invested in clean paths to production. When a scaffolded project comes with batteries included, an AI agent can safely generate more of it. Developer experience becomes the substrate that makes automation trustworthy instead of chaotic.

From perk to strategy

For a long time, improving developer experience was framed as a retention play. The logic was that happier engineers were less likely to leave, and perks like better laptops or cleaner tooling were part of that equation. That lens has not gone away, but it is no longer sufficient.

What is changing is that DevEx is being folded into the core story of how a company competes. Internal portals, standardized workflows, and thoughtful documentation become part of the answer to investor questions about how a business will ship new products faster than rivals. Platform teams are judged not only on internal satisfaction scores but on their contribution to time to market and stability.

The organizations that treat developer experience as an economy of its own are starting to look different inside. Projects spin up with fewer meetings. New hires find their footing in days instead of weeks. AI tools amplify good patterns instead of copying bad ones. The work of building internal tools and platforms is still largely invisible to customers, but its effects are not.

In an era where the external technology frontier is moving quickly, the real differentiator is often what happens inside the walls of a company. The developer experience economy is the quiet infrastructure behind that edge, turning the messy, improvised workflows of the last decade into something more deliberate, measurable, and, increasingly, strategic.

The Invisible Automation Boom

Stacking Trades — Thu, 04 Dec 2025 21:58:40 +0000

The Automation You Cannot See

Across industries, a new form of automation is emerging. It is not the traditional workflow automation that relies on rigid scripts. It is not the public-facing AI that helps employees generate text or draft documents. The new wave consists of systems that function within pipelines, data flows, and coordination layers. These systems complete tasks before they reach human teams, often eliminating steps entirely.

The impact is significant, but it is difficult to measure. This creates a strategic advantage for companies that grasp what is happening below their workflows. It also ties directly to the growing discussion about work that does not show up in metrics, as discussed in a related piece about the hidden layers of productivity.

The Shift From Tasks to Preemptive Resolution

Traditional automation waits for a task to be triggered. Invisible automation removes the need for the task. It detects patterns in data, identifies common failure points, and resolves them before they appear. Tools now exist that can restructure requests, rewrite queries, reformat documents, classify inputs, correct errors, and reroute information without surfacing any of the work to human operators.

Enterprises using these systems are seeing significant drops in queue volume and process delays. In several publicly shared case studies, companies reported reductions of 40 percent or more in routine operational tasks without changing team size. The tasks that were not completed simply never reached employees.

This is where the multiplier begins.

Multi Agent Systems Driving Quiet Efficiency

Many companies are using groups of specialized agents instead of just one model. One agent plans, another retrieves context, another validates, and another enforces compliance rules. Together, they deliver a smooth outcome that feels immediate to the end user.

This setup reflects patterns seen in enterprise software. When subprocesses work together effectively, the outcome is greater than the individual parts. Companies using multi-agent orchestration for ticketing, operations, procurement, and internal knowledge routing are already seeing significant efficiency gains.

These systems are not glamorous. They do not show up in corporate demos. They run in the background, shifting the center of gravity in how work is completed.

“The most powerful automation is the kind that removes work before anyone realizes it was ever needed.”

The Early Movers

The earliest transformation is happening in three areas:

Operations
Automated queue reduction, routing, and triage have become standard in companies deploying intelligent layers. What used to be human escalation is now resolved before assignment.

Enterprise Search and Knowledge Retrieval
Employees spend a considerable amount of time searching for context. Modern retrieval systems reduce this dramatically by structuring inputs and synthesizing results quietly in the background.

Back Office Coordination
Finance, HR, and procurement functions are seeing the earliest signs of large scale invisible automation because their workflows include high volumes of structured tasks that can be intercepted and resolved automatically.

These capabilities are not theoretical. They are already deployed in Fortune 500 environments across logistics, financial services, and large enterprise SaaS.

How This Becomes 10x Efficiency

Efficiency increases in three layers:

1. Work avoidance
Tasks never reach humans because upstream agents solve them.

2. Work compression
What used to take multiple steps now takes one.

3. Work stabilization
Error rates drop, which removes the downstream cleanup that often consumes significant hidden time.

When these three effects compound inside large organizations, the output per employee can rise dramatically. The increase is not incremental. It is structural.

This is why invisible automation will define the next wave of enterprise productivity.

The Strategic Blind Spot for Competitors

Companies still optimizing linear workflows will fall behind. The organizations shifting toward dynamic, multi agent coordination will outperform peers long before the metrics catch up. By the time the numbers reflect the change, the competitive gap will already be wide.

The companies positioned to win the next decade are the ones building automation the metrics cannot yet see.

The New Billion-Dollar Job

Stacking Trades — Wed, 26 Nov 2025 20:49:39 +0000

From Labels to Logic

For years, the main jobs related to AI seemed unexciting. Data labeling, annotation, and tagging were the tasks at hand. Workers drew boxes around objects in images, marked sentiment in text, or checked answers for accuracy. It was repetitive work, but it was important. Models required examples, and people provided them.

That era is still with us, but something new is emerging on top of it. As models gain raw power, the bottleneck is shifting. The hardest problem is no longer teaching systems what a cat looks like. It is teaching them how to decide, how to reason, and how to follow norms that resemble judgment rather than pattern matching.

A new class of work is forming around that challenge. Not labeling. Not simple prompting. Something closer to instructing machine minds in how to think.

The Limits of Raw Scale

Over the last few years, large language models have improved thanks to more parameters, more data, and more computing power. However, even the most advanced systems still show familiar weaknesses. They make up information. They contradict themselves. They have a hard time with multi-step reasoning even when they seem confident. Benchmarks from research groups at Stanford, Berkeley, and other institutions repeatedly highlight gaps in logical consistency, planning, and reliable tool use, despite fast improvements in basic performance.

Scaling has brought us to a new plateau. More data and more GPUs move the ceiling, but they do not change the fact that the models are learning correlations, not principles. Organizations can no longer assume that throwing more tokens at the problem will yield better judgment.

This is where the new job appears.

Teaching Frameworks Instead of Answers

Inside AI labs and companies that deploy models at scale, people are starting to work less as annotators and more as curriculum designers. They do not just identify the correct answer. They define what a clear chain of thought looks like. They specify which tools a model should use and the order in which to use them. They write policies that describe acceptable reasoning paths and those that are unacceptable. They build scaffolds.

Some of this shows up publicly in research on tool using models and reasoning agents. System prompts now include detailed instructions about steps, constraints, and evaluation criteria. Teams design synthetic tasks where models practice decomposing problems rather than jumping to a guess. In more advanced settings, models are trained or fine tuned on traces of their own reasoning, corrected and curated by humans who act less like graders and more like tutors.

The work is not about discrete labels. It is about teaching structure.

The People Behind the Structure

This role does not fit neatly into old titles. It blends parts of machine learning, product thinking, behavioral design, and even a little philosophy.

Some people doing this today have titles like AI researcher, alignment engineer, or reasoning specialist. Others work in product teams but spend much of their time designing evaluation frameworks, system instructions, and feedback loops for agents instead of users. They select which examples to show models. They determine how to phrase objectives. They establish what counts as a solid solution.

They are not writing traditional software, but they are programming behavior. The medium is not code. It is thought.

As more companies rely on AI for complex decisions, this role starts to matter as much as traditional engineering. A model can draft a hundred options. It still takes a human, working at the framework level, to decide what the model should value.

“The most valuable AI work is shifting from giving models answers to teaching them how to think.”

Why This Becomes a Billion-Dollar Job

This is not about salaries alone. It is about leverage.

If one person improves the reasoning framework of a widely used model, that improvement affects every user, every workflow, and every integration. A single insight on how to shape a decision can spread through a system that serves millions. The economic effect of that work far surpasses the effect of adding another app or feature.

Companies are already signaling this. Job postings for roles focused on model behavior, evaluation, and policy design have grown significantly in the last two years. Investors increasingly ask frontier model companies about alignment, reliability, and governance, not only benchmark scores. Enterprises deploying AI in finance, healthcare, and logistics want to know who is responsible for how the models think, not just how fast they run.

The people who can shape that thinking are quietly becoming some of the most leveraged individuals in the stack.

Beyond Prompting

It is tempting to confuse this with prompt engineering. At the beginning of the generative wave, prompt engineering looked like a cheat code. Clever phrasing, special tokens, and long detailed instructions could produce surprisingly good results. But as models and tooling have matured, the focus has shifted.

The new work focuses less on clever lines and more on repeatable systems. It includes test suites, scenario libraries, failure catalogs, and structured rubrics that define good reasoning in a domain. It involves working together with legal, risk, and domain experts. It treats model behavior as something that can be directed using frameworks rather than relying on one-off hacks.

Prompting is to this work what a single lesson is to an entire curriculum.

The Next Layer of Responsibility

There is also a deeper responsibility here. Training models how to think is not neutral. Choices about what counts as valid reasoning, what risks are acceptable, and which trade offs matter are all value laden. They reflect the priorities of the organizations building the systems.

That is why this emerging role is not only technical; it involves governance. The people who create the reasoning frameworks of powerful models will impact decision-making in areas that involve money, health, safety, and information. They are not just building tools; they are shaping the standards of machine judgment.

As AI systems become more autonomous and more embedded in critical processes, this influence will only grow.

A Job That Did Not Exist Ten Years Ago

Ten years ago, there was no such job. There were machine learning engineers, data scientists, and research scientists. There were product managers and architects. There were compliance officers and domain experts.

Today, we are beginning to see something new at their intersection. People whose primary work is to teach machines not what to think, but how.

It is difficult to measure this role using traditional categories. It will not appear as a separate item in standard org charts for long. However, as AI progresses from pattern matching to something resembling reasoning, the people who influence that reasoning will become some of the most crucial builders in the stack.

The new billion-dollar job is not labeled as such yet. It lives under different titles and in different departments. But its shape is already clear. Somewhere between engineering and instruction, between governance and design, people have started training AIs how to think.

The Disruption We Cannot Measure Yet

Stacking Trades — Tue, 25 Nov 2025 20:15:44 +0000

The Shift We Can Feel But Cannot Quantify

Companies have always measured progress. They look at productivity, throughput, efficiency, and margin improvement. Reporting has shaped our understanding of reality. However, a curious change is happening as AI takes on more tasks. The old methods of measuring output can’t reflect the real activity anymore. There is a shift happening beneath the surface that is changing how work flows, but the dashboards remain flat.

In 2025, AI systems will make more decisions, coordinate tasks, and solve complex issues before humans see them. The work is there. The impact is real. However, the metrics designed for human-centered processes cannot capture this. Most organizations monitor what goes through people, not what gets resolved before it reaches them. We are seeing disruption that leaves no trace in the tools meant to spot it.

When Metrics Miss the Work

The signs appear first in operations. A logistics team reports fewer delays, but there is no clear reason. A support team sees a drop in escalations, but workflows remain unchanged. A finance group closes faster than before, but staffing is static. The output improves without any visible inputs.

Multi-agent systems, routing engines, and autonomous workflows now handle edge cases, reorganize queues, and resolve dependencies without surfacing the activity. Problems that would have appeared in reports simply never materialize. The data shows stability. The underlying work is in motion.

A 2024 analysis by McKinsey found that a significant amount of AI-driven productivity improvements had no clear source in traditional KPIs, particularly in operational layers. At the same time, Gartner predicts that by 2026, half of enterprise AI value will come from machine-only workflows that standard performance metrics do not capture.

We are witnessing the rise of invisible productivity.

“The greatest impact of AI is happening where traditional metrics cannot see it.”

The Economy of Invisible Systems

This is not inefficiency. It is evolution. AI systems work at speeds and sizes that human reporting never anticipated. They rearrange data structures, stop errors, highlight contradictions, fix routes, rewrite queries, and improve queues. However, since no human is involved in the task, the system does not log anything significant.

Organizations built measurement frameworks for human bottlenecks. AI removes the bottlenecks, and the frameworks lose their anchor.

Economists are beginning to question how to measure output when machines generate value without involving human labor. There are no timestamps. No check-ins. No handoffs.
There isn’t a model for this yet. Everyone realizes that something significant is getting lost on the dashboards.

The Strategic Blind Spot

Leadership teams face a new challenge. When the most valuable work leaves no metrics, how do you assign credit? How do you identify what to invest in? How do you manage risk? If AI prevents a thousand issues that never occur, what does success look like? If a cluster of agents makes strategic adjustments before anyone sees the underlying problem, who decides whether the system should continue?

In the early 2000s, digitization created new metrics. AI creates fewer. This is the paradox. As intelligence becomes more autonomous, its contribution becomes less visible. Executives who are used to charts and slides must now learn to manage systems where the value is sensed, not measured.

The Coming Redefinition of Measurement

New tools will eventually appear. New metrics and frameworks will emerge. We will see benchmarks that capture stability, prevention, coordination, and invisible orchestration. But for now, we remain in the gap between ability and understanding.

AI is already creating value that organizations cannot quantify. Competition is shifting in ways that do not show up in reports. The advantage lies not in what companies track, but in what their systems quietly resolve.

The disruption is here. We just have not learned how to measure it.

The Multi Agent Workplace

Stacking Trades — Mon, 24 Nov 2025 20:18:05 +0000

The First Signs of a Shift

Workplaces have always been structured around teams of people. Groups with different skills coordinate, pass on tasks, and work through issues together. In 2025, a new layer will join that structure. It’s not just one assistant working quietly in the background. Instead, there will be clusters of AI agents working together, sharing information, and managing tasks before they even come to a human. It’s subtle, but the first signs are already visible.

You can see it in early deployments of AI orchestration systems inside companies. In customer service, multiple agents now work together to search knowledge bases, classify tone, propose responses, and check compliance before handing a draft to a human. In software development, tools like GitHub Copilot Workspace coordinate multiple models across planning, coding, and testing workflows. In operations, AI agents handle routing, forecasting, and scheduling across logistics networks that once required full teams.

The workplace is starting to feel less like a single model helping a human and more like a distributed team where machines collaborate with each other.

When Agents Begin to Coordinate

The shift is rooted in simple economics. Enterprises that once experimented with single AI assistants found that one model alone could not cover the complexity of their work. The solution was not a bigger model. It was a cluster of narrow ones, each tuned to a specific function.

Research groups anticipated this trend. A 2024 Microsoft study on multi-agent systems found that agents working together on structured tasks performed more reliably than a single general model on its own. Stanford’s 2024 AI Index noted the same trend in workflow automation: coordination is better than scale. Early results from Anthropic’s multi-agent experiments showed better reasoning through division of labor instead of sheer force.

Companies started using the same structure. A planning agent divides a project into steps. A research agent gathers context. A reasoning agent writes decisions. A verification agent reviews constraints. A summarization agent presents the result for a human. Each agent becomes a specialist.

The model is not replacing teams. It is joining them.

The Human in the Loop Evolves

In this environment, the role of the human shifts. Instead of performing all the steps, people become reviewers, supervisors, and strategic guides. They focus on interpretation rather than execution. Work feels less like a stream of tasks and more like a series of decisions supported by systems that do the heavy lifting.

This is not automation in the old sense. It is collaboration. Your teammates just happen to be machines with perfect recall, continuous attention, and the ability to work in parallel.

You can already see early examples of these dynamics in real-world settings. Retail companies operate small fleets of forecasting agents that update inventory in real time. Financial firms test research agents that collect filings, earnings data, and sentiment analysis before analysts sit down to review. Logistics platforms depend on groups of agents for route optimization and predicting delays. The models are not taking the place of people. They are cutting down on the overhead that used to slow them down.

“The workplace is shifting from one model helping one person to clusters of models working together before the work reaches a human.”

Where the Friction Lives

The multi agent workplace is not without issues. Coordination problems appear when agents over interpret instructions or reinforce each other’s errors. Enterprises report that agent clusters often need supervision until guardrails mature. And compliance teams warn that too many interconnected decision points can make audits more complex.

But the trajectory is clear. As companies move beyond isolated pilots and into integrated workflows, multi agent systems become a natural way to scale intelligence without scaling headcount.

The workplace is beginning to reorganize itself around networks of cooperating models. It is early, but real. The structure forming underneath is not science fiction. It is a preview of how organizations will function when intelligence is abundant and coordination is cheap.

From Code to Cure

Stacking Trades — Wed, 19 Nov 2025 18:26:32 +0000

A Quiet Revolution

The drug discovery process has been one of the slowest and most costly in science. It typically takes over a decade and costs more than a billion dollars to bring a new therapeutic agent to market. In 2025, this is changing. Artificial intelligence is no longer just an experiment in labs. It is emerging as a significant force in biotechnology, with substantial funding, important partnerships, and clear timelines.

Milestones in Motion

Consider the fact that Alphabet’s Isomorphic Labs (a subsidiary of DeepMind) announced it was “very close” to placing its first AI-designed drug into human trials. In one move, a company previously known for protein-prediction AI (AlphaFold) is now pushing into full drug development, signifying a shift from insight to intervention.

Another example: the partnership between U.S. biotech Nabla Bio and Japan’s Takeda Pharmaceutical Company, announced in October 2025, spans design of biologics using Nabla’s platform with milestone payments potentially exceeding US $1 billion.

These deals bring in capital, set deadlines, and create accountability. These factors make this change more real.

Meanwhile, in peer-reviewed research, a June 2025 paper published in Discover Pharmaceutical Sciences concluded that AI is “revolutionizing drug discovery by accelerating timelines, reducing costs, and increasing success rates.” Real science, real claims. The era of AI assistance is expanding into the era of AI leadership.

What Brought the Shift?

Three structural forces converged. First, data volumes exploded: genomics, proteomics, real-world patient data and imaging all feed into AI models capable of pattern recognition at scale. As the Harvard Wyss Institute notes, machines are now ideal for analyzing the complexity of human biology. Second, compute power and cloud infrastructure matured enough to support large scale virtual screening and simulation.

Third, urgency—society demanded faster innovation in areas like oncology and neurodegeneration, and the regulatory environment began to respond.

Add to this the sheer economic pressure. A segment of industry commentary in 2025 suggests that firms investing in AI-driven R&D are reducing timelines by up to 50 percent compared to traditional methods. That reduction turns years into months, costs into opportunity.

“AI-driven drug discovery is no longer futuristic. It is turning clinical timelines into a business metric.”

The Road Still Ahead

Of course, the major achievements are still on the way. Many AI-designed candidates are still in early stages. A survey of biotech executives in 2025 noted that while AI quickly identifies leads, getting full clinical validation is still tough. The challenges of regulatory approval, human safety, large-scale manufacturing, and market fit still exist.

However, the change is no longer just a possibility. AI’s role is shifting from support to creation. When machine-designed molecules start human trials, the boundary between computational biology and actual therapy becomes unclear.

Why It Matters

This matters not just for science, but business, policy and society. Pharmas redesigned around AI will compete differently, venture capital will flow toward platforms more than pipelines, and global health may accelerate in ways previously thought impossible.

Investment decisions once based on incremental chemistry now factor in algorithmic power and data access. The future of medicine is being rewritten in code.