This really depends on the project. For example, if you’re creating a CRUD web app for managing some kind of data, the main tough decisions involve system and data architecture. After that, most other work is straight forward menial work. It doesn’t take a genius to validate a gajillion text fields for a specific min and max length, map them to the correct field in the API, validate on the server again, and write them to the correct database field.
I agree that AI might screw companies over in the long run, when there’s no more juniors that can become seniors. That doesn’t apply to this case at all.
p03locke@lemmy.dbzer0.com 4 days ago
No, for major projects, you start out with a plan. I may spend upwards of 2-3 hours just drafting a plan with the LLM, figuring out options, asking questions when it’s an area I don’t have top-familiarity with, crafting what the modules are going to look like. It’s not slop when you’re planning out what to do and what your end result is supposed to be.
We are not the same
People who talk this way have zero experience with actually using LLMs, especially coding models.
Auli@lemmy.ca 3 days ago
Oh so I didn’t vibe code a go program that I have no understanding of the language cause I knew what I wanted the program to do in the end. Got you I am now a go developer.
p03locke@lemmy.dbzer0.com 3 days ago
No shit… you don’t even have an understanding of the English language. No wonder the LLM didn’t understand you.