3 ms·
I call that first one ("typing or clicking to have computers do stuff") "typing." The taxonomy is missing "designing," "architecting," "crafting," and more thi
by drewcoo 4y ago
I call that first one ("typing or clicking to have computers do stuff") "typing."
The taxonomy is missing "designing," "architecting," "crafting," and more things people like to say they do. To feel important. More important than someone(s) else.
And I often call myself a "professional typist" because the whole taxonomy is pompous BS.
I get paid to solve business problems.
- rfrey 4y ago>I get paid to solve business problems That's far more pretentious than any of the things you listed.
- WinnieRallycar 4y agoI wouldn’t say so. In essence, every employee is paid to solve business problems.
- irrational 4y agoHow is it pretentious? I feel the same way. When people ask me what programming is like, I tell them it is 50% understanding the business problem, 49% problem solving, and 1% writing code.
- rfrey 4y agoBecause first, it's trite: literally every person in the organization is hired to "solve business problems". Second, I think it's pompous to elevate one's position to some sort of strategic "problem solver" role when, unless you are a consultant, you are hired to translate requirements into working software systems. Your boss would roll her eyes at the "I solve business problems" language. She would say, "Uh-huh. You do that - solve the business's problems. Just make sure you close your Jira tickets while you're doing it."
- d0mine 4y ago"translate requirements into working software systems" demonstrates fundamental misunderstanding what programmers do. It is a decades old and rather common misconception. It is why there is "mythical" in the Mythical man-month book (1975). More https://news.ycombinator.com/item?id=35297082 https://news.ycombinator.com/item?id=35297082
- mechanical_bear 4y agoThat’s literally what it is though.