Ryan Hayes

made a hook that adds a bouncing dvd logo to claude code whenever it's thinking

Just ask for Mermaid. Done.

@GeoffreyHuntley @rayzhudev Call it “YesMiLord”

what if an coding orchestrator was warcraft 3? coming soon from @rayzhudev

@Ryan_Hecht @GeoffreyHuntley @AkkermannKris Have you added the ability to interrupt it inline while it’s generating and have it course correct? Like not stop it but just interject/send a message realtime.

@RyannosaurusRex @GeoffreyHuntley @AkkermannKris The team is definitely agreed that this is the killer feature -- besides the other things mentioned in this thread, any other specifics you think we need to do better on to realize this distinction?

so, i cannot recommend copilot cli at all at this stage. the cli is super low taste just use opencode or claude code cbf even putting up with it in its current form even though its free opus inferencing

CMD > MCP

@GeoffreyHuntley @AkkermannKris Yea this was my problem with it. It acts like the code gen is the killer feature of these headless agent tools when interaction with bash/the command line consistently and reliably is the ACTUAL killer feature.

@AkkermannKris it absolutely does not know how to use the bash tool effectively it falls for the && failure mode can’t handle special chars for file names like @

This is the best way anyway. Sometimes I want the steps for a thing outlined so it can just decide and do it well. Other times I don’t want it to think…just get goin’ on it right now with a slash command.

@GeoffreyHuntley @trashh_dev Yea, I had people telling me about it this week and I was like…wait…this has been around a while, though! Cool to see it finally get traction!

@trashh_dev hi trash, it’s me. blame me ghuntley.com/ralph six months ago. it’s only just now catching on

who the hell is ralph

Every time we've made it easier to write software, we've ended up writing exponentially more of it. When high-level languages replaced assembly, programmers didn't write less code - they wrote orders of magnitude more, tackling problems that would have been economically impossible before. When frameworks abstracted away the plumbing, we didn't reduce our output - we built more ambitious applications. When cloud platforms eliminated infrastructure management, we didn't scale back - we spun up services for use cases that never would have justified a server room. @levie recently articulated why this pattern is about to repeat itself at a scale we haven't seen before, using Jevons Paradox as the frame. The argument resonates because it's playing out in real-time in our developer tools. The initial question everyone asks is "will this replace developers?" but just watch what actually happens. Teams that adopt these tools don't always shrink their engineering headcount - they expand their product surface area. The three-person startup that could only maintain one product now maintains four. The enterprise team that could only experiment with two approaches now tries seven. The constraint being removed isn't competence but it's the activation energy required to start something new. Think about that internal tool you've been putting off because "it would take someone two weeks and we can't spare anyone"? Now it takes three hours. That refactoring you've been deferring because the risk/reward math didn't work? The math just changed. This matters because software engineers are uniquely positioned to understand what's coming. We've seen this movie before, just in smaller domains. Every abstraction layer - from assembly to C to Python to frameworks to low-code - followed the same pattern. Each one was supposed to mean we'd need fewer developers. Each one instead enabled us to build more software. Here's the part that deserves more attention imo: the barrier being lowered isn't just about writing code faster. It's about the types of problems that become economically viable to solve with software. Think about all the internal tools that don't exist at your company. Not because no one thought of them, but because the ROI calculation never cleared the bar. The custom dashboard that would make one team 10% more efficient but would take a week to build. The data pipeline that would unlock insights but requires specialized knowledge. The integration that would smooth a workflow but touches three different systems. These aren't failing the cost-benefit analysis because the benefit is low - they're failing because the cost is high. Lower that cost by "10x", and suddenly you have an explosion of viable projects. This is exactly what's happening with AI-assisted development, and it's going to be more dramatic than previous transitions because we're making previously "impossible" work possible. The second-order effects get really interesting when you consider that every new tool creates demand for more tools. When we made it easier to build web applications, we didn't just get more web applications - we got an entire ecosystem of monitoring tools, deployment platforms, debugging tools, and testing frameworks. Each of these spawned their own ecosystems. The compounding effect is nonlinear. Now apply this logic to every domain where we're lowering the barrier to entry. Every new capability unlocked creates demand for supporting capabilities. Every workflow that becomes tractable creates demand for adjacent workflows. The surface area of what's economically viable expands in all directions. For engineers specifically, this changes the calculus of what we choose to work on. Right now, we're trained to be incredibly selective about what we build because our time is the scarce resource. But when the cost of building drops dramatically, the limiting factor becomes imagination, "taste" and judgment, not implementation capacity. The skill shifts from "what can I build given my constraints?" to "what should we build given that constraints have in some ways been evaporated?" The meta-point here is that we keep making the same prediction error. Every time we make something more efficient, we predict it will mean less of that thing. But efficiency improvements don't reduce demand - they reveal latent demand that was previously uneconomic to address. Coal. Computing. Cloud infrastructure. And now, knowledge work. The pattern is so consistent that the burden of proof should shift. Instead of asking "will AI agents reduce the need for human knowledge workers?" we should be asking "what orders of magnitude increase in knowledge work output are we about to see?" For software engineers it's the same transition we've navigated successfully several times already. The developers who thrived weren't the ones who resisted higher-level abstractions; they were the ones who used those abstractions to build more ambitious systems. The same logic applies now, just at a larger scale. The real question is whether we're prepared for a world where the bottleneck shifts from "can we build this?" to "should we build this?" That's a fundamentally different problem space, and it requires fundamentally different skills. We're about to find out what happens when the cost of knowledge work drops by an order of magnitude. History suggests we (perhaps) won't do less work - we'll discover we've been massively under-investing in knowledge work because it was too expensive to do all the things that were actually worth doing. The paradox isn't that efficiency creates abundance. The paradox is that we keep being surprised by it.

The Amplifi HD system has been solid and I still use it for the mesh wifi part of my ubiquiti network for the time being. Wish the Amplifi talked to the rest of the Ubiquiti stuff and was controllable on the console, but it just acts like any other generic switch - can’t adjust things.

@theo I’m scared that you are right on this one. I am currently a Ubiquiti guy and tempted to test this. How is @Ubiquiti letting this happen?

Most of the Black Friday deals suck. There's some gold, but you have to DIG for it. Reply here with the best deals you've found - I'll do the same 🫡

Cursor 2.0 feels dumber and is more expensive without any free models.

this is my first question when I am interviewing I have kids I have beautiful wife I had a broken family growing up Yes this is important to know I am not joining a meat grinder Craig

@shl A piece of land a spider selects for their home.

What is a website? Best answer gets $1,000.

This is clearly correct

@RockRMS @Timlem Yeaaa, Tim!

Welcome to the Hall of Fame @Timlem! Thank you for being such an important part of the Rock Community and driving our mission forward. 🎸

Push brooms can sweep larger open rooms or hallways faster.

A family

@RickStrahl @burkeholland @code Exactly. Hallucination drift is real.

@burkeholland @code Wow the comments here… Generating the file explicitly and saving for you lets you tweak it. And you can regen *as needed*… Not everything should be automagic… there’s enough unpredictability with all of this as it is.

Now @code will generate your copilot-instructions file for you. You will get CRAZY better results by having these instructions for the AI...

Happy Independence Day! The day we celebrate the crazy guy flying straight up the middle of the alien ship's laser beam hole so we can figure out how to beat them and save our planet from total destruction!