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

One does not have to be a carpenter to have furniture, and one does not have to become a software engineer to get computers to do things.

Unless you are into it, you’ll realize that it’s quite a grind and your time is much better spent getting somebody who is into it (and thanks to that became an expert to it) get computer to do what you want faster and better.

There’s nothing wrong with trying it, if anything to find out whether you are into it or not in the first place. If you stick to it, chances are you are into it—just like you don’t become a carpetner simply because you want to have furniture: perhaps that’s one of your initial impulses, but you are also mentally compatible with the process and tick some other boxes.

On that note, what does it mean to be “into it” when it comes to programming? What is a “good” reason to become a software engineer? To me, it’s about the inclination to tinker, the eventual payoff of the dopamine rush from seeing puzzle pieces fall together, and the desire to own the process, do things by yourself even as you stand on the shoulders of giants.

Between these things, LLM-driven development strikes me as somewhat weak on tinkering (there may be some, but less, and much less precise and deterministic), and very weak on the desire to do things by yourself. Of course, that shouldn’t invalidate anyone’s personal experience.



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

Search: