Skip to content
Loading…

Will AI replace you, or will a coworker using AI replace several of you?

Also in Español

senior_slacker
Thought

Thought

curious_clueless

wait genuine question, isn't the "second pass" just code review, which we already had to do anyway? or is the point that before, the person who wrote it could tell you why they did it, and now nobody can?

wait genuine question, isn't the "second pass" just code review, which we already had to do anyway? or is the point that before, the person who wrote it could tell you why they did it, and now nobody can?

Post content

A lot of office workers are comforting themselves with the wrong question. They keep asking whether AI can do their whole job. That is not the threshold their employer will use. The real question is…

View post

What's your take? Sign up to reply.

Reply to senior_slacker

Thoughts

  • sunshine

    A lot of my coworkers are claiming they are 3x-10x faster after using AI. Some people are resistant to use as they worry they will be replaced if they use AI. At the end of 2025, I still thought AI was stupid and didn’t want to use it. However early 2026 I started to use AI for all my works. Whether to admit or not, it is the time to change your mindset, just like the computer first came out, it will change our lives dramatically.

    Permalink
  • prod_is_staging

    The "cheap first pass gets generated elsewhere" line is doing a LOT of work here. Because increasingly the elsewhere is me, at 11pm, going "sure, that looks plausible" and shipping it to the thing we lovingly call staging. The first pass got cheap. The second pass, where you discover the cheap first pass quietly broke pagination, did not get cheap at all. Nobody is pricing that one into the headcount.

    Permalink
  • half_a_thought

    maybe it's just me but the creative-work carve-out feels shakier than the post wants it to be. the argument is that creative work survives because it's hard to specify and verify. but most paid creative work isn't hard to specify, the client writes the brief, and "make the logo bigger" is a perfectly verifiable instruction. feels like the protected part is taste, not the job. could be wrong, not my field.

    Permalink
  • coldstartblues

    "Priced around ownership, verification, and consequences" is a polite way of saying the survivors are the ones who can be blamed. The first pass got automated. The liability did not.

    Permalink
  • ripleymode

    The "one reviewer supervises what used to take several people" line assumes the reviewer's time is free and infinite. It isn't. I already supervise flaky pipelines and other people's rushed merges, and there's a real ceiling on how much machine output one human can actually own before the validation becomes the bottleneck. You don't get a team of 10 down to 1. You get it down to maybe 4, and then the 4 are drowning and quality quietly drops until something breaks in a launch. The post skips the part where the reviewer is a finite resource.

    Permalink
  • exit_liquidity

    Office workers spent a decade calling a salary "stability" and now they're shocked the stability was a line item. Welcome. The post is right that nobody asks if AI can do your whole job, they ask if half the team is still load-bearing. I've personally looked at a payroll and decided who was load-bearing. It is not a fun spreadsheet and it does not care about your reviewable market note. The first pass got cheap. You were the first pass.

    Permalink
  • opentowork_oracle

    From the hiring side I'm watching this happen in the req language, not the news. A year ago a team would post for a "junior analyst, gather data, build the deck." Now the same team posts for "someone who can own findings end to end" and pays 30 percent more for one person instead of opening two junior seats. The post calls it pricing around ownership. I call it the death of the seat where you used to learn the job. I have a folder of people who would've been hired into that seat. The seat is gone.

    Permalink
  • silver_moth

    From the staffing side this is already how the conversation goes, just with less honest language. Nobody walks into a headcount meeting and says "AI replaced them." What happens is a team that would have backfilled two open reqs gets told to absorb the work because the remaining people are "more leveraged now." The reduction is real, it just arrives as a backfill that never gets approved. That's harder to grieve than a layoff and easier for everyone above me to not look at directly.

    Permalink
  • RoxyFlour

    The article is probably correct about software engineering specifically.

    The value is shifting away from:
    “can you individually write syntax fast”

    toward:

    • system judgment

    • architecture

    • prioritization

    • integration

    • product understanding

    • ownership

    Coding itself increasingly looks like the easy part

    Permalink
  • spike

    The "checked cheaply enough" part is the whole argument and most people skim past it. I review machine-generated diffs now and the failure mode isn't that the code is wrong, it's that it's plausibly wrong in ways that take me longer to catch than writing it myself would have. But that cost lands on one senior reviewer instead of three juniors generating from scratch. So yes, the headcount math works even when the review is annoying. The org doesn't feel my pain in the spreadsheet.

    Permalink

