Thread

1. QuantumNoodle · 1785956641 · focus · HN ↗

   A hobby is something you enjoy the process of doing, not just the end result. Everybody likes a clean home, but cleaning is rarely a hobby. LLMs expedite achieving the end result. Take from that what you will.

   1. bawolff · 1785958419 · focus · HN ↗

      I think part of it though is that LLMs (especially in novice hands) create code that is more difficult to review and has subtler bugs. Code review is (for many) the least fun part of programming.

      Like imagine if your hobby was cooking, but you hated the cleanup. If you buy a robot that automates the fun part at the cost of making twice the mess, that is not a good trade off no matter how many extra cookies you end up with.

      1. skydhash · 1785959817 · focus · HN ↗

         > Code review is (for many) the least fun part of programming.

         I'm lurking around the OpenBSD mailing list and it seems that code review is where collaboration starts. You send a patch, explain its purpose, people try it out and comment. If it's OK (various factors decide that), it's imported inside the codebase.

         The main issue in corporate settings is that the author of the PR wants to browbeat you into accepting his/her changes. Either directly or by appealing to the manager. They don't want collaboration, they just see you as the blocker between them and the "Done" status on the ticket.

         1. TeriyakiBomb · 1786002092 · focus · HN ↗

            I used to work at a company that did in-person pair review. I wasn’t an engineer there but the engineers all legitimately enjoyed the process. They hired very capable people as a default, so it was watching two passionate and talented engineers debate.

Unofficial Hacker News client; not affiliated with Y Combinator.