Anthropic engineer: "You're not supposed to watch Claude Code work. You're supposed to wake up and review what it shipped" in 22 minutes she builds the full workflow from scratch, step by step a routine that ships work while you sleep most developers have never seen Claude Code run... without them watching watch the session, then save the guide belowshow more

The moment you're letting agents work for hours unattended, understanding how their knowledge changed becomes as important as understanding what they built.

this video is just a small step It takes a lot of effort to get things done while we sleep

new benger

will see

that is how you suposed to work with claude

It really is

most devs will watch the 22 minutes then keep using it the old way

Hope not

this is such a good invitation to stop hovering and start designing better systems

sleep while claude ships hits different

@AnatoliKopadze this sounds wild, I've never even heard of Claude before. gonna need to check it out and see if it can do my job while I nap 😂

The real question is what breaks when you're not watching. i've seen these demos work beautifully on greenfield projects with clear specs. The moment you're debugging legacy code or the requirements shift mid-session, autonomous coding turns into expensive hallucination cleanup

Yes, that's correctly said, we need to wake up and check what they have released

twenty two minutes is wild for an entire flow like that

this is an amazing workshop, watched it alredy two times !

You are fast

Wake up and review what it shipped is a completely different relationship with your tools than most developers have right now

fr the stuff i've seen from ton devs so far, most wouldn't recognize a prod-ready workflow if it bit 'em.

クロード・コードの作業を見るべきではありません。起きて完了物をチェックすべきです。ありがとうございます！

most developers have never seen claude code run without them watching, that's the setup most people are missing and it's why the productivity gap keeps widening

Unit test coverage feels good until you realise you've tested all the pieces but none of the joints. How do you handle integration testing?

interesting perspective bro, definitely feels like one of those ideas that makes u stop and think about where the space is heading next fr

n8n users hit this exact reframe around week 3. 'I'm no longer running the CRM update manually' > 'I'm the one who designed the trigger that runs it.' Claude Code gets developers there in days. The reviewer is the new author.

非常棒！学到了很多。感谢分享。

クロード・コードの作業を見てはいけません。起きて、出荷されたものをレビューするべきです。あなたが眠っている間に仕事を出荷する日課。ほとんどの開発者は、クロード・コードが自分が見ていないときに動作するのを見たことがありません。セッションを見て、以下のガイドを保存してください。 Ngược lại: どのようにしてクロード・コードは自動的に作業を進めることができますか？

o it's cheating death with a stacked deck

,あなたはClaude Codeに仕事を見られることは許されない。目を覚まし、彼/彼女が何を成し遂げたのかを振り返るだけでいい。 彼/彼女は22分の間に、一連の手続きを一から構築し、 あなたが眠っている間に、仕事を完了する自動化された手順を実行します。 多くのプログラマーは、Claude Codeが流れずに動くのを見たことがありません。 作業セッションを見てから、以下の手順を保存してください。

I have started engineering with Claude Code instead of prompting too. And it's just working with little to zero intervention.

貴方の仕事を見て学ぶべきではなく、目覚めて成果を検証すべきだよ。作業をデリバリーするルーチンは睡眠中。Claude Codeを見たことがない開発者はほとんどいない。セッションを見て、このガイドを保存してください。

So the new dev workflow is basically: go to sleep, wake up, pretend you “oversaw the process” haha Managers are gonna call this leadership by morning

What matters is what's in your head, not inside you

アンソピックのエンジニア： 「Claude Codeを見るより、デリバリーをレビューすべきだよ」 22分でゼロからフルワークフローを構築するのはすごい！ 眠ってる間にデリバリーするルーチン、興味深いね。 開発者はClaude Codeを見たことがない、セッションを見てガイドを保存する。

Thanks for the information, bro. Finally, I can skip my routine….