there is a lot to be said for adding complexity you dont understand and then trying to work around it, despite not grasping it. comparing it to no longer doing

there is a lot to be said for adding complexity you dont understand and then trying to work around it, despite not grasping it. comparing it to no longer doing the long division portion of a math problem isnt a great 1 to 1 here. long division would be a great metaphor if the user is TRULY only using llms for auto complete of tasks that add 0 complexity to the overall project. if you use it to implement something and dont fully grasp it, you are just creating a weird gap in your overall understanding of the code base. maybe we are in full agreement and the brunt of your argument is just that if it doesnt fit ur current usecase then dont use it. i dont think i agree with the conclusion of the article that it is making the non coding population dumber, but i also AGREE that we should not create these gaps in knowledge within our own codebase by just trusting ai, its certainly NOT a calculator and is wrong a lot and regardless if it IS right, that gap is a gap for the coder, and thats an issue.