5 ms·
I would like to say this as unambiguously as possible. You either have a skill issue, or you are deliberately solving problems other than the thing you actually
by chickenzzzzu 2y ago
I would like to say this as unambiguously as possible. You either have a skill issue, or you are deliberately solving problems other than the thing you actually want to solve, which you do not mention.
- 9dev 2y agoI think he’s got a point actually. How many times has a compiler told you about a missing semicolon ”here“, and you’ve never thought, ”well if you’re so clever, why don’t you just solve it?!“ Code is an awful abstraction to capture chains of thoughts, but it’s the best we’ve got. Still, caring about syntax, application architecture, concurrency, memory layout, type casting, …—all of that is just busywork, not making the robot go beep.
- mdaniel 2y agoed: or did you omit a "not" as in "not just busywork"? > application architecture, I think you got carried away with your analogy there, because I can assure you that if the LLM generates kafkaClient.sendMessage everywhere for latency sensitive apps, that's not gonna go well, or similar for httpClient.post for high throughput cases
- 9dev 2y agoNeither. What I was trying to say was that all tasks I listed are just there to please the binary gods, not to solve actual business problems. With Application architecture, I was more referring to the layout of the code, as in module boundaries, class inheritance, and so on.
- blacksoil 2y ago> You either have a skill issue, or you are deliberately solving problems other than the thing you actually want to solve, which you do not mention. Wow the first one is quite judgmental. FWIW, I'm the same way, I like writing some code, but definitely not all code. Writing CRUD boilerplate for a schema? No thank you, AI is more than welcome to take that. I derive my joy from getting something done, making it actually usable by the business side, and ultimately have it to generate revenue.