monospace.studio
Back to Thoughts

Design and code · 2016

Why I learned to Code

A designer's argument for getting close enough to code to understand the medium, collaborate better, and make stronger product decisions.

Imagine walking into a library and not being able to read. That is how I feel to be living in this age of information and data without being able to code. Data is everywhere, hence information is everywhere.

I work in tech, and as such I am privy to common knowledge (in the tech world) that many people are not aware of. Do you know I could reach out (into the internet) and pull together a very decent profile of everyone who is/has been in my vicinity with relative ease? People who "check-in", or post messages using Geo-location on their phone, for example, are fair game online. A cross-reference here, a cross-reference there, and a useful profile emerges.

Snooping is of very little interest to me. But I do like the idea of being able to use code to gather information and empower me to make decisions. Small scripts (of code) — which can even be considered simple robots — are not difficult to create and can run a whole slew of boring tasks for you: searching for an apartment, ordering regular deliveries and so on. And once the Fridge starts to join the party, who knows what doors are unlocked.

I decided that code is important and learned to code. Except, like any language, it's difficult to become "fluent". It requires constant practice. So, I continue to study, and write minimal scripts, and sharpen my fluency, as I wait for the day when I find writing code as easy as writing these sentences, and I watch the world turn around me, and I say "wow, did I really make that happen?".

Update: I found this link which just about sums up how awesome it is to be able to code: blog.howdy.ai/lunch-hacks. This is what I'm talking about!

Read the original Medium article