| ▲ | thomascountz 17 hours ago | ||||||||||||||||
That makes sense. For me, being "responsible," becoming the new "owner," and "debugging" code which I did not write, can each be frustrating. With regard to LLM generated code, the frustration often comes from there not being a previous "someone" who had been responsible for the code; or rather, the original author was in my opinion, irresponsible, and I must assume responsibility. To your earlier point, I think your examples can be frustrating regardless of whether or not you're a professional—it being a regular part of the job notwithstanding. | |||||||||||||||||
| ▲ | fsniper 16 hours ago | parent [-] | ||||||||||||||||
That's my point. It should not be frustrating. It's part of the job. A responsibility a professional should be ready for. On the part of vibe coded code, it can be a "bad code base" and readily so it's very understandable that reading it can be frustrating. However it could also be very well written. LLM written code can be considered a codebase that was written by a large portion of the developer community all together. It's not coming from some software. Software curated that from human written code one word at a time. | |||||||||||||||||
| |||||||||||||||||