Blog→Career Economics
Career Economics11 min read read

The Software Factory Is Running 24/7 (And Nobody Wants the Output)

If you spent the last five days doing actual work instead of staring at tech blogs, you missed an absolute circus. Google pushed out Gemini 3.8 Flash. That is their third model update in six weeks. Th...

By Richard Ewing·
Share:

The Software Factory Is Running 24/7 (And Nobody Wants the Output)

If you spent the last five days doing actual work instead of staring at tech blogs, you missed an absolute circus.

Google pushed out Gemini 3.8 Flash. That is their third model update in six weeks. They aren’t even waiting for people to finish testing the last version before replacing it with a cheaper one.

Meanwhile, OpenAI pushed GPT-6 Astra into ChatGPT on Thursday, claiming it can take over your keyboard and mouse, build interactive websites on the fly, write entire spreadsheets, and conduct multi-step research projects while you step away from your desk.

On social media, the tech crowd went into its predictable routine: people posting screen recordings of an avatar clicking around a browser window, declaring that knowledge work is officially dead, and advising everyone to learn how to write 500-word prompts before they get left behind.

Sitting in an office or working from home on a Sunday afternoon looking at your calendar for tomorrow, the whole thing feels completely disconnected from reality.

Nobody feels unburdened. If anything, the past week felt like someone opened a firehose of synthetic noise and pointed it directly at everyone’s screen.

We are living through a weird moment where the machines are generating work ten times faster than human beings can read, check, or care about it.

The biggest story this week isn't that models got smarter. It's that they got ridiculously cheap.

Google priced Gemini 3.8 Flash down in the bargain basement: fractions of a cent for thousands of words. They are practically paying people to use it.

When anything gets that cheap, supply explodes. And when the supply of words and code costs virtually nothing, the quality of attention drops straight to zero.

Think about how communication in an office used to work. If somebody wrote a six-page proposal, it took them two days. The fact that it took two days acted as a natural filter. It meant they actually thought through the trade-offs, debated the numbers, and cared enough about the outcome to sweat the details.

Now, someone types a sloppy sentence into an assistant, waits twelve seconds, and hits send on an eight-page memo.

The person who receives it knows it took twelve seconds to make. So what do they do? They don't read it. They click a button to summarize it into three bullet points.

We’ve built a digital economy where one machine inflates a thought into 2,000 words of polite corporate filler, and another machine deflates it back down to twenty words, while humans on both sides pretend meaningful collaboration happened.

The only people making money in that loop are the cloud providers charging for the electricity.

OpenAI's launch of Astra in the ChatGPT release is the next escalation in this game. They don't want to just give you answers in a chat box anymore. They want to drive your computer.

In the polished demo videos, it looks effortless. You ask it to pull customer data from an internal dashboard, cross-reference it with a sales report, and draft invoices. The screen moves, buttons get clicked, files download, and the job gets finished with a neat little bow.

Try doing that on an ordinary Tuesday with your company’s real tools.

Real systems aren't clean. You have two-factor authentication prompts that expire after sixty seconds. You have software that won't let you submit an expense because someone selected the wrong department code. You have an old vendor contract where the customer address is an image instead of text.

When an autonomous tool runs into those mundane speed bumps, it doesn't have common sense. It doesn't walk down the hall to ask Bob in accounting what happened.

It guesses.

It picks the closest plausible button, clicks it, and moves to the next step.

So what does your actual day look like when you turn this on? You don't get to go outside and drink coffee. You sit in your chair, hands hovering two inches above the keyboard, watching the computer click around on its own, your stomach in knots hoping it doesn't send an unfinished pricing sheet to an active client.

The manual labor of typing was replaced by the pure stress of surveillance.

If you listen to the talking heads on LinkedIn, there are only two kinds of people right now: the brilliant innovator moving at lightspeed, and the stubborn dinosaur about to lose their job.

Talk to people who actually have to run a business or meet a payroll, and the picture looks entirely different. People are using these tools in messy, contradictory ways, and the results are all over the map.

This is the senior leader who saw a headline in the business press and called an emergency staff meeting. They declared that every team must show a 30% efficiency bump by implementing automated workflows before the end of the quarter.

