Try reading a manuscript copy of a book before it’s been edited. Yes I know some people do this out of interest but for most people it’s not the type of writing they are interested in reading or would get the most out of.
Just move up an abstraction level and put that flow into planning the features and decomposing them into well defined tasks that can be assigned to agents. Could also write really polished example code to communicate the style and architectural patterns and add full test coverage for it.
I do notice the same lack of flow when using an agent since you have to wait for it to finish but as others have suggested if you set up a few worktrees and have a really good implementation plan you can use that time to get another agent started or review the code of a separate run and that might lend itself to a type of flow where you’re keeping the whole design of the project in your head and rapidly iterating on it.
> Just move up an abstraction level and put that flow into planning the features and decomposing them into well defined tasks that can be assigned to agents
This doesn't work because you still have to read and verify all of the stuff your agents produce
So the new workflow is:
Move up an abstraction level to use an agent to produce code
Then move down an abstraction level to review the code it produces
This sounds like way more cognitive overhead and way harder (and therefore probably slower) to do than just writing the code by hand in a good flow
There's something fundamentally different between writing the program directly that you visualize in your head versus staying one level away and reviewing someone else's code. I'm really talking about the former.
This is nit-picky but you're probably actually referring to Cinematographers, or Directors of Photography. They're the ones who deal with the actual cameras, lens, use of light, etc. Directors deal with the actors and the script/writer.
The reason we give them awards is that the camera can't tell you which lens will give you the effect you want or how to emphasize certain emotions with light.
For category #2 it’s very useful as well and ties in with the theme of the article in that it reduces the activation energy required to almost zero. I’ve been using AI relentlessly to pursue all kinds of ideas that I would otherwise simply write down and file for later. When they involve some technology or theory I know little about I can get to a working demo in less than an hour and once I have that in hand I begin exploring the concepts I’m unfamiliar with by simply asking about them: what is this part of the code doing? Why is this needed? What other options are there? What are some existing projects that do something similar? What is the theory behind this? And then also making modifications or asking for changes or features. It allows for much wider and faster exploration and let’s you build things from scratch instead of reaching for another library so you end up learning how things work at a lower level. The code does get messy but AI is also a great tool for refactoring and debugging, you just have to adjust to the faster pace of development and remember to take more frequent pauses to clean up or rebuild from a better starting point and understanding of the problem.
From what I heard, hyperkalemia is much less of an issue than high unregulated sodium intake for a large majority of the population. The highlighted issue of toxicity in high doses applies to many household foods in general, and I wouldn't think a slightly less salty salt could be posing the highest dangers. Happy to be corrected by more medically-versed people though.
Hyperkalemia can kill you. So can hypernatremia, but we have thirst mechanisms that respond very well to that. Most people who eat more sodium get thirsty, drink more, and then urinate it out.
