iconography
An icon is a symbol equally incomprehensible in all human languages
An icon is a symbol equally incomprehensible in all human languages. There's a reason why humans invented phonetic languages.
A universal correspondence
In 1923 Kandinsky proposed a universal correspondence between the three elementary shapes and the three primary colors: the dynamic triangle is inherently yellow, the static square is intrinsically red, and the serene circle is naturally blue.
The series ▲■● represents Kandinsky’s attempt to prove a universal correlation between color and geometry; it has become one of the most famous icons of the Bauhaus. Kandinsky conceived of these colors and shapes as a series of oppositions: yellow and blue represent the extremes of hot/cold, light/dark, and active/passive, while red is the intermediary between them. The triangle, square, and circle are graphic equivalents of the same polarities.
BeOS Icons
Rethinking Twitter Verification
An Article by Terence EdenThe main problem, I think, is that no one knows what "Verified" means.
If I were in charge (which I'm not) there would be various types of ticks.
🤖 is a bot
🆔 proved their legal identity
🏭 is run by a brand
⚖ is run by a government department
👮 Official law enforcement
😎 CelebrityAnd so on.
What happened when I stopped using Emojis
An Article by Clo S.In March 2021, I went through a fun self-imposed experiment: no emoji for 2 weeks. Not on social media, not in private messages, not even as Slack or Discord reactions. No emoticon either: the goal was to communicate without illustrations, only with words. I did a semi-rigorous (a.k.a. half-assed) diary study, taking notes on my feelings and behaviour.
Why Software is Slow and Shitty
Roman empire military
Rome military diagram.
Most company structures are based on the Roman empire military. CEO Caesar says he wants something, and the lieutenant managers below him on the org chart break it down into smaller tasks for the soldiers to accomplish.
On a development team, programmers are the soldiers of these shitty new armies. They open their Jira issues and add whatever feature it says to add, or fix what it says to fix. If I can save time by adding another dependency, or skip a meeting by implementing a mockup exactly as designed, why should I care?
Building is never a straight line
You might think that Mario 64 was built with tickets and sprints, but, according to interviews, there was no master plan, only the principles that the game should feel good and be fun. They started with just Mario in a small room, and tuned his animations and physics until he felt nice and responsive. After that, the levels were also created as they went, with the designers, developers, and director going back and forth using sketches and prototypes.
Building like this is never a straight line. Ideas and code get left on the cutting room floor because part of innovation is questioning whether what you made should exist. The process is cyclical and iterative, looking something like this.
Conversations, not commandments
Good software comes from a vision, combined with conversations not commandments. In a craft-focused environment, care for efficiency, simplicity, and details really do matter. I didn’t leave my last job just because I wanted to make something new. I left because I wanted to make it in a way I could be proud of.