ZDNET57%

The top AI fear for 6,000 tech pros isn't losing their jobs - it's more work for the same pay 79%

By Joe McKendrick47%

7/20/2026, 12:24:02 PM

BS Summary: This article contains 27 faulty reasoning types, including Negativity Bias, False Dilemma, and Anecdotal, with Appeal to Authority as the most egregious example at 33.8% saturation with 322 hits. Analysis detected 2,102 faulty-reasoning hits from 953 analyzed words, generating a BS Score of 70.7% and a BS Rank of 79% (4,478 of 20,882 articles). This article is worse (more manipulative) than 78.60% of the article peer group.

Many tech professionals are becoming disillusioned and burned out from constantly having to keep up with the pace of change of new technology. 
Now, the rise of AI may be increasing their uncertainty and driving even more tech workers away. 
Interestingly, this uncertainty is not related to potential layoffs, but something else. 
"The number-one fear in tech right now is not losing your job to AI -- it's being squeezed to do more work for the same pay," according to Noam Segal and Lenny Rachitsky's latest tech worker sentiment survey, covering 6,000 professionals: "AI raised the bar for output, and the reward was... more work for the same pay." 
Many technology professionals are feeling the impact of a changing environment firsthand. 
"I have a close friend who went from being a senior software engineer to school to start over as an X-ray technician," said Kaan Esendemir, AI application architect at UPS. 
"In my day-to-day as an AI app architect, I've noticed the lack of motivation or the assumption that AI can handle everything. 
I've noticed employees coming in early, taking lunch meetings, and leaving later, myself included, just to get ahead of the curve." 
Notably, burnout is up, while optimism is down among tech pros, Segal and Rachitsky found in their survey: "Shipping faster is burning people out. 
More prototypes, more product requirements documents, more agents, more output. 
The speed AI unlocked got plowed straight back into expectations." 
Tellingly, they also discovered most tech professionals wouldn't recommend their own role to someone entering the industry today. 
AI is actually being viewed through two opposite lenses. 
Half of respondents to Segal and Rachitsky's survey said they feel "amplified -- more capable, more productive, more excited about their future. 
The other half feel their role is being redefined, that they're feeling destabilized or that they've been diminished." 
There is also an emerging risk called "cognitive rot," in which tech pros "see the AI's initial output, accept it without applying their judgment, and gradually let their own critical thinking atrophy." 
It isn't just AI creating a sense of burnout and frustration across all industries. 
Laura Spencer, chief academic officer at an elite academic academy, who was an IT director herself, observed how, "K-12 tech leaders are expected to move at the same speed as the private sector while working inside FERPA, state privacy law, and a school board that needs a year to approve what a vendor ships in a month. 
That gap between expected pace and permitted pace is what pushes people out, quietly disengaged if not gone outright." 
Spencer urged tech pros to "stop trying to learn every new release. 
Build a habit of deliberate evaluation instead. 
I use four questions before adopting anything: What is it for? 
What does it strengthen? 
What does it replace? 
And the one people skip: what does it allow to be done poorly? 
That last one catches the tools that quietly erode a skill before anyone notices it's gone." 
The real skill "is telling waves from ripples," said Joel Marotti, senior managing partner at Vertical Media Solutions: "Most of what churns through tech is a ripple. 
A wave changes how the work gets done. 
There have been maybe five of those in the last three decades. 
When a real wave hits, you don't need a certification. 
You need one real project where you apply the new tool to your actual domain. 
That's like a week of focused effort, not a year of anxiety." 
Learn to say 'no' to a tool, she added. 
"Saying no to a tool, deliberately, is still expertise. 
In education, where the risk lands on kids, and not just quarterly numbers, that's not caution. 
It's the job." 
Providing tech professionals opportunities to learn and explore tools and technologies may be key to alleviating feelings of frustration and burnout. 
"Personally, I don't like just picking up a tool with no random use case and just experimenting with it," said Cameron Adams, chief product officer and co-founder at Canva. 
"I really like to take something that I'm working on now or a problem that I'm feeling, and then bring a tool to bear on that and learn through that process. 
I think that's how we've seen our staff get the most value out of AI experimentation, when they're dealing with a real problem." 
Adams said it's important to provide such freedom, "because employees need to feel comfortable experimenting," she suggested. 
"We're all terribly busy and naturally fall into the patterns we would normally do things in. 
We give our staff plenty of time to just sit back, put down their tools, get out of business as usual, and get stuff done." 
In conclusion, it's impossible to try to keep up with every new development. 
"Identify the technology changes that are certain to continue, then focus on the skills tied to those changes," said Daniel Burrus, technology futurist and AI expert in residence at High Point University. 
"AI will keep advancing. 
Automation will keep expanding. 
Data, cybersecurity, and human judgment will remain central. 
Spend less time chasing product announcements and more time learning how these shifts affect your role, customers, and industry." 
Trying to keep up with every release "is a losing game at this point, so I'd stop trying," agreed Riken Shah, founder and CEO of OSP Labs. 
"What holds up is depth in a few things, such as systems thinking, architecture, security, actually knowing how to solve a hard problem, and enough surface awareness of everything else to know when it's worth a closer look. 
AI fits into that as leverage on what you already know." 
Article reasoning-pattern comparisonThis article: 1.3%Joe McKendrick: 0.5%ZDNET: 2.8%Confirmation Bias1.3%This article: 0.0%Joe McKendrick: 2.1%ZDNET: 1.7%Anchoring Bias0.0%This article: 7.8%Joe McKendrick: 2.6%ZDNET: 3.1%Availability Heuristic7.8%This article: 2.8%Joe McKendrick: 0.6%ZDNET: 1.0%Representativeness Heuristic2.8%This article: 0.0%Joe McKendrick: 0.0%ZDNET: 0.5%Hindsight Bias0.0%This article: 8.1%Joe McKendrick: 3.6%ZDNET: 3.2%Overconfidence Bias8.1%This article: 11.8%Joe McKendrick: 3.8%ZDNET: 4.0%Framing Effect11.8%This article: 2.1%Joe McKendrick: 1.7%ZDNET: 1.4%Loss Aversion2.1%This article: 4.3%Joe McKendrick: 0.9%ZDNET: 0.6%Status Quo Bias4.3%This article: 0.0%Joe McKendrick: 0.0%ZDNET: 0.2%Sunk Cost Effect0.0%This article: 5.8%Joe McKendrick: 3.4%ZDNET: 5.1%Optimism Bias5.8%This article: 8.9%Joe McKendrick: 5.8%ZDNET: 1.3%Pessimism Bias8.9%This article: 24.9%Joe McKendrick: 10.0%ZDNET: 4.6%Negativity Bias24.9%This article: 9.5%Joe McKendrick: 2.5%ZDNET: 1.6%Self-Serving Bias9.5%This article: 1.7%Joe McKendrick: 0.2%ZDNET: 0.3%Fundamental Attribution Error1.7%This article: 0.0%Joe McKendrick: 0.0%ZDNET: 0.1%Actor-Observer Bias0.0%This article: 0.0%Joe McKendrick: 0.2%ZDNET: 0.5%In-Group Bias0.0%This article: 0.0%Joe McKendrick: 0.0%ZDNET: 0.2%Out-Group Homogeneity Bias0.0%This article: 0.0%Joe McKendrick: 0.6%ZDNET: 4.0%Halo Effect0.0%This article: 0.0%Joe McKendrick: 0.2%ZDNET: 0.2%Horn Effect0.0%This article: 0.0%Joe McKendrick: 0.0%ZDNET: 0.0%Dunning-Kruger Effect0.0%This article: 0.0%Joe McKendrick: 0.5%ZDNET: 1.5%Recency Bias0.0%This article: 0.4%Joe McKendrick: 0.1%ZDNET: 0.4%Primacy Effect0.4%This article: 0.0%Joe McKendrick: 0.0%ZDNET: 0.1%Blind-Spot Bias0.0%This article: 0.0%Joe McKendrick: 0.0%ZDNET: 0.0%Ad Hominem0.0%This article: 0.0%Joe McKendrick: 0.0%ZDNET: 0.1%Straw Man0.0%This article: 33.8%Joe McKendrick: 10.3%ZDNET: 4.5%Appeal to Authority33.8%This article: 15.6%Joe McKendrick: 4.0%ZDNET: 1.5%False Dilemma15.6%This article: 3.4%Joe McKendrick: 3.4%ZDNET: 0.6%Slippery Slope3.4%This article: 0.0%Joe McKendrick: 0.4%ZDNET: 0.2%Circular Reasoning0.0%This article: 9.8%Joe McKendrick: 13.5%ZDNET: 6.5%Hasty Generalization9.8%This article: 0.0%Joe McKendrick: 0.0%ZDNET: 0.5%Red Herring0.0%This article: 0.0%Joe McKendrick: 0.0%ZDNET: 0.5%Bandwagon0.0%This article: 6.8%Joe McKendrick: 1.9%ZDNET: 1.9%Appeal to Emotion6.8%This article: 4.3%Joe McKendrick: 0.7%ZDNET: 0.7%Begging the Question4.3%This article: 12.0%Joe McKendrick: 2.7%ZDNET: 1.5%Post Hoc (False Cause)12.0%This article: 0.0%Joe McKendrick: 0.0%ZDNET: 0.0%Tu Quoque0.0%This article: 0.0%Joe McKendrick: 0.4%ZDNET: 0.2%Burden of Proof0.0%This article: 0.0%Joe McKendrick: 0.0%ZDNET: 0.1%Appeal to Nature0.0%This article: 6.0%Joe McKendrick: 0.8%ZDNET: 0.2%Composition/Division6.0%This article: 14.0%Joe McKendrick: 5.4%ZDNET: 4.8%Anecdotal14.0%This article: 0.0%Joe McKendrick: 0.0%ZDNET: 0.0%No True Scotsman0.0%This article: 4.7%Joe McKendrick: 0.7%ZDNET: 2.4%Ambiguity (Equivocation)4.7%This article: 0.0%Joe McKendrick: 0.0%ZDNET: 0.0%Gambler’s Fallacy0.0%This article: 0.0%Joe McKendrick: 0.0%ZDNET: 0.2%Middle Ground0.0%This article: 0.0%Joe McKendrick: 0.0%ZDNET: 0.1%Personal Incredulity0.0%This article: 2.3%Joe McKendrick: 0.3%ZDNET: 0.2%Special Pleading2.3%This article: 0.0%Joe McKendrick: 0.0%ZDNET: 0.1%Genetic Fallacy0.0%This article: 6.0%Joe McKendrick: 1.3%ZDNET: 0.9%Unattributed Quote6.0%This article: 0.0%Joe McKendrick: 0.2%ZDNET: 0.5%Quote-first Misdirection0.0%This article: 0.0%Joe McKendrick: 2.8%ZDNET: 6.4%Biased Writer Voice0.0%This article: 10.1%Joe McKendrick: 5.4%ZDNET: 4.0%Indoctrination10.1%This article: 0.0%Joe McKendrick: 0.0%ZDNET: 0.0%Politically Left Leaning Bias0.0%This article: 0.0%Joe McKendrick: 0.0%ZDNET: 0.0%Politically Right Leaning Bias0.0%This article: 2.6%Joe McKendrick: 0.8%ZDNET: 7.3%Attempt to Sell a Product or S…2.6%

