> 1) copilot is a terrific auto complete, and writes tremendous amounts of repetitive boilerplate
I term this "low-entropy code". Copilot is great at writing heaps and heaps of low-entropy code.
The thing is, if you're not paid by LOC, and care about your system as a whole, you normally strive to get rid of code if possible (any code is liability), and make the rest of it high-entropy.
Today's terrific autocomplete is tomorrow's legacy shit you have to deal with.
Lmao what are you talking/coping about? What happened to carriage drivers is pretty well-documented. Maybe ask one of these AI chatbots, they will summarize it for you.
Thank you very much good sir for your kind advice.
I, in turn, suggest looking out of the window: modern carriage drivers are called truck drivers and their number is edging towards 10M worldwide.
Now add to this rail carriage drivers, sea carriage drivers and air carriage drivers. Years of progress changed the way you feed your "horse" and made reins somewhat more complex, but fundamentally nothing changed.
I term this "low-entropy code". Copilot is great at writing heaps and heaps of low-entropy code.
The thing is, if you're not paid by LOC, and care about your system as a whole, you normally strive to get rid of code if possible (any code is liability), and make the rest of it high-entropy.
Today's terrific autocomplete is tomorrow's legacy shit you have to deal with.