economics
Baumol’s cost disease
Small economies
The economic value of old buildings
The mirror-image economy
You cannot consume what is not produced
The Fetish of human life
Avant-Garde and Kitsch
The trend is your friend 'til the bend at the end
The amorality of Web 2.0
An Essay by Nicholas CarrThe Internet is changing the economics of creative work – or, to put it more broadly, the economics of culture – and it’s doing it in a way that may well restrict rather than expand our choices. Wikipedia might be a pale shadow of the Britannica, but because it’s created by amateurs rather than professionals, it’s free. And free trumps quality all the time.
Tokenize This
An Artwork by Benjamin GrosserDifferent from the typical website whose URLs act as persistent indexes to a page and its contents, Tokenize This destroys each work right after its creation. While the unique digital object remains viewable by the original visitor for as long as they leave their browser tab open, any subsequent attempt to copy, share, or view that URL in another tab, browser, or system, leads to a “404 Not Found” error. In other words, Tokenize This generates countless digital artifacts that can only be viewed or accessed once.
Hints towards a non-extractive economy
An Article by Matt WebbThere’s a movement called the circular economy which is about designing services that don’t include throwing things away. There is no “away.”
A non-extractive economy is going to look very different to today’s economy. These points feel opposed somehow but they are part of the same movement:
- With CupClub, it’s all about infrastructure.
- With the battery-free Game Boy, it’s untethered from infrastructure: once manufactured, no nationwide electricity grid is required to play.
We’ll need better tools to track and measure. There will be new patterns for new types of services. New technologies to build new products. New language. So it’s fascinating seeing the pieces gradually come together.
The psychology of a discount
An Article by John MaedaFound on a wall.
The bitterness of poor quality remains long after the sweetness of low price is forgotten.
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.