What I learned:

"Code is cheap, judgment is scarce" is the consensus bet - The single loudest claim from people inside AI-heavy work right now is that writing code is no longer the moat - the judgment around it is. Towards Data Science puts it bluntly: the engineers thriving "integrated AI into their workflow without surrendering their judgment," and the parts requiring "wisdom, context, and taste" became more valuable, not less. The Communications of the ACM calls this a "seniority-biased" shift - AI disproportionately amplifies engineers who already have systems judgment, architecture taste, and operational intuition, and widens the gap between people who can design systems and people who can only type code.

The job is becoming "delegate, review, own" - and reviewing is the skill - Practitioners describe the day-to-day flipping from authoring first drafts to validating AI output. Per CIO, engineers now spend less time on foundational code and more orchestrating "a dynamic portfolio of AI agents," with the operating model converging on "delegate, review and own." On Reddit, the anxiety underneath this is concrete: a r/cscareerquestions thread asking what employers actually mean by "experience with AI agents" in job listings shows people scrambling to figure out which version of the new skill set is the one being hired for.

Context and problem framing are what people are explicitly retraining into - The bet that comes up over and over is not a tool, it's a meta-skill: knowing what to ask and why. The New Stack names "context - the gap between what engineers carry in their heads and what AI can understand" as the real 2026 bottleneck. A widely shared Medium piece argues the AI skills employers want "have almost nothing to do with writing code" - critical thinking, judgment, problem framing, and refining AI-generated output. The career math reinforces it: per PwC's 2026 AI Jobs Barometer, workers with advanced AI skills earn 56% more than peers in the same role, and "professionalised" jobs grow twice as fast with 42% higher wage growth.

"Taste" and intent are the creative-side moat - For design and product people, the bet is taste - the thing that survives because AI generates possibilities but struggles with intent. The AlphaBytes essay "Taste is All You Need" argues a generated interface "can look polished while quietly missing emotional nuance, cultural context, brand personality, or strategic clarity." Tom's Guide frames the winners as "critical users" who know when to trust the tool and when to take back the wheel.

The grounded skeptics: tool vs. crutch, and who actually gets retrained - Not everyone is betting on a clean upgrade. A r/artificial thread debating whether people use AI "as a tool or as a replacement for thinking" captures the worry that the safe skill - judgment - is the exact one that atrophies if you over-delegate. And a sober YouTube explainer from "AI Took Our Job" cautions that AI "is breaking down the individual tasks that make up your day" rather than replacing whole roles, projecting up to 30% of work hours automatable by 2030, and notes that per a 2025 survey "only 40% of retrained workers actually found new roles in emerging tech fields" - a reminder that betting on a skill and successfully landing in it are not the same thing.

KEY PATTERNS from the research: 1. Judgment beats output - "Code is cheap. Engineering judgement is now the scarce resource," per Towards Data Science 2. The new operating model is delegate-review-own, with reviewing AI output as the load-bearing skill, per CIO 3. Context and problem framing are the explicit career bet - the bottleneck is what's in your head, not the model, per The New Stack 4. AI skills pay a measurable premium: +56% wages, jobs growing 2x faster, per PwC 5. Taste and intent are the creative moat - polished output still misses nuance and strategy, per AlphaBytes 6. The dissenters worry the "safe" skill (judgment) erodes if you treat AI as a thinking replacement, per r/artificial

What I learned:

Meta became the flashpoint of the bossware backlash - In April Meta quietly installed mouse-and-keystroke tracking on every work device, telling staff its "models need real examples of how people actually use them - things like mouse movements, clicking buttons, and navigating dropdown menus." Employees revolted: they posted protest flyers in conference rooms and on vending machines, circulated petitions, and openly branded the company an "Employee Data Extraction Factory," per @v_shakthi. After weeks of staff revolt Meta retreated, agreeing to let workers "pause" tracking for 30 minutes when something is "personal," per Inc. - though full opt-out is limited to remote workers with bandwidth concerns and those handling sensitive material.

The tracking goes far past "are you at your desk" - What set Meta's workers off was scope creep: the tool also logged code changes, computer sleep/wake cycles, and URLs copied to the clipboard, and reportedly chewed through some employees' entire monthly home-internet data allowance in days, per The Cool Down. That matches what the broader monitoring market now sells: vendors openly advertise "AI-based productivity scoring" that "analyzes patterns of activity, task completion, idle time, and engagement levels to generate real-time productivity scores," per People Managing People, and a new class of tools that monitor employees' AI usage itself, per Hubstaff.

