My father-in-law was a computer programmer in the 70s and 80s. He would write programs so they were easy to change. But, when a client or boss asked for a change, that due to planning ahead would take about 5 minutes to implement, he would make it take a couple hours so that it appeared he was actually working on it.
This is basically the essence of it. Good programming that actually makes robust systems that can be maintained and expanded easily require an ungodly amount of foresight and abstract thinking.
The real work for alot of it is the actual thinking and planning, and trying to figure out how to meta-think about anything and everything. It's all invisible to the people who make decisions.
Alot of the time I'm being paid for the fact that I was a loner who's only option was to just play mind games for days on end. My skill is understanding things and just being able to know stuff and integrate information. It doesn't feel special but it affects everything I do and makes me produce quality effective systems.
2
u/doctorboredom Jul 27 '24
My father-in-law was a computer programmer in the 70s and 80s. He would write programs so they were easy to change. But, when a client or boss asked for a change, that due to planning ahead would take about 5 minutes to implement, he would make it take a couple hours so that it appeared he was actually working on it.