The world is always breaking So the world is always breaking; it's in its nature to break. Steven J. Jackson, Rethinking Repair melancholydecay
Angkorwatification Applied to a blog, angkorwatification is a sort of textual equivalent of rewilding. You have a base layer of traditional blog posts that is essentially complete in the sense of having created, over time, an idea space with a clear identity, and a more or less deliberately conceived architecture to it. And you have a secondary organic growth layer that is patiently but relentlessly rewilding the first, inorganic one. That second layer also emerges from the mind of the blogger of course, but does so via surrender to brain entropy rather than via writerly intentions disciplining the flow of words. Venkatesh Rao, Ribbonfarm www.ribbonfarm.com writingentropydecay
The web in decay is the web by design An Essay by Chia Amisola chias.blog When will there be a guide to best practices for archiving the web? Will the giants responsible for the platformization of the web make the act of digital archival any easier for us? Is it foolish for platforms like Snapchat or Instagram Stories to brand themselves as “temporary” when temporariness is impossible on our internet? Should the web exist as something organic, malleable, and destructible –– or as an eternal timekeeper? Is link rot more of a technological issue or a human one? Do humans want to know themselves forever? The Internet Is Rotting decaywww
The Internet Is Rotting An Essay by Jonathan Zittrain www.theatlantic.com Too much has been lost already. The glue that holds humanity’s knowledge together is coming undone. Links work seamlessly until they don’t. And as tangible counterparts to online work fade, these gaps represent actual holes in humanity’s knowledge— they represent a comprehensive breakdown in the chain of custody for facts. The web in decay is the web by design wwwhypermediadecayknowledge
Weathering Steel A Material en.wikipedia.org Weathering steel, often referred to by the genericised trademark COR-TEN steel and sometimes written without the hyphen as corten steel, is a group of steel alloys which were developed to eliminate the need for painting, and form a stable rust-like appearance after several years' exposure to weather. The name COR-TEN refers to the two distinguishing properties of this type of steel: corrosion resistance and tensile strength. Dark satanic steelTilted Arc decay
The Fidelity Curve An Article by Ryan Singer m.signalvnoise.com How do we choose which level of fidelity is appropriate for a project? I think about it like this: The purpose of making sketches and mockups before coding is to gain confidence in what we plan to do. I’m trying to remove risk from the decision to build something by somehow “previewing” it in a cheaper form. There’s a trade-off here. The higher the fidelity of the mockup, the more confidence it gives me. But the longer it takes to create that mockup, the more time I’ve wasted on an intermediate step before building the real thing. I like to look at that trade-off economically. Each method reduces risk by letting me preview the outcome at lower fidelity, at the cost of time spent on it. The cost/benefit of each type of mockup is going to vary depending on the fidelity of the simulation and the work involved in building the real thing. Four levels of fidelityTime to build versus confidence gained prototypesinterfaces
Four levels of fidelity Suppose we have four levels of fidelity… Rough sketch (on paper or an iPad) Static mock-up (eg. Photoshop or Sketch) Interactive mock-up (eg. Framer, InVision) Working code prototype (HTML/CSS, iOS views) Depending on the feature you’re working on, these levels of fidelity take different amounts of time to create. If you plot them in terms of time to build versus confidence gained, you could imagine something like a per-feature fidelity curve.
Time to build versus confidence gained Show image 0 Show image 1 Show image 2 Take a simple CRUD web UI, where you’re just navigating between screens. It doesn’t take much more time to build the real version than it does to mock it when the design is simple. If you were to build out an interactive mock first, you would end up spending twice as much time in total without gaining much out of it. Contrast that with a complicated Javascript interaction. Or a native iOS feature that requires programmer time to build out. If it takes substantially more time to build the real code version, then it may be smart to do an interactive mockup first.