Click any tag below to further narrow down your results
+ coding
(1)
+ benchmarks
(1)
+ programming enjoyment
(1)
+ hacker news
(1)
+ chris kiehl
(1)
+ junior developer training
(1)
+ software engineering
(1)
+ coding agents
(1)
+ human advantage
(1)
+ codebase knowledge
(1)
+ technical writing
(1)
+ deep atlas
(1)
+ workflow orchestration
(1)
+ data modeling
(1)
+ alejandro aboy
(1)
Links
Thomas Wolf, a startup founder, argues that AI's strong benchmark scores don't match its limited economic impact because real work depends on judgment and agency, which benchmarks rarely measure. He ties this to a drop in entry-level hiring, since execution is the part of junior work AI handles best, and that junior work is where people usually build the judgment that later makes them senior.
- A Stanford analysis found employment for workers aged 22–25 in the most AI-exposed occupations fell about 6% between late 2022 and mid-2025, while older workers in those jobs gained 6–9%.
- Models now solve around 75% of real-world coding tasks on SWE-bench, yet the Remote Labor Index shows the strongest agents succeed on only about 2.5% of paid freelance projects.
- Wolf's hiring framework splits workers into execution, judgment, and agency; AI is advancing fastest on execution, so the entry layer gets squeezed first, weakening the pipeline for future senior people.
The author argues that making software cheap is likely to mean much more software, as Jevons predicted for coal in 1865, but that whether the people who build it gain depends on what the new tool does to their specific job. Historical cases like farming, light, bank tellers and telephone operators show the paradox holds for output but can fail for workers.
- Jevons argued in 1865 that efficient engines would increase coal use, and that cheaper products would widen employment, which the coal boom bore out for about fifty years before output collapsed.
- The price elasticity of demand decides the outcome: food (elasticity roughly 0.27 to 0.81) saw the savings leave the industry, while light behaved as if elastic and use rose thousands of times over.
- Bank tellers survived ATMs because branches multiplied, but the job shrank from 600,500 in 2008 to 339,200 in 2025 once mobile banking removed the need to visit, and telephone operators lost 50 to 80% of their jobs almost immediately after mechanical switching.
- Software output already looks like coal in 1865: Google's token processing rose about 330 times in two years, and new repositories and app submissions climbed sharply.
Elliot Morris argues that prototypes used to force engineers to communicate clearly, surface real problems, prove competence, and engage with reality, but LLM-built prototypes break most of those benefits. He thinks the useful future prototype is a sharp, single-thesis experiment rather than a big, sprawling demo.
- Prototypes once delivered four bundled benefits: clear communication, early problem discovery, a visible competence signal, and forced contact with reality. LLM prototypes keep only the first of these reliably.
- LLM output tends to drift toward a generic "average" answer, so the builder can end up communicating something they didn't intend without noticing.
- Experienced engineers make rougher, smaller prototypes because they test one narrow thesis. Morris suggests the key question is now "what specifically does this prove, and why should I care?"
A mother who works at fast-growing AI company Lovable argues that 996 schedules (9am to 9pm, six days a week) are a bad strategy, both for the people working them and for companies that filter out parents and others with real lives outside work. She says boundaries only hold if companies build cultures that protect them and if people stop overriding their own limits.
- Working 996 gets treated as a badge of honor in AI companies, but she argues it confuses long hours with ambition and talent.
- Companies that require 996 as the default borrow against employees' future health and relationships, and that cost never shows up on the balance sheet.
- Excluding parents and caregivers narrows the range of perspectives building the product, and constraints outside work often make people sharper at prioritizing.
Chris Kiehl pushes back on the gloom around Hacker News, arguing that while AI has changed the economics of paid programming, coding for its own sake is still worth doing. He describes his weekend projects, a buggy Breakout clone, Java type-safety experiments, and a frustrating dive into recursion schemes, to show that learning hard things is rewarding without any business payoff.
- Programming for work and programming for enjoyment are different things; AI changing the value of hand-written code at a job doesn't remove the reason to do it for fun.
- Kiehl admits his projects have no clear payoff: a bad Breakout clone, Agda-inspired Java experiments, and recursion schemes that left him unsure what they were even good for.
- The "there is no point" feeling comes from constant exposure to doom-heavy online discussion, and it fades once you log off.
Jake Goldsborough argues that AI coding agents aren't killing software engineering—they're freeing engineers from tedious mechanical work so they can focus on the actual problem-solving that defines the craft. The hard parts that never mattered (regex wrestling, syntax memorization, build system incantations) are disappearing, but the work that requires real judgment and responsibility remains.
- The difficult parts of coding—parsing edge cases, remembering obscure syntax, navigating unfamiliar codebases—were never the point; they were tolls between understanding a problem and solving it, and removing them doesn't diminish engineering skill.
- Agents handle syntax and scaffolding faster, which lets engineers explore domains that were previously too expensive (rewriting programs in different languages, understanding unfamiliar systems, testing experimental ideas), actually tightening the learning loop rather than replacing it.
- The real shift is architectural: engineering moves from "produce every character by hand" to "direction, judgment, verification, and responsibility," and the actual risk isn't that the work disappears but that companies cut people, generated code creates failures at scale, and the junior-to-senior training path collapses.
As AI models get better at coding, engineers need to stop pretending it's not happening and instead identify what they can do better than the models—mainly deep knowledge of their specific codebase and the ability to write clearly about technical decisions.
- AI models fail on "errors of ignorance" (not knowing which module to use, missing company conventions) and "errors of paranoia" (over-engineering simple systems), mistakes only caught by someone deeply familiar with the actual codebase and willing to confidently disagree with the AI.
- LLMs are paradoxically getting worse at writing even as they improve at coding, because writing quality can't be automatically verified and labs prioritize capability over communication—making human-written technical docs increasingly rare and valuable.
- Being a "meat proxy" who just runs prompts through AI and submits the output is worse than not using AI at all, since you're providing zero value and will be replaced once those workflows get automated into enterprise tools.
This article discusses a live session with Alejandro Aboy, a Senior Data and AI Engineer, about the evolving role of data engineers in the context of AI. Alejandro emphasizes that strong data engineering skills, particularly data modeling and orchestration, are crucial for successful AI work and shares practical steps for integrating AI into existing data workflows.
- Data modeling accounts for roughly 80% of the skill transfer from data engineering to AI engineering, according to Aboy.
- Good orchestration/workflow design can handle most AI tasks without needing complex agents.
- Precise column/model descriptions function as prompts for AI, so metadata and documentation quality directly determine AI performance.
- AI still lacks common-sense judgment (illustrated by a debugging agent missing context), so critically reviewing outputs rather than accepting them blindly remains essential.
Career-Ops is an AI-driven tool that simplifies job searches by evaluating offers, generating tailored CVs, and tracking applications in one place. It uses a structured scoring system to help users focus on high-fit opportunities without spamming companies. The system is customizable and designed for efficiency.
- Creator personally evaluated 740+ job offers and generated 100+ tailored CVs using this system before landing a Head of Applied AI role
- Uses an A-F scoring system across ten weighted dimensions to rank job fit and cut wasted applications
- Automates job scanning across Greenhouse, Ashby, and Lever for 45+ companies with batch processing of multiple offers at once
- Generates ATS-optimized CVs as PDFs tailored to specific job descriptions, run through Claude Code with a dashboard for tracking applications
Deep Atlas offers an intensive curriculum designed to compress months of AI and machine learning education into just weeks. With hands-on projects, community learning, and successful alumni, participants can quickly gain the skills needed for a career in AI.
- Deep Atlas compresses months of AI/ML education into a few weeks through an intensive, project-based curriculum.
- The program emphasizes hands-on projects and community learning as core to skill-building.
- Alumni outcomes are cited as evidence the accelerated format leads to real AI career placement.