paint-brush
Coding is Like Writingby@BenjiStokman
2,094 reads
2,094 reads

Coding is Like Writing

by Ben StokmanOctober 13th, 2017
Read on Terminal Reader
Read this story w/o Javascript
tldt arrow

Too Long; Didn't Read

<span>W</span>hen you <a href="https://hackernoon.com/tagged/code" target="_blank">code</a>, you <a href="https://hackernoon.com/tagged/format" target="_blank">format</a> the characters in such a way that you can understand what you have written — as well as anyone else who will be reading it. When you write, you format your words in such a way that you can understand what you have written — as well as anyone else who will be reading it.
featured image - Coding is Like Writing
Ben Stokman HackerNoon profile picture

Note: This is a half-poem half-essay thing

When you code, you format the characters in such a way that you can understand what you have written — as well as anyone else who will be reading it. When you write, you format your words in such a way that you can understand what you have written — as well as anyone else who will be reading it.

Every single choice you make in your formatting will completely change how what you are creating is interpreted.

But none of that matters — no matter how we format our words or how we space and write our code, the underlying function will always be the same. Always carrying out the same function, holding the same meaning, communicating the same amount of information.

But without the format, the meaning would be meaningless to the reader. The syntax and tone in which the code is written affects its efficiency and how it is interpreted by its human readers. Code without spacing, or English-named variables, or inconsistent formatting would be unreadable to humans, even though it contains the exact same underlying information.