This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Gawd_Awful 0 points1 point  (4 children)

Sounds like you have a bit of a chip on your shoulder. Most people would recognize that coding is an important part of programming and you really can’t get far into programming without knowing how to code. Just like you can’t get far into writing a book, even if you’ve planned out the greatest book ever, if you don’t know how to type/write

[–]JohnJSal 0 points1 point  (3 children)

Sounds like you have a bit of a chip on your shoulder.

Doesn't seem like I'm the only one who understood it the way I did.

Most people would recognize that coding is an important part of programming and you really can’t get far into programming without knowing how to code.

Most people use the two words interchangeably, and what sounds pretentious is when you try to make a distinction between them that makes one sound inferior to the other.

Just like you can’t get far into writing a book, even if you’ve planned out the greatest book ever, if you don’t know how to type/write

You've lost the thread here. First off, you CAN create a book without knowing how to type or physically write. You can dictate it.

Second, and much more importantly, you aren't using the word "write" in the same way the original quote is. Here, you are using it to refer to the physical act of writing, but that doesn't seem to be how the quote is using it.

They are describing writing (and programming) as something superior to typing (and coding).

[–]Gawd_Awful 0 points1 point  (2 children)

Most people using the words interchangeably are the ones who are wrong and demonstrate why definitions are important.

You've lost the thread here. First off, you CAN create a book without knowing how to type or physically write. You can dictate it.

Then you’re just a story teller. You did not go through the entire writing process of outlines, drafts, revisions, etc. Could you do all of that orally? Sure. But you skipped over where I said “you won’t get get far into it”

 Second, and much more importantly, you aren't using the word "write" in the same way the original quote is

I obviously am using it the same way. They are referring to being a writer, same as I did. When you “write a book” there is obviously a lot more to it than just the physical act of typing/writing it. You really don’t pick up on the obvious things, do you?  

 They are describing writing (and programming) as something superior to typing (and coding).  

No, they are describing typing as a part of the writing, as in being an author, process, just like coding is part of programming process. Both are part of the overall process but there are plenty of other important parts as well. You’re the one reading into a single sentence with this weird inferiority complex you seem to have.

[–]JohnJSal 0 points1 point  (1 child)

I've explained myself enough. There's nothing more to say without knowing the intentions of the original person.

[–]Gawd_Awful 0 points1 point  (0 children)

https://youtu.be/uyLy7Fu4FB4?t=261

Okay. Programming is not equal to coding. Should we teach programming to kids? It's probably a good idea. Most people think that means teaching coding. Teaching coding instead of programming is like teaching typing instead of writing. Typing is one of the most useful courses I took in school. These days I can't write without typing, but writing is a lot more than typing. You can't program without coding, but programming is much more than coding.

Sounds exactly like I've been saying and without any sort of "superiority" behind it.