Workers describe getting scored and written up by software they can't see - On r/work a "got written up for poor productivity today" thread captures the daily-life version of this: being disciplined against a metric the worker had no visibility into. It lands inside a wider 2026 mood across r/antiwork and r/recruitinghell where the dominant feeling is that employers want maximal extraction (one PwC-analysis thread on entry-level roles "with senior-level skills in the age of AI" pulled 2,166 upvotes) while offering minimal trust - the same trust gap surveillance widens.

The pushback is shifting from grumbling to organized refusal - The clearest signal is that resistance now has leverage. Cornell research found AI-specific monitoring produces more dissatisfaction and resistance than human oversight, per SHRM, and survey data shows roughly half of employees would quit over intrusive monitoring while 24% would take a pay cut to avoid it, per ExpressVPN. That quit-and-compare behavior is now reshaping retention: workers in AI-heavy orgs are more likely to leave and to grill employers about automation in interviews, per Metaintro, and organized labor is picking it up, with the AFL-CIO convening a "Workers First AI" summit demanding civil-rights protections.

KEY PATTERNS from the research: 1. Visible collective action works better than individual evasion - Meta only blinked after flyers, petitions and forum campaigns, not after quiet mouse-jiggling, per @v_shakthi. 2. The "it's for training our AI" justification is the new trust-destroyer - reframing surveillance as model-training data was the specific trigger for Meta's revolt, per HR Grapevine. 3. Quitting is the most-cited form of pushback - ~half would leave and 24% would take a pay cut to escape monitoring, per ExpressVPN. 4. Being scored by an algorithm stings more than by a human - AI monitoring uniquely raises dissatisfaction and turnover, per SHRM. 5. Scope creep is the recurring complaint - clipboard URLs, sleep/wake cycles and home-bandwidth drain turned a "productivity" tool into a privacy fight, per The Cool Down.

What I learned:

Epic just blew the category open by open-sourcing Lore - The single biggest 30-day story is Epic Games open-sourcing Lore at State of Unreal 2026, a next-generation version control system built specifically around huge binary assets. It started life as Unreal Revision Control, already ships inside Unreal Editor for Fortnite, and is now MIT-licensed - a deliberately permissive license meant to pull studios off Perforce. Per The Register, it is a centralized, content-addressed VCS designed from the ground up for large files and easy enough for 3D artists, not just engineers, and the EpicGames/lore repo went public alongside UE5.8 and a UE6 roadmap.

The core reason plain git fails is merging, not just file size - The community keeps correcting the "git is just bad with big files" framing. The real wall is that binary assets - textures, meshes, audio, cutscenes - cannot be merged. Whoever commits second silently overwrites whoever committed first, so you need exclusive file locking, which git does not support natively. As @kidtsang put it on X, "it's not just about file size; the way we version control assets needs a rethink... collaboration on large binaries requires smarter tools." The Bugnet Blog makes the same point: with no automated merge for binaries, file locking and clear ownership are the whole game.

Git LFS is the indie floor, Perforce is the AAA default, and both have sharp edges - The consensus stack is unchanged at the extremes: Git+LFS for small-to-mid indie teams, Perforce (Helix Core / P4) for large studios with massive libraries, per Anchorpoint. But LFS reportedly chokes past roughly 50GB repos and 5GB files with limited locking, while Perforce "works when it works" but is gnarly enough that teams often staff a dedicated tools engineer just to keep the server alive, per the same gamedev discussions surfaced on r/unrealengine.

Cloud-native challengers are smelling blood - Diversion is positioning as the modern Perforce replacement, and its founder showed up in the r/unrealengine Lore thread predicting "more game devs / studios will leave Perforce/Git for either Lore or Diversion." Per Diversion, it offers exclusive file locks, branch creation in seconds versus minutes on big Perforce streams, sync that scales to 400,000+ files per minute, and up to 70% lower total cost of ownership - and it claims to be officially recommended by Epic with the top-rated VCS plugin on FAB.

KEY PATTERNS from the research: 1. The headline event is Epic open-sourcing Lore, an MIT-licensed VCS purpose-built for large game binaries - per The Register 2. Plain git fails on binaries because they can't be merged and git has no native file locking, not merely because files are big - per Bugnet Blog 3. The practical split stays Git+LFS for indies, Perforce for AAA, with LFS hitting limits around 50GB repos / 5GB files - per Anchorpoint 4. Perforce's hidden cost is operational: studios often need a dedicated tools engineer to keep it running - per r/unrealengine 5. Cloud-native challengers like Diversion are pitching seconds-not-minutes branching, file locks, and up to 70% lower TCO as the post-Perforce path - per Diversion