The Stronger AI Gets, The More Tired People Become: 'Anxiety' Becomes the Norm for Companies and Employees

marsbitPubblicato 2026-03-02Pubblicato ultima volta 2026-03-02

Introduzione

Amidst promises of liberation, AI coding tools like Claude Code and Codex are instead fueling widespread workplace anxiety and a "productivity obsession." While over 40% of C-suite executives claim AI saves them at least 8 hours weekly, 67% of non-managerial staff report saving less than two hours—or none. Studies reveal that even as AI handles more tasks, working hours are increasing. This anxiety is top-down: executives like Intuit’s CTO code at 5 a.m. with AI, while CEOs monitor usage bills to gauge effort. Employees face量化管理, tracked on daily AI interactions, leading to burnout and "AI fatigue." The gap between leadership’s staff experience is stark, with executives enjoying hands-on prototyping while employees bear转型成本 and job insecurity. Researchers note "task expansion" – non-technical staff generate code, but engineers clean up, increasing workloads. The risk? A surge in "busyware": low-value projects that consume resources but add little. True efficiency may lie not in building more, but in questioning what shouldn’t be built at all.

Author: Xu Chao

Source: Wall Street News

AI coding tools promise to liberate engineers, but the reality is they have spawned a new wave of efficiency anxiety.

As the capabilities of AI programming agents like Anthropic's Claude Code and OpenAI's Codex continue to leap forward, tech companies are falling into a top-down "productivity obsession." Executives are personally writing code, employees are required to increase their frequency of interacting with AI, and overtime hours are rising instead of falling. AI, meant to be a labor-saving tool, has instead become a new source of pressure in many workplaces.

Survey data reveals a clear cognitive gap: a survey by consulting firm Section shows that over 40% of C-suite executives believe AI tools save them at least 8 hours per week, while 67% of non-managerial employees say AI saves them less than two hours, or is of no help at all. An ongoing study by UC Berkeley of a 200-person organization found that even as employees offload significant work to AI, their actual working hours are still increasing.

The spread of this anxiety has structural reasons. When CTOs are敲代码 (writing code) with AI at 5 a.m. and CEOs measure team effort by the amount of the bill, the entire industry's imagination of "efficiency" has been redefined—and the cost of this redefinition is being borne by ordinary employees.

Executives Jump Into Coding, Efficiency Anxiety Spreads Top-Down

The term "Vibe coding" initially came with a lazy expectation. Former OpenAI researcher Andrej Karpathy introduced the concept to the public in February 2025, describing a new programming mode where engineers只需与 AI 聊天 (just chat with AI) to complete development—"completely immersed in the vibe."

However, a year later, the vibe has long since changed tone.

Intuit CTO Alex Balazs described his recent routine: his wife came downstairs at 8 a.m. to find he had been working for hours. "She asked me how long I'd been up, and I said I got up at 5 a.m. to write code." More accurately, he was guiding an AI agent to write code for him, which he said allowed him to reconnect with underlying code he hadn't touched in years.

This kind of executive behavior is transmitting pressure downward. OpenAI president Greg Brockman recently posted on X, "Every moment your agent isn't running feels like a wasted opportunity." This statement precisely triggered the workaholic culture already prevalent in the tech industry.

Alex Salazar, co-founder and CEO of AI startup Arcade.dev, is more direct. He regularly checks the company's Claude Code bill—the bill is directly linked to how frequently engineers use the tool—and calls out employees who "aren't spending enough": "I'll say, 'You're not pushing hard enough.'" He said that after the first such "faith meeting," the company's AI programming tool bill soared tenfold, and he sees this expenditure as a sign of progress.

Employees Quantitatively Managed, "AI Fatigue" Quietly Spreads

In this atmosphere, the way employees are assessed is also quietly changing.

DocuSketch, a software company focused on property restoration, tracks the number of "interactions" engineers have with AI programming tools daily, defaulting that the higher this number, the stronger the team's productivity. Claude Code also generates a weekly report for each engineer, listing all the patterns where they got stuck in ineffective loops with AI and offering suggestions for improvement.

