You're only looking at half of the equation here. Following your logic, if my time is worth $100/hr, I should be willing to pay $99/hr for a haircut. But reality is that a haircut isn't just worth some utility value based on time saved, it's worth the lowest amount where suppliers' willingness to provide it at a given quality and buyers' willingness to pay meet.

So while the $99/hr haircut might technically save me money/time, suppliers of haircuts are generally willing to give the same haircut for $30/hr. If one supplier tried to pin their prices to the growth of their customers' income, they would go out of business. That is because the value of the suppliers time isn't increasing at the same rate.

Ah, that's a great idea. I've just been having the agent add a Progress section to the plan files and checking things off as we work.

Yeah, I'm watching more. These are incredible. I really like how she describes what she's doing in tempo with the music as she does it. The description is basically part of the performance. Really unique and engaging approach.

This is pretty incredible to watch. I initially thought she must be pulling some kind of trick to make that look so fluid, but the fact that she is making very small typos and correcting them as she goes make it look very believable. This is really the first time I've watched someone use one of these tools and it feel like a musician using a new kind of instrument.

This is essentially my exact workflow. I also keep the plan markdown files around in the repo to refer agents back to when adding new features. I have found it to be a really effective loop, and a great way to reprime context when returning to features.