Сreator of Claude Code: BORIS CHERNY, WHO BUILT CLAUDE CODE, SAID IT PLAINLY." I don't prompt Claude anymore. I have loops running that prompt Claude and figure out what to do. My job is to write loops. "He is not typing anymore. He runs loops that write the code... for him. That is the shift most people miss. Not a better prompt. A loop that keeps running while you are gone.People sell $500 courses on this. The person who built the tool said it for free. The exact setup is in the article below.Bookmark this. Follow CyrilXBTshow more

he's not typing, he's still deciding. that part never gets automated away.

The next productivity leap comes from automation, not repetition. Build the loop once, let AI do the rest. This is where AI is heading—from assistants to autonomous execution.

Boris Cherny nailed it. We see the same shift in labeling loops for quantum datasets. The loop runs quality consensus checks while domain experts step away.

The shift from prompting to orchestration feels huge. Are loops the new programming interface?

your full article is so underrated, i found a lot of new uses for it there

loops turn claude from prompt tool into agent that compounds. Same shift hitting base agent launches right now. @cyrilXBT

Hey, you might wanna check out this Chrome extension called LingTube. It does real-time voice translation on videos from YouTube, TikTok, Bilibili, and stuff like that — super handy for watching tutorials or learning while you chill 😊

写循环这步确实比调提示更像分水岭

this feels like the real change because the system keeps working even when you step away

We're moving from writing prompts to writing systems. That's where the compounding productivity gains begin.

?

I've noticed the biggest shift is moving from asking AI questions to designing workflows.

tough day