The 100% Human-Written Walkout: How a November 2026 Tech Worker Strike Could Change the Apps You Use

By Sarah Chen | MyTechDailyNews General desk

Behind many of the products you tap, scroll and pay for, there are people who say they are finished pretending. A self-described technology worker has put a short invitation on the record: during November 2026 he will stop working, taking the third week of November as his own window, and he is asking colleagues to choose a one week period that fits their situation and coordinate it with the people they work alongside. He attaches one unusual credential to the message — it is 100% human written, with no AI used to write or research it.

Readers who never open a code editor still have a stake here. The author is explicit that this is not merely a quarrel about artificial intelligence. In his telling, AI is a visible symptom of a much older problem, and the damage arrived in a certain order: first the hostility toward the people who use software, then the alienation of people who do not use it, and only now the hostility toward the people who build it — colleagues whose work may not involve writing code at all.

What the announcement says, in six lines

• Who is acting: an individual technology worker, publishing an open request rather than a fixed rulebook.
• When: November 2026; the third week of November is the organizer's own stop period.
• How long: a one week action, with the days chosen by each participant.
• How to join: pick the days that suit you, then coordinate with colleagues.
• What is being objected to: user-hostile products, addictive algorithms, forced commute rules (twice a week, once a week, or 11.33% of the week), micro-management, AI slop, AI replacing customer service staff, unrealistic deadlines and forced growth.
• What is being asked for: software that empowers the public again, with humanity and good returned to the work of building it.

Why the complaint is older than the AI boom

The announcement describes years of accumulated damage, and the writer says he no longer wants to pretend that the human side of technology is being defended. That is why the call is aimed at more than one tool or one feature change. The argument is about direction: whether the industry still exists to give people capability, or whether it now exists to take capability away from them.

The stated endpoint is deliberately simple. The demand is that humanity and good come back into software, and that software serve the public instead of operating as a resource extraction machine for the rich and powerful.

How an open promise turned into a toll booth

To understand the grievance, the writer asks readers to remember what software was meant to do. The point of building companies, jobs and industries around it, in his account, was to empower people — and it did. Software is probably one of the most accessible and inexpensive forms of advanced technology ever placed into so many hands. With an internet connection, search, navigation, live communication, live streaming, e-commerce, fintech and health advice all become reachable, almost like everyday magic.

The equipment used to build that magic is not very different from the equipment used to consume it: one machine can develop software and use it. That was the engineer's dream — a utopia in which information, communication, market access and shared prosperity would be available to everyone. It was never reserved for coders; it included anyone who understood what software could do and wanted it to do good.

The turn, according to the announcement, came from investors chasing absurd highs rather than ordinary returns, which established businesses can already provide. Believing software carried a near-zero marginal cost, they built walled gardens to charge rent from users and converted that low starting cost into enormous profits.

Then the bill arrived. Early, shoddy builds had been rushed to market out of greed to crush competition, so maintenance costs climbed. There was still profit, the text says, but not enough. Advertising expanded next, described as the largest assault on the privacy of the general public ever attempted, and it took over the products themselves: nearly all software began, in one way or another, to serve the goal of drawing attention to advertisements. Once that mechanism was proven, it was applied to politics and made even more outrageous money. Only after that, the account goes, did the owners decide they did not want to pay the workers who kept the software alive — and turned against them.

Two kinds of loss

What users give up

For ordinary people, the result is a loss of control over daily life. Access to your own money, your own messages and your own pictures now requires a locked, always-online device that tracks location, health and similar details.

What builders give up

For the workers inside the system, the cost is described in physical terms: renting costly small apartments near offices, commuting, or doing both, only to sit through video calls with colleagues. The text argues this weakens the software they create, and therefore weakens other software as well. It is presented as a madness that takes from the poor and hands everything to the powerful.

The demands, translated into plain language

The author stresses that specifics vary with your place, habits, company and role; the goal is what stays common. Below is each demand as stated, paired with what it looks like on a normal working day.

