Lazy work used to mean too little output. Now, with AI, it often means too much and more work for everyone else. @tobi call it "slop grenades." A "Slop Grenade" is when you let AI produce the work and pass it on without adding any value (including checking it). Someone else has to wade through it, catch the mistakes, and clean up the mess. You save time and look productive but someone else pays for it.

🚨Mikel Arteta tried to hug the referee but was given a yellow card xitter.cf/fbtl_topcee/status/209…

Compound Engineering is what happens when agents write 100% of the code. At @every, engineers don’t type code anymore. They orchestrate agents. The shift: - Coding is no longer the bottleneck - Planning, review, and learning loops matter more than syntax - Each feature makes the next one easier to build The 4-step Compound Engineering loop: 1.Plan – Agents research the codebase + best practices and produce detailed plans 2.Work – Agents write code, tests, and iterate using real app simulations 3.Assess – Humans + AI review from multiple angles (security, performance, overbuild) 4.Compound – Lessons learned are stored so future agents never repeat mistakes Complexity still grows, but so does the AI’s understanding of the system. Result: - One developer can now do the work of ~5 - Products run by single engineers serve thousands of users - New hires instantly inherit years of institutional knowledge Engineering is no longer about writing code. It’s about designing learning systems that compound. — Thanks @danshipper and @kieranklaassen for sharing your approach. So much to learn and takeaway from this compound engineering approach.

And that water is destroyed, right? It’s annihilated, leaving our ecosystem forever.

No one can defeat Unitree G1. Watch till the end, as G1 evolves wildly, performing extreme somersaults, continuous side flips, and other gravity-defying maneuvers.