> much less time for me to review the plan and output

So typing was a bottleneck for you? I’ve only found this true when I’m a novice in an area. Once I’m experienced, typing is an inconsequential amount of time. Understanding the theory of mind that composes the system is easily the largest time sink in my day to day.

▲

stavros 19 hours ago | parent [-]

I don't need to understand the theory of mind, I just tell it what to compose. Writing the actual lines after that takes longer than not writing them!

▲

olig15 10 hours ago | parent [-]

What do you mean you don’t need to understand? So what do you do when there’s a bug that an LLM can’t fix?

If your bottleneck is typing the code, you must be a junior programmer.

▲

stavros 5 hours ago | parent | next [-]

I don't need to understand the theory of mind because I don't have the LLM design the code, I tell it what the design is. If I need something, I can read the functions I told it to implement, which is really simple.

▲

peteforde 5 hours ago | parent | prev [-]

They said that they don't need to understand the LLM's theory of mind. I think that's crystal clear.

If there is a bug, it's vastly more likely that Opus 4.5 will spot it before I can.

Do you know one of the primary signifiers of a senior developer? Effective delegation.

Typing speed has nothing to do with any of this.

▲

miningape an hour ago | parent [-]

It's not about understanding the LLM's theory of mind - the direct quote was

> Understanding the theory of mind that composes the system

i.e. the logic underpinning how the system works

	▲	peteforde 23 minutes ago \| parent [-]
		You are one of several people in this thread who clearly skipped their Descartes readings.