Demand as written	What it refers to in practice
Stop forcing us to write user hostile software	Refusing to lock products down in order to extract more rent from the people using them.
Stop forcing us to use addictive algorithms	No more pushing antisocial, hate-mongering adware junk at people through feeds tuned only for attention.
Stop forcing workers to commute unnecessarily	Not twice a week, not once a week, not 11.33% of the week — simply no. Individuals and teams decide how to work; if performance is poor, existing performance management tools are enough.
Stop all forms of unnecessary micro-management	Details depend on each company and role, but the objection is supervision that adds nothing.
Stop forcing us to sell slop	No more shoving AI-generated nonsense at users as if it were a product.
Stop replacing human customer service colleagues with AI agents	Letting AI handle some repetitive work is one thing; it cannot replace a dedicated human who cares about helping customers.
Stop making us absorb the slop ourselves	When software is bad, builders need time to fix it; deadlines cannot exceed the complexity of real life.
Stop forcing growth	Some people are content with their current jobs and roles, and do not want lengthy self-praise essays written about mediocre achievements. For many, a job is a job.

Common misconceptions

• This is an anti-AI protest. Artificial intelligence appears repeatedly, but as a symptom. The same list covers commute mandates, micro-management, deadlines and career pressure.
• Everyone stops at the same moment. No. The organizer names the third week of November for himself; everyone else chooses a one week window and coordinates locally.
• There is one official demand sheet. The text says the exact list is not important and should not be universal, because different people have different needs.
• Only engineers are invited. The grievance explicitly includes people who build software even if their work involves no code — and the customer service colleagues named in the demands are not developers either.
• It is a pay dispute. The stated purpose is to send a message that control cannot continue indefinitely: if workers do not cooperate, the house of cards can fall tomorrow.

Why a scattered, quiet week can carry weight

The strategic claim is modest in form and sharp in substance. Software keeps working only because people keep keeping it alive. The announcement asks colleagues to test that dependence for a one week period during November 2026, and to treat the act as a way of saying that the industry must remain a method of empowering people rather than a tool for satisfying greedy billionaires.

Action guide

1. If you work in tech: choose the days that suit you inside November 2026, then coordinate with your colleagues — the two practical steps the announcement asks of participants.
2. Write your own version of the list. Your place, habits, company and role shape which demands actually bite.
3. Check the eight items against your last month of work. Where did you ship something you knew was user hostile, or absorb slop because a deadline outran real life?
4. If you lead a team, note that the argument about performance is not new: existing performance management tools are named as sufficient, while the dispute is about mandated office percentages and unnecessary oversight.
5. If you only use software: look closely at what your daily apps demand of you — an always-online locked device, location and health tracking, attention routed toward ads.
6. Read product announcements with the slop question in mind. When a service swaps human support for an agent, ask whether a repetitive task was automated or whether the dedicated human was removed.
7. Talk to the humans who build what you use. The 100% human-written label on this announcement is meant to be an argument in itself.

Frequently asked questions

When exactly does the strike happen?

The organizer stops for the third week of November. Everyone else is asked to select their own one week stretch in November 2026 and align with colleagues.

Is artificial intelligence the cause?

No. The text calls AI a symptom and points to older causes: hostility toward users, alienation of non-users, and now hostility toward the people who build products.

What does good mean in this context?

It is used as the opposite of extraction: software that empowers people, markets and daily life, rather than a machine for pulling resources upward.

Does the proposal ban AI at work?

It does not call for a blanket ban. It draws a line between repetitive automation, which is accepted, and AI-generated nonsense being pushed at users or human customer service colleagues being replaced.

Why those specific commute percentages?

Twice a week, once a week and 11.33% of the week are listed as examples of mandated office days the author rejects; the position is simply no, with individuals and teams deciding how to work.

Will users notice anything?

The announcement does not describe a scheduled service shutdown; the action is individual weeks of refusal, coordinated informally, aimed at the people who keep software alive.

Whether you maintain a service, answer support chats, or simply unlock a phone tomorrow morning, the question behind this call is the same: who is software supposed to serve? MyTechDailyNews will keep watching how tech workers answer it in November 2026. If your team is weighing its own week of action, or a product change feels openly hostile to the people using it, write to the General desk at hello@techdaily.com.