Shawn Wang
100 Bytes of CSS to look great everywhere
An Article by Shawn Wanghtml { max-width: 60ch; padding: 1.5rem; margin: auto; line-height: 1.5rem; font-size: 24x; }
Metrics have a strange hold on the imagination
A Fragment by Shawn WangOnce in place, metrics have a strange hold on the imagination: I've seriously had a CTO carelessly reject my genuine idea out of hand because "it doesn't help OKRs", the same OKRs we previously agreed should not describe all that we do.
I agree with Amir Shevat that we should "do the right things over the easy to measure things."
The Genius of Apple's Name
An Article by Shawn WangIt's easy to have strong opinions about stuff only developers see since user validation is just asking people like yourself. It's much harder to name something consumer facing. Here are some useful rules I gleaned from Apple:
- Two syllables max
- Familiar English word - literal 5 year olds can spell and pronounce it right
- Starts with A - useful for alphabetical sort. Amazon did this too
- Name leads to easy logo/swag/branding ideas
- Evoke aspirational qualities - knowledge, health, nature
Don't Rush to Simplicity
An Article by Shawn WangYou've probably heard this story before:
A businessman finds a fisherman, who is living an idyllic, peaceful life by the sea.
He laughs and tells the fisherman how to get rich instead.
The fisherman asks him what he will do after he gets rich.
He replies that he would retire to an idyllic, peaceful life by the sea.There's supposed to be a deep life lesson in there, but it's always felt insincere to me.
To me it is better to have reached the heights of a career, or suffered an epic defeat, even if I do end up in the same place as everyone else in the end.
To me simplicity is made more beautiful when understood through a long personal struggle with complexity. When I can dance with it, having turned a mighty nemesis into an old friend, and teach others to do the same.
Better to have loved and lost, than never to have loved at all.
80/20 is the new Half-Ass
An Article by Shawn WangThe Pareto Principle is making you lazy.
Let me be more precise: The Pareto distribution is a useful model of power law effects in real life. But people are using it poorly, primarily as an excuse to be lazy.
...People forget that the devil is in the details. The first 20% everyone knows to say on Twitter. The remaining 80% is the ugly, nasty, hacky, unglamorous shit nobody talks about unless you've got time to sweat the details.
The Right Tools for the Job
Tool-building is an essential but poorly incentivized component of academic geography and social science more broadly. To conduct better science, we need to
build better tools.
A representational tension
Do I need to know the precise polygonal geometries of Los Angeles and the University of Southern California to assert that the latter is within the former? No. My mind contains no such precise geometric model of points and lines, yet I know that USC is in Los Angeles. When humans reason with the real world, they focus on its objects, relations, and processes—rather than starting with geometry—because these are the keys to understanding and explaining the real world. Our GIS tools, however, usually do the opposite. Built from the geometry-up around the legacy logic of traditional cartography (geometries and layers), most GIS tools today are restricted by that legacy’s limited ability to model objects, relations, and processes. A representational tension thus exists in GIScience between being a geometric information science versus an ontological, relational, and processual information science.
The teleology of tool-building
The teleology of tool-building suggests that the real value lies in the end use of the tool, rather than in its origins
Urban form and grain
One square mile of different cities' street networks, held at the same scale to compare the urban form and grain.
Software often feels inevitable
Software often feels inevitable because its backstory is often invisible. We click a download link, run an installer, and suddenly have a new tool to use. Yet this conceals years of human decisions, experiences, and constraints shaping software outcomes that are in no way pre-destined.