"If the problem is that we’ve painted our development environments into a corner that requires tons of boilerplate, then that is the problem. We should have been chopping the cruft away and replacing it with deterministic abstractions like we’ve always done. That’s what that Larry Wall quote about good programmers being lazy was about. It did not mean that we would be okay with pulling a damn slot machine lever a couple times to generate the boilerplate."
If you have a fediverse account, you can quote this note from your own instance. Search https://tldr.nettime.org/users/tante/statuses/116074382014960841 on your instance and quote it. (Note that quoting is not supported in Mastodon.)
RE: https://tldr.nettime.org/@tante/116074382014960841
Some of this resonates, but maybe code wizard is not the correct lens?
For ~50 years, programmer meant “writes code”. But, maybe it should have meant "solves problems".
In other words: companies don't pay programmers high salaries to write code, they pay them to solve business problems. Sometimes that means you don't write any code at all and fix a process problem. Other times, code is the solution.
The code is not the valuable artifact, though.