42 ms·
I think it depends on your copilot, and your own programming style. For example, I find that, when fleshing out an idea, I blackbox a lot. I end up with five o
by shakna 10y ago
I think it depends on your copilot, and your own programming style.
For example, I find that, when fleshing out an idea, I blackbox a lot. I end up with five or six stubs, as I work on a core idea, knowing where to go back to. Then from there, go down over the new code, adding safety once what I have is a working "template".
When I'm driving, the passenger either a) continually interrupts, breaking my flow and interrupting the memory-model of the code I have, or b) doesn't say anything at all, till the end, and it's a major refactor to add in the great ideas they've had. People have trouble with timing, though that might be because a lot of my team find me intimidating.
When I'm a copilot, I do struggle to know when to change the direction, but the biggest issue is that people... Like to "own" their code. Its a personal insult to point out flaws, or to suggest a new way to do something.
In other words, a lot of what the article talks about has been my experience, and some people can't adapt to it.