Freedomless freedom The beauty of kasuri is received as a gift. As long as the laws of nature are upheld, the beauty of kasuri remains intact. This demonstrates the curious principle that the artisan is deprived of technical freedom but works in the freedom of nature. In this sense, kasuri can be said to be created in a state of freedomless freedom. Yanagi Sōetsu, The Beauty of Kasuri freedomconstraintsnaturemaking
Technological middle age In the automobile's technological middle age, it is hard, if not impossible, to tune or repair one's own vehicle. Technical standardization of cars has occurred, and with it the elimination of the user's access to the machine itself. At the same time, the infrastructures that once served those who did not use automobiles atrophied and vanished. Some may say they were deliberately starved out. Railways gave way to more and more roadways. And thus a technology that had been perceived to liberate its users began to enslave them. Ursula M. Franklin, The Real World of Technology technologyfreedominfrastructure
Why We Build the Wall A Song by Anaïs Mitchell genius.com What do we have that they should want? We have a wall to work upon We have work and they have none And our work is never done And the war is never won The enemy is poverty And the wall keeps out the enemy And we build the wall to keep us free That’s why we build the wall We build the wall to keep us free So that its destruction cannot begin workfreedomcapitalism
Background textures of work An Article by Lucy Keer lucykeer.com One thing I've been enjoying about working as a technical writer is that the minute-by-minute texture of the work feels right. Something about formatting text, faffing about with SVGs, trying to rewrite a sentence more clearly... it's just enjoyable in itself, and I feel at home with it. ...Working as a programmer was very much not like that. There's something in the rough vicinity of professional dev work that I do like, which I could probably label as 'iterative hobbyist tinkering with websites'. I like working on something with a strong visual component, and I like to be inside of a fast feedback loop, and I'm mostly interested in just somehow bodging through until it works. I'm not very interested in either the computer-sciencey side of programming — data structures, algorithms — or the software-engineerey side of making things run reliably at scale in a maintainable way. So maybe it's not surprising that the minute-by-minute texture of professional programming was just... kind of bad. Occasional fun bits when I got into something, but the background experience was not fun. workproductivitymaking