perhaps during those walks he may try and catch up on the learning being missed out on by having outsourcing thinking to a data collection machine

I mean, you're free to not "outsource your thinking". If you actually believe that fiddling with the code by hand is essential, just spend 5 minutes giving a prompt and 55 minutes working by hand. Boom, you're as efficient as 2 programmers were before AI, and you only had to "miss out on" 1/12th of the learning.

That's great for everyone who isn't the author of the post:

> A year ago leadership told us everything goes through agents now. Hand written code needed a reason

I can't imagine needing to ask for permission or having to justify myself every time I personally wrote code. That definitely sounds like hell

Ironically the author of the original post is probably a LLM reddit spam bot https://news.ycombinator.com/item?id=50434474

But in any case, in that hypothetical scenario, just automate your day job and spend time coding a side project you're passionate about. You might have to spend 10 minutes out of every hour prompting, but hey, that's still 400 minutes a day for your side project of choice.

im sure your take applies to the majority of men who label themselves programmers

This reads as a flippant and reductive comment that projects a bit (outsourcing thinking?) but actually helps surface a good rule of thumb:

If you're telling an agent how to implement something, congrats! You're doing it right and should go on a walk while it's being implemented.

If the agent is telling you how to implement something, you should probably take a walk to digest it, and come back to tell that implementation-machine what to actually do so you can take another walk while it's being implemented.

i have no idea what you are accusing me of, did you want to make it a bit clearer what i am supposedly projecting? to me, the act of doing something is outsourced to entity X, when entity X is requested to do that thing (and proceeds to do it). are you saying the only actual thinking that occurs in human structures occurs at the planning level, therefore plan execution involves no further scope for learning?

That sounds great in theory, but a) it leads to burnout trying to do so much stuff in parallel and b) it's useless in the end unless you're willing to just yoloship things.

I stopped doing it as a result.

My real point is you shouldn't be sitting there waiting so you can tell the agent to "continue." Spec stuff out more and let it do it's thing. Whether you yolo-ship it or not is another matter.

My point is the context switching gets so exhausting that it's not worth it. The more you spread your attention thin by having lots on the go, the less you understand about any of it, the longer it takes to properly verify its correct before shipping. These things are at odds with one another.

It's amazing how much you missed the point.

>> If he's waiting around, he should give it bigger chunks of work or work on multiple projects in parallel. Give it larger prompt and go for a walk.

The level of stupidity of this statement is unbelievable.