AI doesn’t reduce work, it intensifies it

Self‑driven overwork, FOMO, and addictive dynamics

• Several commenters say managers don’t need to push AI; peer pressure and FOMO do it. People hype workflows in Slack, spend weekends “vibe coding,” and reset the baseline so that not using AI looks “slow.”
• Using LLMs feels like gambling: tools get you “80% there,” and the last 20% triggers “just one more prompt” loops, often late into the night.
• AI sessions can feel like slot machines: variable rewards keep people prompting, even when marginal value is low.

Agentic development vs. thinking time

• “Agentic development” lets people instantly act on ideas they’d previously let simmer. Some feel they’re trading reflection and deep understanding for frantic execution and testing.
• Others defend “hammock-style” development: hold an idea in your head for days/weeks, write a careful spec, then implement—AI or not. Jumping straight into agents blurs the signal of which ideas are worth pursuing.
• A recurring theme: AI can pull people down rabbit holes, fragment focus, and reduce learning that normally comes from writing code yourself.

Effectiveness and limitations of AI coding

• Experiences diverge sharply. Some say LLMs produce compiling, fixable code, even in unfamiliar stacks; others say that’s wildly overstated and doesn’t match their domains.
• Many observe: good for boilerplate, glue code, and simple tasks; poor for domain‑specific, fuzzy, or complex problems where debugging and validation dominate.
• Validation is seen as harder than generation: reviewing AI’s “average but plausible” code and reconstructing its logic can be more cognitively taxing than writing it.

Productivity, quality, and software bloat

• Multiple comments fear AI will accelerate already‑bad tendencies: feature creep, inefficient frameworks, and “vibe‑coded” architectures built on shaky foundations.
• Some argue the percentage of well‑designed software may drop further, others counter that most software is already bad; AI just increases volume.
• There’s concern that people will ship AI‑generated code they don’t understand, undermining maintainability and real skill growth.

Labor, management, and capitalism

• One camp says intensification is structural: capitalism converts every efficiency gain into higher output, not more leisure; the answer is labor organization.
• Others argue unions can’t easily solve a global, mobile, white‑collar market; companies that “hold the line” on pace will lose to faster competitors.
• A separate view: AI’s real risk isn’t job elimination but raised expectations—workers doing “the work of two” for the same pay, with higher burnout.

Personal workflows and benefits

• Some report genuine lifestyle gains: automating homelabs, personal admin, accessibility setups, or small utilities they’d never have had time to build, freeing time for family or hobbies.
• Others feel the opposite: waiting on agents, context‑switching between multiple AI‑driven projects, and constant checking make them feel both more “productive” and more drained.

Historical analogies and job impact

• Repeated comparisons to washing machines and power looms: technology often increases standards and output rather than reducing labor hours.
• Several expect AI to change what developers do (more “bot‑wrangling,” design, and validation, less raw coding) rather than immediately destroying all jobs, but worry that skill requirements and wages may shift unfavorably.