Hacker News new | ask | show | jobs
by makeitdouble 944 days ago
In an ideal world I'd choose stacks with not enough boilerplate to warrant copilot.

I had my share of auto generation with enterprise Java stacks, and tried as hard as I could to move to stacks where what we write is concise and relevant (rails is the closest I came to this, not perfect but clearly going in the right direction).

I think AI has its place, but I also hope to be lucky enough to not have to use it.

Illustrators might have similar issues, where some of them need to produce boilerplate drawings a lot, but I think they'd also prefer working on project that aren't that.

1 comments

Yeah these Copilot type tools shouldn’t help much if a language is well-designed, or a project is structured in a fashion that doesn’t require a ton of boilerplate. If we’re doing things well, we’ll only have to tell the computer something once, right?

If it is possible to guess what we’re going to write, then we aren’t transmitting much information to the computer.

Copilot seems to be very popular though.