Designers need codes, not keys, to unlock their career

Written by a ‘designer who does a bit of code’

At the origin of the world there were designers and coders sitting at the opposite sides of a room, throwing each others assets and specs (and chewing gums) like there was no tomorrow.
Websites were ugly and didn’t really need much design work (many of those websites are still live and in that old, rudimentary shape) — UX problems were taken in consideration only from the elite.
Then Apple and Google came and the assets multiplied and the concept of beauty on the screen (not only mobile) changed completely.

We all know this old story, but sometimes I just wish I’d been a designer when web design was not a thing — at least I could have tried the old processes (and programs) that didn’t work on my own skin instead of having to read or listen to the predicaments from professors or some famous person I have never met.
Now, more than 10 years later (feels long, but it’s nothing), it’s interesting to reflect on how much the design thinking and profession have changed.

We don’t throw chewing gum to engineers anymore (or at least we shouldn’t).

Designers of my generation have been given a bunch of keys…