Anders Lie

@dexhorthy @humanlayer_dev they're trying to catch up

very cool of dario to finally give everyone else the thing that @humanlayer_dev beta testers have had for 6 months - respect! very tasteful!

@michaelgarfield "chill beats to get your body scanned by sound waves to"

@anderslie onbeing.maxcooper.net/peace-exists-h…

A technical dive inside our new "Midjourney Scanner"

@michaelgarfield oh hell yeah

@UnslothAI @Zai_org nobody: 2-bit GLM 5.2:

GLM-5.2 can now be run locally!🔥 The 2-bit model retains ~82% accuracy after we shrunk it from 1.51TB to 238GB (-84% size). Run on a 256GB Mac or RAM/VRAM setups. GLM-5.2 is the strongest open model to date. Guide: unsloth.ai/docs/models/gl… GGUF: huggingface.co/unsloth/GLM-5.…

@tugot17 Huge untapped market of ppl looking to reshape their ears into a kind of folded down doggy ear shape

Startup: yes we have a strong PMF The PMF in question:

@RasputinKaiser the guy knows it cooked, it doesn’t need to look at that shit

@anderslie jesus christ I didnt realize it didn't have vision. It was doing pretty fire on my tests

Actual footage of GLM 5.2 cooking at design even though it literally has no vision capability

@sgl_project Like peanut butter and jelly

Try it with SGLang (your preferred inference😁)!

@STUD_MAN_X @FFmpeg ofc

@anderslie How you are doing this? remotion?

@wesbos Introducing: nun

It’s bun backwards

@voratiq the student hath become the teacher

GLM 5.2 high just won head-to-head against Opus 4.8 xhigh and GPT 5.5 xhigh The task was a tricky performance optimization in an internal code-analysis product First time we've seen an open-weight agent outperform the top closed agents Very interesting result...

Code slop has been a huge problem since AI coding picked up and yet no one really knows how to tackle it. Great to see @dexhorthy taking a big swing at it

@dexhorthy Hell yeah looks awesome, been exciting to see the journey! Time to end slop

At HumanLayer, we’re on a mission to solve the AI slop code problem. In 2025 we open-sourced our Research, Plan, Implement framework, now deployed inside fortune 500s like Block and Uber - places where shipping slop is just not an option And that was just the beginning. Today, we’re opening access to HumanLayer - an Agentic IDE, collaboration platform, and building blocks for your software factory. HumanLayer enables engineers solving hard problems in complex codebases to: > move 2-3x faster across the entire SDLC (not just coding) > maintain rigorous standards for system architecture and program design Hundreds of engineers at companies of all sizes are already using HumanLayer to ship fast without sacrificing quality. I'm excited to invite you to try humanlayer today at humanlayer.com, and I'm even more excited to see what you build. @0xblacklight and I are deeply grateful to our team, our customers who give us so much incredible energy and feedback, our investors who have always been in our corner, and our friends and family who have supported us along this crazy journey if you're a staff or principal engineer trying to make AI coding work at scale for your team, we'd love to hear from you as @swyx likes to say - let's make this the year of no more slop

@dexhorthy I was thinking abt this, I feel like there should be a functional spec which defines observable requirements but then also a quality/standards spec which defines internal requirements, both must be enforced to have functional+maintainable code

there's a new word i'm hearing a lot in the most frontier-pushingest coding-agent builders: _program design_ for even the best agentic coders trying to maintain code quality, we've all seen it - you come up with something to build - you research the codebase, riff with the agent, align on what the end state looks like - you (or the agent) breaks it down into tasks for individual agents / context windows - you rip the implementation - the code works or is close to working - and it follows your spec to the letter but the code itself is still trash - poorly factored methods - leaky abstractions - tramp data - overloaded interfaces - try catch, useEffect, global variables everywhere I thought models would catch up, or that this wouldn't matter - that if we stayed in spec-land, understood the high-level architecture, and tokenmaxxed hard enough, we would be able to skip code review and just stay shipping doesn't seem to be working out that way I have seen agent-owned codebases spin up out of nothing... ...and I have seen them collapse into rubble within 6 months now there's something to be said about "skate where the puck is going"... ...and I can't tell you what tomorrows models will be capable of but I *can* tell you that *today*, models are mid-to-bad at program design you can solve some of this with memory / agents.md, but the scope of program design is massive. - entire companies have been built to help you implement it - books, classes, and professions have spun up around it are you building something to last? Or are you slinging more slop on the pile? anyways, thats the post, stay tuned for a fun announce tomorrow y'all 🙂

@NathanFlurry It’s also way harder to RL “make code changes that will make this project easier to build with for the next several months” vs “make the test pass”

llms are trained to get the job done fast at the cost of technical debt it's not an intelligence issue imo, it's an intentional optimization the market for "ship code cheaply" is bigger than "write perfect code at any cost" it's a story as old as time

@NathanFlurry @EffectTS_ one, of, us. one, of, us.

If you write @EffectTS_ for agents or realtime, we've been cooking: Effect gives you incredible primitives for stateful apps, but they live and die with one process. Now with the Rivet SDK, your Effect code can run as a Rivet Actor: a long-running, lightweight process.

@samgoodwin89 Very useful if actually works, a lot of cases where there’s dangling resources that are annoying to clean up. Though I hope my clanker would not think to give this one a go..

You probably don't need this feature, but I certainly do: `alchemy unsafe nuke` Will "nuke" your cloud accounts by deleting every resource. Have fun 💣

@csparks1919 @0ximjosh ohhhhh

@anderslie @0ximjosh objects that are durable duh

okay you got me. Durable objects are sick

@herdrdev this looks very cool, reminds me of obsidian plugin ecosystem - simple baseline, customizable from there

herdr 0.7.0 is out, and it's a major one: it introduces plugins! the idea is simple: herdr stays lean, and everything custom gets extended through plugins. shareable, scoped, built however you want, to fit your own flow. with this release we're also shipping a few examples of what the plugin system can do. first up: a telegram plugin. herdr already controls your agents and knows their status, so the plugin just hooks into agent events and pings telegram the moment one needs you. notification lands → `herdr --remote` or ssh from your phone → straight back to the agent that needs you.