▲ | codr7 5 months ago | ||||||||||||||||||||||||||||
So instead of being creative and finding ways to avoid duplication, you look for a way to make copies faster. That's one way to solve the problem. Not the way I'm looking for when hiring. | |||||||||||||||||||||||||||||
▲ | JohnBooty 5 months ago | parent | next [-] | ||||||||||||||||||||||||||||
That's not at all how I read the parent post. It feels more like you're replying to a hybrid of the grandparent post (person who churned out a lot of duplicated code with AI) and the parent post (person who likes being "editor" and finds AI helpful) | |||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||
▲ | AnimalMuppet 5 months ago | parent | prev | next [-] | ||||||||||||||||||||||||||||
This has happened before. When we went from assembler to compilers, this logic would have said, "So instead of being creative and finding ways to avoid hand-coding loops, you look for a way to spit out copies of loops faster." And the answer is, "Yeah, I do! I want the compiler to write the loop for me and get all the jumps right so I don't have to worry about it! Getting the jumps for the loop right is incidental to what I'm actually trying to write; I've got better things to spend my time on." Note well: I am not arguing that AI will produce good code rather than multiple layers of garbage. I am merely saying that this particular argument is weak. | |||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||
▲ | solumunus 4 months ago | parent | prev [-] | ||||||||||||||||||||||||||||
The more experienced I get as a developer the less importance I place on avoiding duplication. The amount of time wasted breaking apart abstractions because someone year or two earlier was intent on avoiding duplication… A lot of these abstractions are just not worth the time to implement or maintain. It’s much better to have all the duplication and then in time the optimal abstraction will become apparent, if there even is one. | |||||||||||||||||||||||||||||
|