Stories

AI is supercharging fake work

Article news.ycombinator.com

AI is supercharging fake work

As anyone with an internet connection knows, there’s been a lot of buzz about how AI is going to reshape the workforce for the past 3 years and layoffs due to “AI” have already started, the most severe of which came last week as Block announced they were chopping off 40% of their workforce for what sounded more like the potential that AI could replace workers as opposed to it actually being able to. There has been a (in my opinion) healthy dose of skepticism regarding the claim that AI is going to make us more productive and these productivity gains are going to put people out of work. I think this skepticism has been felt by many of whom work in tech companies where AI is literally being force-fed to us, and I wonder how much of this skepticism would apply to other companies and the workforce in general. OK, so…

1. Many (possibly most) people at major tech companies spend most of their time doing essentially fake work, which may or may not be actually negatively impacting productivity. Think time spent in pre-meeting meetings for the many layers of WBRs and MBRs on the product side and over-engineering workflows to get promoted on the tech side.* There are many reasons that people have speculated for why these kinds of jobs exist but in my experience, this basically just comes down to gaming the optics of productivity. True productivity is nearly impossible to evaluate so proxies are used and proxies are inevitably gamed (lines of code, meeting attendance, how many people report to you, etc.).

2. AI is really good at generating fake work. We’re starting to see some of the repercussions of the tech-side of AI slop as Amazon apparently is formally addressing some of the engineering issues it’s causing. but on the non-tech side, there’s endless amounts of doc slop and increasingly Slack slop, all filled with emoji-bulleted lists and em-dashes. The maddening part of doc slop is that you really have no idea what the person intended to say so you can never be sure you’re truly responding to them or just what they thought looked good. I suspect a good amount of performance “reviews” now are just managers doc-slopping their way through and stumbling through an oration of whatever ChatGPT spit out.

3. Whether a company benefits from AI comes down to whether the enhanced fake work undercuts the enhanced real work. At companies where personal advancement comes through optics, meeting-scheduling, public-Slack-channel posting, “visibility”, etc. the doc slop and Slack slop are going to be absolutely out of control. These companies are likely rent-extractors that face limited competition, are public, and don’t have much innovation left. They’ve probably been absorbing a hefty amount of fake work for years. I don’t think there’s any way AI helps these kinds of companies and it will likely make it hard for anyone doing real work to stand out and get rewarded. AI is never going to enhance productivity at these places, because people were never really trying to be productive to begin with. On the other hand, companies where visibility/optics/fake work isn’t rewarded but boosting hard metrics like revenue or signing new clients is, AI could help and probably actually replace people. I can’t deny that AI has some real productivity-enhancing abilities IF you are actually trying to enhance productivity, I’ve seen this firsthand.

The logical implication of this is that AI’s overall impact on the workforce is really going to come down to the composition of fake work vs. real work that already existed. In my mind, the economy was never set up to benefit from anything truly productivity enhancing because the amount of fake work so drastically outweighed the amount of real work to begin with.

* The latter ironically leads to real work, which is fixing the over-engineered workflows that fail constantly because the engineer that over-engineered them left after he got promoted for over-engineering.

Discussion 10 comments · 13 points · rxm233 · 2026-03-12
Open on HN
Loading the discussion…

Domain filters

Stories from these domains are hidden from every list. Subdomains match too: blocking substack.com also hides danluu.substack.com. Type a domain, or paste a link to block its site, and press Enter.

New collection

Delete this collection?

About YAVCHN

YAVCHN is a reader for Hacker News and Lobsters, with articles and discussions in separate windows or Classic pages.

Created by Paul Parks and built with PUDL.

YAVCHN source code on GitHub

Privacy policy · Terms of use

Help

Keyboard

j / k
Move down and up the story list. The arrow keys scroll whatever has focus.
Enter
Read the marked story in the article reader.
[ / ]
Read the story above or below in the list, in the same article reader. Back returns to the story you came from.
p
Pin or unpin the marked story, which keeps it in Pinned.
n / N
Move to the next or previous top-level comment in the window in front.
c
Collapse or expand that comment.
f
Hide or show the story list.
Esc
Close a menu or this help.
Access key m
Go to the menu bar. Most browsers take it with Alt on Windows and Linux, and Safari with Control and Option.
?
Show this help.

Windows

Each story opens in a window holding its article above its discussion; drag the bar between them to share the room differently. A window can be moved by its title bar, resized from any edge, snapped to a half or a corner by dragging it there, maximised, or minimised to the bar at the foot of the page. Use Window > New reader window to open an empty reader, or Story > Open in new reader window to open another reader for the current article. Docked readers keep their articles when you select another story from the sidebar. Minimized readers can be restored and reused for their site. A window's Previous and Next buttons read up and down the list in the same window.

A link in a comment or an article to another Hacker News or Lobsters thread opens that thread in a window too. A link to a single HN comment opens the comment above its replies.

While a story's window is in front, the Story and Discussion menus in the menu bar hold its commands: pinning, Previous and Next story, sorting, collapsing every thread, jumping to the first new comment. Each window also remembers where you were in its article and discussion, so a reload, or Back to a story that Next took you past, finds your place again. Closing a window forgets it.

The whole arrangement lives in the address, so a bookmark or a shared link brings it back, and Back undoes the last change. Moving between Hacker News, Lobsters, their lists, Pinned and Find changes only the list, and leaves the windows open.

The list

The pin at the start of a row keeps the story in Pinned, and the cross at its end hides it. Pinned can be narrowed by words in the title, site or author, by source, and to the stories you haven't opened yet, and ordered by when you pinned them, by points or by comments; the filters are part of the address, so a filtered view can be bookmarked. Scroll past the end of the list to load more. Domain filters, in the View menu, hide every story from a site.

Collections are named lists of stories. Story > Add to collection files the story in front into one or more of them, and the Collections feed shows them all or one at a time; the menu that chooses collections also creates, renames, and deletes them. A note is your own text on a story. Choose Add note in a story's toolbar to write one; it saves as you type. Rows with a note carry the note mark, and the Notes feed lists every noted story and searches the text of your notes.

Browsing view

View > Windowed and View > Classic select the browsing view and save your default in this browser. Window view reuses a reader for each feed. Classic view opens stories and applets as pages. Open as a page is a one-off action that does not change your saved default. Use the Windowed selector to return an article to a window. Direct page links always open as pages.

Applets

The Applets menu in the menu bar holds three tools, each a window of its own. Replies to me takes your Hacker News user name and lists the replies to your last thirty comments and stories, checking again every three minutes while it is open, and marking what is new since you last marked them read. Look up a user opens a profile on Hacker News or Lobsters, with their submissions and recent comments, as a commenter's name in any discussion does; the bar at the top of a profile looks up someone else in the same window, and Back returns to the one before. Who is hiring? filters the posts of HN's monthly hiring threads by the words you type.

They read only what the sites publish to everyone, so none of them asks for a login, and your user name stays in this browser anonymously and is included in retained applet state when signed in.

Find

Find takes any link and lists every time it was submitted to Hacker News and Lobsters, so you can read each discussion of it.

About

YAVCHN never sees your Hacker News or Lobsters login. The discussion is fetched from each site's public API; to vote or reply, follow the link above the discussion, or the arrow beside a comment, to the source's own site. Without a YAVCHN account, your data stays in this browser. When signed in, pins, collections, notes, blocked domains, and retained reading state are stored with your account and synchronized across devices. Hidden stories and layout stay in this browser. The privacy policy has the details.

Open source: github.com/paulmooreparks/yavchn. Built with PUDL.