Depends on your definition of "programming." If you mean "putting code together" then maybe even more than half. If you mean "engineering" then a very small fraction.
I would also argue that "engineering" as a discipline, as part of the "operations" clause in the link above requires a close observation of the economics of any proposed solution. In other words, engineers have to worry about costs.
FWIW, I went through a journey a couple years ago to try to define the term "software engineer." I notice there were A LOT of people just throwing code around or just copying and pasting random crap from stacktrace and aws demo code w/o understanding what it did.
I think inherent to the "application of scientific knowledge" part of the definition is an implication there's a mental model where the engineer is manipulating abstractions in the model to get to a solution.
I have no idea how to code, yet have boiler plate GPT code in production. No interest in learning, it's not for me. I like this site for the diversity of topics and information.
Actually it's more like to "Try to play the wise guy in Hacker News in any category you can possibly imagine and someone will definitely know more than you and write an essay proving their point while making you feel really worthless for just breathing" sub-Reddit lol!
11 comments
[ 3.1 ms ] story [ 29.1 ms ] threadI would also argue that "engineering" as a discipline, as part of the "operations" clause in the link above requires a close observation of the economics of any proposed solution. In other words, engineers have to worry about costs.
I think inherent to the "application of scientific knowledge" part of the definition is an implication there's a mental model where the engineer is manipulating abstractions in the model to get to a solution.
I found this book useful (and short): https://academic.oup.com/book/591