11–20 of 64 posts
> engineering isn’t just for engineers. Yes it is.
Could be. The question is: Do you want to drive every day to work over the bridge that was not build by engineers.
I'm curious about the use of the terminology "code/coding/coder" as distinct from "programming/programmer". I've noticed that a lot of recent programming outreach and education efforts consistently use "learn to code" instead of "learn to program". How come? What connotations do they perceive? Are they intending to refer to a broader set of activities (including document markup, which I wouldn't refer to as programmi…
I'm curious about the use of the terminology "code/coding/coder" as distinct from "programming/programmer". I've noticed that a lot of recent programming outreach and education efforts consistently use "learn to code" instead of "learn to program". How come? What connotations do they perceive? Are they intending to refer to a broader set of activities (including document markup, which I wouldn't refer to as programmi…
"Programming" is a superset of that, and includes planning and psuedocodes and etc.
As an example of that use see "Jackson Structured Programming" which spends a lot of time drawing little boxes and includes coding right at the end.
Earlier quoted context omitted.
Could be. The question is: Do you want to drive every day to work over the bridge that was not build by engineers.
I disagree with your metaphor. If the bridge you're on collapses, you could be seriously injured. If the CRM you're working in crashes, you're moderately inconvenienced until it comes back up.
You could find loopholes in any analogy. That's what they are - analogies. Perhaps a different one could capture what I wanted to say.
Everybody can sing, but not everybody can listen it.
Earlier quoted context omitted.
Could be. The question is: Do you want to drive every day to work over the bridge that was not build by engineers.
I disagree with your metaphor. If the bridge you're on collapses, you could be seriously injured. If the CRM you're working in crashes, you're moderately inconvenienced until it comes back up.
Or maybe the software you use leaks your secrets to others and you are unwillingly outed as transgender/gay/in-disagreement-with-the-state/etc...
In this digital age, bad software can do irreparable harm to people. We need to keep this in mind and hold ourselves to a higher standard.
We should be helping kids discover coding, not making them love it. I started hating chemistry and biology because I'm forced to study them in thorough detail in school and I have no interest in them--they're really just a pain in the ass. If someone has genuine talent for a particular area, you don't have to push them to explore it--you just make them aware of it and their natural curiosity will do the rest.
I'm curious about the use of the terminology "code/coding/coder" as distinct from "programming/programmer". I've noticed that a lot of recent programming outreach and education efforts consistently use "learn to code" instead of "learn to program". How come? What connotations do they perceive? Are they intending to refer to a broader set of activities (including document markup, which I wouldn't refer to as programmi…
Also thanks to its relatively new household term status, it doesn't carry as much of the pre-internet 80s/90s imagery of nocturnal bearded men doing arcane systems programming through a CRT. The average non-tech office worker in the 80s had some kind of experience with an oddball programmer coming in for an assignment and leaving with a check in hand. As a child of the 90s, that impression even trickled down to me. Partly due to my father sharing his past workplace experiences, but mostly due to the exaggeration of television, movies, and early internet culture.
"Coding" is more cleanly associated with the new wave of engineers, entrepreneurs, apps, and games visible to young people in popular media.
It seems irrational, and it is, but that is language and life.
Earlier quoted context omitted.
I disagree with your metaphor. If the bridge you're on collapses, you could be seriously injured. If the CRM you're working in crashes, you're moderately inconvenienced until it comes back up.
Your app constantly crashes, your customers are pissed and leave. You have to close the company. You suffer from depression and kill yourself. You could find loopholes in any analogy. That's what they are - analogies. Perhaps a different one could capture what I wanted to say. Everybody can sing, but not everybody can listen it.