Wirick himself admitted to feeling a certain kind of "addiction." "I feel like I must complete a few more interactions each day, and I'm still thinking about how to do a few more before bed." He attributes this state to an "epiphany experience" when trying Anthropic's latest model, Opus 4.5, last November—he gave a functional prototype task that would usually be assigned to an engineer to the model, and 20 minutes later saw the model autonomously break down and implement the task, "feeling like my brain was rebooted."

This all-hands-on-deck acceleration mentality is eroding the boundary between work and life. The Berkeley study found that even though many tasks have been handed over to AI, people's working hours have not shortened. Some engineers are also beginning to openly admit they are experiencing "AI fatigue"—a constant worry about missing the next breakthrough, which always seems just one prompt away.

Cognitive Gap Between Executives and Employees Widens

The enthusiasm of executives stems largely from the novelty of creating things firsthand. Salazar admitted that building prototypes personally with AI provides more of a "productivity visual" than handling authorizations and decisions on a daily basis. He recently even directly responded to a service request from an important financial client by building a demo app from scratch.

At Intuit, product managers and designers are now encouraged to use the "vibe coding" method to build functional prototypes themselves within QuickBooks. Balazs said, "At least now, product managers can take a concrete thing to engineers and say, 'I want something like this.'"

However, survey data from consulting firm Section shows this cognitive gap is quite significant.

There is a huge断层 (fault line) between executives' perception of the AI dividend and the experience of frontline employees. Salazar believes this partly stems from employees bearing a higher transition cost when adapting to new tools: "They are implicitly asked to find time to explore and experiment, but the expectations of daily work haven't been adjusted accordingly to free up this space."

Concerns about job security are equally real. Salazar坦言 (admitted) that he originally planned to switch third-party web service providers, but now the marketing team can update the company website themselves using AI tools, so this outsourcing expense was cut.

"Task Expansion" and False Prosperity, The Other Side of the Efficiency Myth

The Berkeley researchers named this phenomenon "task expansion": when non-technical colleagues start generating code with AI, engineers have to spend time cleaning up these semi-finished products,反而增加了工作量 (instead increasing the workload). Intuit's Balazs坦承 (acknowledged) that this is reshaping previously clear-cut job divisions, pushing more and more roles towards "hybridization," and also making original collaborative relationships more complex.

A deeper question lies: is this construction boom creating valuable things, or is it just制造更多东西 (making more stuff)?

Analysts point out that if this AI-driven productivity obsession is not restrained, it could lead to a surge of "busyware"—minor website tweaks no one will notice, custom dashboards for a single user, prototype projects abandoned halfway by marketing managers, all eventually handed over to engineers to implement. Each seems justified in the moment, but most will end up in the trash can of废弃代码 (abandoned code).

Intuit's Balazs claims that measured by code production and delivery speed, the company's engineers' productivity has increased by about 30%. But in this future where code is increasingly "disposable," the real efficiency dividend might lie in the answer to another question: which things simply shouldn't be built in the first place.

Domande pertinenti

QWhat is the main paradox discussed in the article regarding AI programming tools?

AThe main paradox is that AI programming tools, which promise to liberate engineers and increase efficiency, are instead creating a new wave of efficiency anxiety. Instead of reducing workloads, they have led to increased working hours and pressure for both executives and employees.

QAccording to the article, what is the significant cognitive gap between executives and non-managerial employees regarding AI tools?

AThe cognitive gap is evident in the perception of time savings: over 40% of C-level executives believe AI tools save them at least 8 hours per week, while 67% of non-managerial employees report that AI saves them less than two hours or provides no help at all.

QHow are some companies, like DocuSketch, measuring employee productivity with AI tools?

ACompanies like DocuSketch are tracking the number of daily 'interactions' employees have with AI programming tools, assuming that a higher number indicates greater productivity. Claude Code also generates weekly reports for each engineer, listing ineffective patterns and offering improvement suggestions.

QWhat is 'task expansion' as described in the article, and how does it affect engineers?

