Hemingway&Gellhorn movie

There is nothing to writing. All you do is sit down at a typewriter and bleed.

~ Hemingway

Lately I’ve been enamoured with Hemingway. Looking up to King is a great way to find a writing style people enjoy reading, but Hemingway looks like a way to write good content.

Mostly I like his approach. At least what I’ve lately seen in movies of his character. There’s been so many references to him lately it almost seems like the universe wants me to pick up a book of his and start reading. Movies, blogposts, comments on this or that forum … he’s everywhere.

Shame my only memory of his content is watching the Old Man and The Sea movie as a kid and being totally, utterly, bored out of my skull.

What really convinced me to start reading Hemingway was his javascript. “Code reduced to its essentials with no word or variable wasted.”

Writing like that isn’t the easiest of things, much easier to fluff things up to seem important and educated. Then again, distilling things to their core will often leave readers with a lack of understanding, making too many assumptions and often missing the point you are trying to make.

Easier for readers to hang on your exact words. Always.

In that regard, the internet public is not much different than a compiler. It too will only look at exactly what you wrote, execute it so specifically it will make you cry. Why won’t you do what I’m trying to tell you, you stupid computer!?

Computers don’t read between the lines.

But they do add a lot of lines. First and foremost, a computer assumes you’re an idiot. A far cry from the pure execution machines of the 1960’s, computers these days perform so many optimisations on so many levels it’s nearly impossible to tell what exactly is going to happen once you press Run.

Though, at least a computer reads what you wrote before executing … Most often, at least on the internet, readers will skim the first two paragraphs, decide what you were going to say, then start making assumptions and maaaaaybe fly through the rest of the text.

Not like programming readers is hard enough already.

Here you have a black box, you can’t look at what’s inside, but look, here’s a language it understands. Your job is to use this language so the black box changes its internal state in a way to produce your desired effect. You can’t know exactly what the changes should be, but they must produce this effect.

Each black box behaves differently …

Go. Write something.

Enhanced by Zemanta

Learned something new? Want to become a better engineer? 💌

Join 9,400+ people just like you already improving their skills.

Here's how it works 👇

Leave your email and I'll send you an Interactive Modern JavaScript Cheatsheet 📖 right away. After that you'll get a thoughtfully written email every week about React, JavaScript,  and lessons learned in my 20 years of writing code for companies ranging from tiny startups to Fortune5 behemoths.

Man, I love your way of writing these newsletters. Often very relatable and funny perspectives about the mundane struggles of a dev. Lightens up my day. ~ Kostas

PS: You should also follow me on twitter 👉 here.
It's where I go to shoot the shit about programming.