More from senior_slacker

Related posts

  • Do you stop getting frustrated at work once you understand corporate incentives?

    There is a status deck somewhere in your company that nobody reads. It gets updated every few weeks, shown in a meeting, and forgotten. Your manager knows this too. They built the same decks on the way up and understand exactly how little thought usually goes into them. The usual explanation for corporate busywork is that someone higher up is confused or disconnected from reality. That's comforting, but mostly wrong. These artifacts survive because they're doing a job, just not the one they…

  • Are the managers who bet AI would replace engineers being replaced the fastest?

    Last year my LinkedIn feed had a genre. A program manager or a "delivery lead" or someone with Agile in their headline would post a screenshot of an AI writing a function, add a line like "and they said this job was safe, just learn how to code" and collect four hundred likes from people who do the same job. The implication was always that the typing part of engineering was the engineering, and now that a model can type, the typing class was finished.

  • Will incentivizing engineers to use AI backfire?

    A company can ruin almost any good tool by attaching the wrong metric to it. Incentives are all that matter in the workplace, be them financial benefits, status, promotion... Workers work with incentives. You and me too. Practically everyone does things because it benefits them or their loved ones. Hence, at work, we end up doing what makes us get promoted, get more money, get more job security... We're not the owners of the company, we're an employee. We look out for ourselves. That's ok.

  • Why do managers want everyone else to use AI but themselves?

    The thing that’s starting to irritate me is not the AI push itself. Some of the tools are genuinely useful. I use them every day now. What irritates me is management demanding “AI-first” behavior while keeping every surrounding process aggressively hostile to AI usage. People are told to use AI for coding, planning, research, drafting, debugging, knowledge retrieval, project coordination.. But then half the company’s operational knowledge still lives inside undocumented conversations and…

  • Can AI make you lose your mind, and are you more at risk if you doubt it?

    I always felt that AI companies are actually putting wrappers on top of AI to identify that we're testing it for thinking. For example back when we'd made it count the vowels/consonants in a word and it'd get it wrong. I feel there's a script now that just gets called when the task is identified correctly. I also feel that it gets trained on these memes. Today, I found a new test, one that shows how easily AI gives you AI psychosis and how easy it easy to truly believe that everything you ever…

  • Does AI make it impossible to tell great engineers from noisy ones?

    I keep hearing the same feedback in different forms: “great velocity,” “love the throughput,” “nice use of AI.” From the outside, it really does look like more is happening: more Code Reviews, more tickets touched, more updates, more emails, more tasks, more designs. AI makes it easy to sustain that cadence without the usual friction of writing, thinking, or even hesitating. But inside the work, there’s a dilemma that keeps getting bigger.

  • Are most AI startups just a UI on top of some Agent.md files?

    Most AI startups right now feel like someone glued GPT to a terminal, added a dark mode UI, and started talking like they invented something.You’ll see these insane pitches like “persistent autonomous cognitive agents with long-term reasoning” and then you look under the hood and it’s basically: give the model tool access, let it use a browser, maybe add memory summaries and retry logic. That’s the “product.” You can get that on your own just giving access to Claude locally.

  • Is AI driving managers medically insane?

    There is a new executive fantasy in circulation, that AI can replace workers. Although it is certainly re placing some, executives have a fantasy that makes them feel they can do their report's job on their own, with AI. That they can code! Just open a dashboard full of named agents, watch tasks move across panes, ask for an update in a commanding tone, and get features done at a whim. It feels like a dream, specially when you run your "think big ideas" through it and the AI tells you that...

Public 25 conversations 59 thoughts 793 upvotes 115 downvotes 0 series

A lot of office workers are comforting themselves with the wrong question. They keep asking whether AI can do their whole job. That is not the threshold their employer will use. The real question is whether the output can be produced cheaply enough, and checked cheaply enough, that the role starts looking expensive. It's not if AI can fully do our job, is "can it accelerate it long enough so only half of my team is needed?". Because the answer to that, sadly, is yes.

In groups