What happens next? Pure theater. The department doesn't move faster. Instead, Product Operations Managers, Engineering Managers, and Product Managers start generating mounds of synthetic documentation (risk matrices, product charters, and market analyses) just to prove they are using the tools. The company’s Slack channels are clogged with automated updates that nobody asked for. The VP gets to tell the board they’ve deployed modern AI across the department, while the engineers and operators are quietly working late to clean up the mess.

This is the senior employee or manager caught in the crossfire. They used to spend their week making strategic decisions or reviewing solid work from their team.

Now, they spend thirty hours a week acting like a high school English teacher grading essays. A junior hire submits a market evaluation that looks immaculate on the surface: perfect formatting, authoritative tone, professional tables. But when the manager digs into the footnotes, two of the competitors mentioned don't exist, and the financial percentages don't add up to 100.

Because the text looks so polished, it takes twice as long to spot the errors as it would have taken if the person had just written an imperfect draft by hand. Review debt is choking companies from the inside out.

This is the person who is actually getting ahead, and you will never see them post about it on Twitter.

They aren't trying to let an agent run their entire job or write their company strategy. They treat the software like a very fast, slightly distracted junior clerk.

They use it for the dull, repetitive stuff that used to drive them crazy:

Taking a disgusting, messy spreadsheet exported from an old mainframe and reformatting it into a clean table.

Scanning a 70-page municipal building code update to find the two paragraphs about setbacks.

Rewording an awkward collection email to a vendor who hasn't paid their invoice in two months so it sounds professional rather than furious.

They never give the machine final authority. They don't let it touch production systems unattended. They glance at the output, fix the two things it got wrong, paste it in, and finish their workday at 2:30 PM to go cook dinner with their family. They understand that the tool is great at grunt work and terrible at judgment.

Then there’s the founder or freelancer who thought they could automate everything. They plugged autonomous tools into their customer support queue, their outbound sales emails, and their social media.

Within two weeks, their customer satisfaction scores plummeted because people immediately recognized the canned, overly agreeable tone of an automated bot. Important enterprise clients got alienated by emails that completely misunderstood the context of past negotiations.

They thought they were cutting costs to zero. In reality, they traded human trust for cheap words, and winning that trust back will cost ten times what they saved on software subscriptions.

While everyone was arguing about model benchmarks this week, OpenAI quietly dropped another data point: their in-app advertising platform hit a billion-dollar annualized run rate in less than seven months.

Remember when the pitch was that subscriptions would give us an objective, ad-free research partner?

That era didn't last long.

Running millions of graphical computer-use loops and multi-step models costs an astronomical amount of cash. The $20 or $30 monthly subscription was never going to pay for those data centers.

Ads are back. Sponsored suggestions are back. And that changes the entire nature of the relationship. When you ask a tool to compare two software vendors or recommend a travel itinerary, you now have to wonder whether the answer is the best choice, or just the one that bought the top placement in the assistant's workflow.

The hype machine will tell you that everything is changing overnight.

It isn't.

The technology is moving fast, but human psychology and business fundamentals move very slowly. Trust still takes months to build and five seconds to destroy. Good judgment is still rare. Knowing what not to do is still far more valuable than doing ten wrong things in twenty seconds.

If you want to stay sane while Google, OpenAI, and everyone else drop a new model every Tuesday:

Never delegate judgment. Let the software format, extract, summarize, and clean up messy text. But when it comes to strategy, ethics, pricing, and people, make the call yourself.

Be suspicious of anything that looks too clean. Machine-generated work has a distinct smell: perfectly balanced sentences, overly polite phrasing, zero rough edges, and no actual opinion. If it sounds like it could have been written by anyone, it says nothing.

Protect your attention. You do not need to test every single release. You do not need to rewire your workflow every time a tech company changes an API.

The people who win aren’t the ones producing the most words or spinning up the most agents.

They are the ones who can look at a mountain of machine-generated noise, cut straight to the three things that are actually true, and have the courage to put their own name on the result.

Richard Ewing writes on technology, business economics, and the reality of working with automated software as The AI Economist. He is an executive product advisor and the founder of Exogram.ai (building deterministic execution firewalls and control planes for software) and CareerWin.ai (career intelligence and navigation).

Software Systems & Governance: Exogram.ai

