Hacker News Reader

Moving from a push to a pull based approach is an absolute must. It’s the difference between having a novice dev constantly in your ear telling you what they think should go next, vs an assistant you trust to fill in scoped out well defined logic for you.

View on HN

But it is a junior dev and changing the UX won't fix that. That's why the proactive, non-blocking, easy-to-dismiss design is so effective. The cost of failure is extremely low. The moment you switch to a UX where you have to push a button and wait, the acceptable failure rate goes way down.

I don’t want to need to read through a bunch of junior dev trash when I’m going about my day to day tasks. If there’s something I am working on that I can clearly define well enough for a novice to be able to implement it, great, if not, I’ll do it myself.

Back in the free Copilot beta, I disabled automatic completions because they were like intrusive thoughts. Even then, with on-demand completion I felt my code-writing skills withering away as I'd instead ask Copilot to generate blocks of code I didn't have to think through myself.

Reply on news.ycombinator.com