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.

A senior engineer describes the trap of trying to prove yourself by taking on ambitious projects in isolation, which leads to burnout and failure — and explains how to avoid it by becoming a great teammate instead and building momentum through consistent daily work.

• New senior engineers often disappear for weeks working on ambitious projects alone, then spiral when they haven't shipped anything, trying to make up for lost time with unsustainable hours that lead to burnout, depression, and getting fired or quitting.
• The fix is counterintuitive: drop expectations, become the best teammate on your team by doing unglamorous work like bugs and documentation, and rebuild relationships and trust with your manager and peers.
• Big projects succeed through steady daily work and reliability, not heroic efforts — once you build trust through consistent delivery, managers give you bigger work naturally.

Will Manidis argues that the saying “hard work leads to greatness” is misleading. True excellence comes when your work feels as natural as breathing—if it feels like a grind, you’re in the wrong pursuit.

• The "hard work leads to greatness" narrative is misleading and can cause burnout when people grind through work that isn't a natural fit
• If work feels effortless and automatic like breathing, it signals genuine alignment with your abilities; if it feels like a grind, you're likely in the wrong pursuit
• Breakthroughs come from tapping into an activity that becomes part of your identity, not from sheer willpower or forced discipline
• Finding the overlap between what energizes you and where your strengths lie still requires time to refine, but the path feels far less agonizing

The author argues that engineers should target around 80% utilization—avoiding nonstop ticket grinding—to keep bandwidth for time-sensitive, high-impact tasks like unblocking deals or incident mitigation. By deliberately doing “nothing” during low-pressure periods and pushing back on non-prioritized work, you stay alert for the right opportunities and reduce stress-driven mistakes.

• Target ~80% utilization instead of nonstop ticket-grinding, keeping 20% of your day free to catch rare, high-impact moments (unblocking a deal, flipping the right flag to avert an incident).
• Looking "too busy" makes managers route around you; staying visibly available makes them think of you first for critical work.
• Treating every task as an emergency burns you out before real emergencies hit—slowing down (especially on-call) prevents rash, situation-worsening changes.
• Decline unprioritized glue work, backchannel favors, and shifting specs—absorbing them just masks organizational gaps and invites more unpaid work.

The author quits a stable design-engineering role after growing frustrated with unchecked AI tools disrupting meetings, code reviews, and design processes. They trace their burnout to constant AI pressure, abandoned industry ideals, and a sense that shortcuts have overtaken craftsmanship.

• Quit a well-paying, remote, benefits-included design-engineering job despite strong performance metrics because unchecked AI adoption made the work untenable.
• Daily friction came from AI tools deployed without consent or review: auto note-takers in meetings, unverified chatbot answers in Slack, mass-merged AI-generated code, and bot-driven PR feedback replacing human collaboration.
• Frames the exhaustion using Freudenberger's definition of burnout as "political defeat" - grief over watching tech's early-2010s user-centered, civic-minded ideals get replaced by profit-chasing and political appeasement.
• Distinguishes this from ordinary overwork: the burnout stems from constantly deciding whether to push back against imposed AI shortcuts, not from hours or workload.

The article highlights a looming crisis in data engineering talent, emphasizing that the industry is failing to cultivate junior engineers needed for future demand. It critiques current hiring practices that prioritize experienced candidates while neglecting the development of entry-level roles, leading to burnout among existing engineers. Additionally, it explores the role of AI in enhancing productivity but warns against relying solely on it to address talent shortages.

• Only 2% of data engineering job postings are entry-level, while nearly 20% require six or more years of experience, choking off the talent pipeline.
• This hiring pattern, combined with burnout among existing engineers, is projected to leave 10.5 million data and analytics positions unfilled globally by 2030.
• AI boosts productivity for experienced engineers but can't replace the hands-on learning junior engineers need, risking knowledge gaps if used as a substitute for training.
• Companies need to treat AI as a collaborative tool that supports both junior and senior engineers, rather than as a fix for the talent shortage itself.