Career Strategy & Diagnostics: CareerWin.ai

Join the list to receive our newest posts straight to your inbox.

Enter your email to access the Product Debt Index Calculator, and join the private ledger where I break down the exact strategies bridging technical execution with financial viability for B2B SaaS.

Home

Archive

Login

Reset Password

Update Password

Profile

Search

Like this analysis?

Get the weekly engineering economics briefing - one email, every Monday.

Subscribe Free →

More in Career Economics

Canonical Frameworks

Innovation Tax

The Innovation Tax is the hidden cost of maintenance work that gets reported as innovation investment. It is OpEx masquerading as R&D investment, causing organizations to dramatically overestimate their effective engineering velocity and R&D productivity. Here's how it works: A VP of Engineering reports to the CEO that "65% of engineering time is spent on new features." The actual breakdown, when forensically audited, reveals that only 23% of engineering time produces genuine new capabilities. The remaining 42% is maintenance work embedded within feature sprints - bug fixes bundled into feature stories, infrastructure upgrades coded as dependencies, and refactoring disguised as feature prerequisites. This 42-point gap between reported and actual innovation investment is the Innovation Tax. It's not fraud - it's systematic self-deception enabled by the way agile teams organize work. When a sprint contains 10 stories and 4 of them are technical debt cleanup dressed as "tech stories" within a feature epic, the team genuinely believes they're spending 100% on features. The Innovation Tax is insidious because it compounds. As the maintenance burden grows quarter-over-quarter, the tax increases. But because teams don't measure it, CFOs and boards continue to believe R&D spending is generating proportional innovation output. By the time the gap becomes visible (missed deadlines, slow feature delivery, competitive lag), the organization is often approaching the Technical Insolvency Date. Benchmarks from Richard Ewing's audits show that most engineering organizations have an Innovation Tax between 30-50%. Organizations with Innovation Tax above 40% are in dangerous territory. Above 70% is terminal - the organization is approaching technical insolvency within 4-6 quarters.

Read Definition →

Kill Switch Protocol

The Kill Switch Protocol is a structured framework for identifying and deprecating "Zombie Features" - code that requires ongoing maintenance but generates zero incremental business value. Most software organizations have a dangerous bias: they add features but never remove them. Product teams celebrate launches. Nobody celebrates deletions. Over time, this creates what Richard Ewing calls "feature gravity" - a constantly growing codebase where 40-60% of the code serves no active users and generates no measurable revenue, yet still consumes engineering maintenance hours. Zombie features come in several varieties: - **Ghost Features**: features that were built, launched, and never adopted. They sit in the codebase, requiring maintenance, but have near-zero usage. - **Legacy Bridges**: compatibility layers, deprecated API versions, and backward-compatible code paths that serve a tiny percentage of users but add complexity to every future change. - **Vanity Features**: features built because a senior stakeholder wanted them, not because users needed them. Often protected by organizational politics rather than business merit. - **Abandoned Experiments**: A/B test variants that were never cleaned up, prototypes that became permanent, and "temporary" solutions that became load-bearing. The Kill Switch Protocol provides a systematic approach to identification, evaluation, and deprecation: 1. **Identify**: Flag features with less than 5% of peak usage, zero revenue attribution, or maintenance cost exceeding 10% of the feature's value contribution. 2. **Quantify**: Calculate the total cost of keeping each zombie alive (maintenance hours × fully-loaded engineer cost × opportunity cost multiplier). 3. **Assess Risk**: Evaluate deprecation risk - what breaks if this feature is removed? What customers are affected? 4. **Sunset Timeline**: Create a communication plan and graduated deprecation (warning → deprecation notice → feature flag → removal). 5. **Execute**: Remove the code with rollback capability. Monitor for unexpected breakage. The typical Kill Switch audit reveals that 30-50% of maintenance burden comes from zombie features. Removing them frees up 15-25% of engineering capacity for actual innovation.

Read Definition →
📊

Richard Ewing

The AI Economist - Quantifying engineering economics for technology leaders, PE firms, and boards.

⚡

Want to apply this to your organization?

Run a free diagnostic first. If the numbers concern you, book a session to build a remediation plan.

Richard Ewing: AI Economist & Capital Auditor