Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

>Almost all the output needs to be re-read, modified and integrated in the project. This often takes longer than just typing it out

You'd be very suprised. Try measuring it.



Yes, I have. That's largely why I've stopped using it.

The time it's taken to rewrite has been larger than not; and worse, it deprives me of understanding the problem i'm solving. So I end up not having thought through the problem and basically having to press delete and type from scratch.


I found it useful for writing unit tests, which really is a stupid brain dead code monkey task.


Really? For me it could not generate meaning full tests, even for the simplest react-components. E.g. it tried to test the display of an error-message in a field in a form. The error message was basically "this is field is required and can't be empty.". It tried to test that, by inserting valid data into the field...


To be fair, many human software engineers can't generate meaningful tests.


People don't have to love using it you know? If the guy doesn't like it, why force it down his neck?

I use plenty of code completion tools already, so I feel similar to them. Sometimes it saves me time, sometimes it doesn't.

For me personally, language servers have been the best thing, you can explore libraries, auto-complete nicely, without as the other poster said, worrying about verifying the correctness.


>People don't have to love using it you know? If the guy doesn't like it, why force it down his neck?

It's not about feelings. It's about there being a thing, in objective reality, with some specific merit, and we're trying to evaluate what it is with some accuracy.

Whether someone enjoys it or not is beside the point.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: