subomi

I was here a few weeks ago, but I'm now on the CC train. The challenge is that the terminal is quite counterintuitive. But if you put on the Linux terminal lens from a few years ago, and you start using it. It starts to make sense. The form factor of the terminal isn't intuitive for programming, but it's the ultimate.

FYI, I still use cursor for small edits and reviews.

Why do we all of a sudden hold these agents to some unrealistic high bar? Engineers write bugs all the time and write incorrect validations. But we iterate. We read the stacktrace in Sentry and realise what the hell I was thinking when I wrote that, and we fix things. If you're going to benefit from these agents, you'd need to be a bit more patient and point them correctly to your codebase.

My rule of thumb is that if you can clearly describe exactly what you want to another engineer, then you can instruct the agent to do it too.

"They're not only awkward, but a 30 minute call takes up hours of my headspace." This is so apt. I've found that I have the best calls with people who provide specific notes about what they want to discuss—the more specific the note, the less headspace the call requires.

Maybe it could be done via email which is the point of this blog, but I never had the confidence to try that.

> I personally experienced said friction with ELv2, so makes me curious.

Can you share more? What friction did you experience with ELv2?