| I'm having trouble with the concept of claiming that one "wrote" something that was entirely, or almost-entirely, generated by AI. I use Tesla's FSD all of the time. When it's on, I'm "driving" insofar as I'm monitoring my surroundings and preparing to take over if the car does something crazy. However, I'll usually tell people that the car drove, not me. I also don't understand the value of using AI to write stuff in loads of unfamiliar languages. I get why one might choose Rust vs. Golang vs. JavaScript depending on the mission, but I would think that those differences go away entirely when you're depending on an LLM to author something in those languages AND you aren't skilled enough in those languages to understand when something's suboptimal or not. This just feels like an express train to bankruptcy via technical debt. I'm also having trouble with the notion of AI accelerating the creation of side projects. For me, actually writing the code (or figuring out how the language works) is part of the fun that I get from doing side projects. If I wanted to create something as quickly as possible, I'd just buy a SaaS subscription or physical version for what I want. It's also insane to me that we're just not AT ALL considering how LLMs stunt the growth of our juniors. Spending hours banging my head against the wall on tiny bugs is how I got to where I am today. I'm going to guess that's the case for many of the people on HN as well. That learning process goes away entirely once an LLM goes into the mix. You can just ask it to fix whatever's broken, no understanding of the bug required. This is fine for seniors who know why things happen how they happen, but I can't imagine juniors making up this skill gap. It's like learning a new language vs having your phone generate whatever in the target language. The end result is the same, but there's no way you can really learn that language with your phone doing the work, unless one assigns no value to learning that language in the first place. Finally, I have trouble accepting the idea of giving up the keyboard once you become an "architect." I very much understand that us "architects" have less free time in the day to fire up the IDE (death by meetings, basically), but giving that up entirely feels somewhat career-limiting to me. Then again, this is a moot point if the market moves towards making software development an AI-only activity. What's crazy to me is that most developers and architects sneered at low/no-code solutions because they created unmaintainable codebases that were too proprietary to make sense of, yet here we are lapping up code generated by "coder" LLMs and accepting that they "might" produce insecure code here and there. Insane. |