Hacker News Reader

The core of what we were doing (Writing code) dictated the core of our tool kit (IDE).

Now that we're not writing code anymore it's very exciting to see how this unfolds in the tool kit.

Before you bury me for that "Not writing code anymore" statement my current workflow is literally just talking to Claude via Wispr Flow (mic) whether it's describing what we need to implement or reviewing what Claude Code implemented.

Still building? Yes - Still writing? No

View on HN

> The core of what we were doing (Writing code) dictated the core of our tool kit (IDE). > > Now that we're not writing code anymore it's very exciting to see how this unfolds in the tool kit.

So maybe the text area in your IDE becomes read-only. Even when not actively debugging, you still need to read code and efficiently browse through it as you review it. Because you always review code, don't you? Don't you??

Of course, but it's a 50/50 between exploring the code in an IDE and just looking at the diff.

For simple things the diff is enough, but for something more complex diving into the code and following branches etc. is required.

Reply on news.ycombinator.com