A'Task expansion' refers to the phenomenon where non-technical colleagues use AI to generate code, but engineers then have to spend time cleaning up these semi-finished products, which actually increases their workload. This blurs traditional job boundaries and complicates collaboration.

QWhat potential negative outcome is highlighted if the AI-driven productivity obsession continues unchecked?

AIf unchecked, the AI-driven productivity obsession could lead to the creation of 'busyware'—minor website tweaks, custom dashboards with only one user, or abandoned prototype projects that engineers must still implement. Most of these efforts may ultimately become discarded code, wasting resources without real value.

Letture associate

Big Short Prototype: Trillion-Dollar AI Investment Started on the Wrong Path from the Beginning

Michael Burry draws a parallel between a 19th-century case study and modern AI development to argue that the current path of large language models (LLMs) is fundamentally flawed. He references an 1880 article from the Smithsonian about Melville Ballard, a deaf man who, without formal language, engaged in complex abstract reasoning about the origins of the universe, life, and God. This story demonstrates that true reasoning and understanding exist prior to and independent of language. Burry contends that by prioritizing language processing over the development of genuine reasoning capabilities, LLMs are merely creating sophisticated mirrors of data, not true understanding. They operate in an intermediate zone, simulating reasoning but lacking the innate rational capacity that precedes language. This "language-first" approach, driven by immense computational brute force, leads to inherent flaws like hallucinations and an inability to achieve real comprehension. The proposed solution is a shift towards a "reasoning-first" architecture, which would focus on compressing information and utilizing System 2 reasoning to drastically reduce computational needs. Burry suggests that true AI must pass a "Ballard Test": demonstrating rational thought without language. He concludes by linking this technological critique to a cyclical pattern of speculative investment booms, comparing the current AI hype to the 19th-century mining speculation in San Francisco, warning of an inevitable bust if the foundational approach isn't corrected.

marsbit19 min fa

Big Short Prototype: Trillion-Dollar AI Investment Started on the Wrong Path from the Beginning

marsbit19 min fa

Trading

Spot
Futures

Articoli Popolari

Come comprare PEOPLE

Benvenuto in HTX.com! Abbiamo reso l'acquisto di ConstitutionDAO (PEOPLE) semplice e conveniente. Segui la nostra guida passo passo per intraprendere il tuo viaggio nel mondo delle criptovalute.Step 1: Crea il tuo Account HTXUsa la tua email o numero di telefono per registrarti il tuo account gratuito su HTX. Vivi un'esperienza facile e sblocca tutte le funzionalità,Crea il mio accountStep 2: Vai in Acquista crypto e seleziona il tuo metodo di pagamentoCarta di credito/debito: utilizza la tua Visa o Mastercard per acquistare immediatamente ConstitutionDAOPEOPLE.Bilancio: Usa i fondi dal bilancio del tuo account HTX per fare trading senza problemi.Terze parti: abbiamo aggiunto metodi di pagamento molto utilizzati come Google Pay e Apple Pay per maggiore comodità.P2P: Fai trading direttamente con altri utenti HTX.Over-the-Counter (OTC): Offriamo servizi su misura e tassi di cambio competitivi per i trader.Step 3: Conserva ConstitutionDAO (PEOPLE)Dopo aver acquistato ConstitutionDAO (PEOPLE), conserva nel tuo account HTX. In alternativa, puoi inviare tramite trasferimento blockchain o scambiare per altre criptovalute.Step 4: Scambia ConstitutionDAO (PEOPLE)Scambia facilmente ConstitutionDAO (PEOPLE) nel mercato spot di HTX. Accedi al tuo account, seleziona la tua coppia di trading, esegui le tue operazioni e monitora in tempo reale. Offriamo un'esperienza user-friendly sia per chi ha appena iniziato che per i trader più esperti.

353 Totale visualizzazioniPubblicato il 2024.12.12Aggiornato il 2025.03.21

Discussioni

Benvenuto nella Community HTX. Qui puoi rimanere informato sugli ultimi sviluppi della piattaforma e accedere ad approfondimenti esperti sul mercato. Le opinioni degli utenti sul prezzo di PEOPLE PEOPLE sono presentate come di seguito.

活动图片