My view is less polarized. I have been coding since I was a kid and always saw it as a means of solving real problems, but also find beauty in understanding things in a deeper, more formal way – it helps clarify your thinking about the problem domain. There are also some things you cannot solve well without “mechanical sympathy” for the machinery under the hood. I use agentic coding every day now, but still care for “craftcoding” and make sure not to lose the edge of actually understanding how my code and the computing below that works.
Since everything is vibecoded now, I think we can just call it "coding", and call the old way of doing it "craftcoding". What do you think @karpathy? :D
@GergelyOrosz If you hated getting up at 2am to an alert, you’ll love getting up at 2:30am, after an AI messed with prod and gave you a summary with some random hallucinations included for good measure :)