953 words analyzed.

Speakers

7speakers75%attributed speech239writer words
Voice mapSelect a segment to jump to its words
Writer's voice • 20 words • 0.0% coverageWriter's voice • 23 words • 0.0% coverageWriter's voice • 17 words • 0.0% coverageWriter's voice • 12 words • 0.0% coverageNoam Segal • 57 words • 100.0% coverageWriter's voice • 12 words • 0.0% coverageKaan Esendemir • 30 words • 0.0% coverageKaan Esendemir • 22 words • 0.0% coverageKaan Esendemir • 21 words • 0.0% coverageNoam Segal • 24 words • 0.0% coverageWriter's voice • 10 words • 0.0% coverageWriter's voice • 10 words • 0.0% coverageWriter's voice • 18 words • 0.0% coverageWriter's voice • 9 words • 0.0% coverageNoam Segal • 22 words • 0.0% coverageNoam Segal • 18 words • 0.0% coverageWriter's voice • 32 words • 0.0% coverageWriter's voice • 14 words • 0.0% coverageLaura Spencer • 57 words • 0.0% coverageLaura Spencer • 19 words • 0.0% coverageLaura Spencer • 12 words • 100.0% coverageLaura Spencer • 7 words • 100.0% coverageLaura Spencer • 11 words • 0.0% coverageLaura Spencer • 4 words • 0.0% coverageLaura Spencer • 4 words • 0.0% coverageLaura Spencer • 13 words • 0.0% coverageLaura Spencer • 16 words • 0.0% coverageJoel Marotti • 27 words • 0.0% coverageJoel Marotti • 8 words • 0.0% coverageJoel Marotti • 12 words • 0.0% coverageJoel Marotti • 10 words • 0.0% coverageJoel Marotti • 15 words • 0.0% coverageJoel Marotti • 12 words • 0.0% coverageJoel Marotti • 9 words • 100.0% coverageWriter's voice • 9 words • 0.0% coverageWriter's voice • 16 words • 0.0% coverageWriter's voice • 3 words • 0.0% coverageWriter's voice • 21 words • 0.0% coverageCameron Adams • 29 words • 0.0% coverageCameron Adams • 31 words • 0.0% coverageCameron Adams • 23 words • 0.0% coverageCameron Adams • 17 words • 100.0% coverageCameron Adams • 16 words • 0.0% coverageCameron Adams • 25 words • 100.0% coverageWriter's voice • 13 words • 0.0% coverageDaniel Burrus • 32 words • 100.0% coverageDaniel Burrus • 4 words • 0.0% coverageDaniel Burrus • 4 words • 0.0% coverageDaniel Burrus • 8 words • 0.0% coverageDaniel Burrus • 19 words • 100.0% coverageRiken Shah • 27 words • 0.0% coverageRiken Shah • 38 words • 0.0% coverageRiken Shah • 11 words • 0.0% coverage
Selected voice

Noam Segal

100%flagged-word coverage
121 attributed words17% of attributed speech100% writer coverage
0%25.0%50.0%Unattributed Quote+47.1 ptsWriter: 0.0%Noam Segal: 47.1%47.1%

Attribution is sentence-level. Pattern percentages are calculated only from words assigned to that voice.

Loading…
Loading…
Loading…

Analysis

Hover over highlighted words in the article to view the associated bias or fallacy analysis.