place
Pointing
"Originally I marked these places, quite literally. I laid a small concrete block flush to the ground at the place where I was standing and stretched a stainless steel piano wire out toward the horizon. It might go off a mile; it simply pointed in a direction. And that was the piece."
The ritualized use of a place
The association of comfort with people and place are reinforced by the ritualized use of a place. Using a place at a set time and in a specific manner creates a constancy as dependable as the place itself. It establishes, in time and behavior, a definition of place as strong as any architectural spatial definition, such as an aedicula, might be. Ritualized use can do more than reinforce the affection for a place. Through ritual, a place becomes an essential element in the customs of a people.
Touring SoHo
SoHo has, however, become part of a tourist archipelago where the definition of place falls into a set of increasingly generic categories. The act of touring devolves less on the particulars of geography than on the consumption of a set of prepackaged lifestyles, defined by a fixed array of goods and services. Almost every city in America now boasts a SoHo equivalent.
We shall meet in the place where there is no darkness
Places I will never go
There are places I will never go. Due to laziness or boredom, or premature fatigue. But there are also landscapes or buildings I should have visited a long time ago. This text reviews those possible places. All of them are part of my story, and they are places I am familiar with in one way or another.
To become completely lost
To become completely lost is perhaps a rather rare experience for most people in the modern city. We are supported by the presence of others and by special way-finding devices: maps, street numbers, route signs, bus placards. But let the mishap of disorientation once occur, and the sense of anxiety and even terror that accompanies it reveals to us how closely it is linked to our sense of balance and well-being. The very word "lost" in our language means much more than simple geographical uncertainty; it carries overtones of utter disaster.
On the edge of something else
The most common response to the question of symbolism was nothing in the city at all, but rather the sight of the New York City skyline across the river. Much of the characteristic feeling for Jersey City seemed to be that it was a place on the edge of something else.
Introverts and extroverts
Some regions are introvert, turned in upon themselves with little reference to the city outside them, such as Boston's North End or Chinatown. Others may be extrovert, turned outward and connected to surrounding elements. The common visibly touches neighboring regions, despite its inner path confusions.
The Image of the City
A Book by Kevin Lynch- To become completely lost
- Apparency
- On the edge of something else
- Nothing there, after all
- Paths, edges, districts, nodes, landmarks
The Third Way
An Article by Kevin KellyBut all the civilized cities of the world were also filled with third places that people loved. Not quite private, not quite public, these third places were intimate but open to anyone. Like settling down at a table at a cafe. It felt like your space, but you were not the landlord. They were public, open spaces that you could “own” for a while.
…We need a new third category of work — something between “employee” and “not an employee”—that encompasses digital gig laborers. AirBnB is neither a hotel, nor a private resident. It is a third thing, and we need to create a new category to deal with it…This is the era of the third way.
On Memory Palaces & Visual Computation
An Essay by Taulant SulkoI now use Are.na as a Memory Palace, separating my channels into rooms. For example, I have a channel that I call the Computation Room. It’s pretty generic and includes any type of block that relates to computation.
If I notice a pattern in the computation room I create a more specific channel in that room. I think of that more specific topic as an object within the room.
Then there are the adjacent topics that I often find even more exciting to focus on. For those, I choose a name that corresponds with the nature of a room and also its size. For example I have a channel called the Visual Computing Observatory. In my head I am imagining an actual observatory where I am looking and observing and studying a given topic.
The Method of Loci
An ArticleFrom the time we learn to walk, we start building up spatial memories—recollections of the layouts of physical spaces and their relationships to the objects in them. These memories tend to form fast and stick around for a long time.
The method of loci hijacks our innate aptitude for remembering physical spaces, using it to help us remember other kinds of information with greater ease.
Not Just a New Feature; a New Compact
A Fragment by Jorge ArangoMy sense is that Slack’s teams think of themselves as adding ‘features’ to a ‘product,’ instead of as stewards of a place where people work.
The small web is beautiful
I believe that small websites are compelling aesthetically, but are also important to help us resist selling our souls to large tech companies. In this essay I present a vision for the “small web” as well as the small software and architectures that power it.
Why aim small?
Why aim small in this era of fast computers with plenty of RAM? A number of reasons, but the ones that are most important to me are:
- Fewer moving parts. It’s easier to create more robust systems and to fix things when they do go wrong.
- Small software is faster. Fewer bits to download and clog your computer’s memory.
- Reduced power consumption. This is important on a “save the planet” scale, but also on the very local scale of increasing the battery life of your phone and laptop.
- The light, frugal aesthetic. That’s personal, I know, but as you’ll see, I’m not alone.
Features and complexity
Niklaus Wirth of Pascal fame wrote a famous paper in 1995 called A Plea for Lean Software. His take is that “a primary cause for the complexity is that software vendors uncritically adopt almost any feature that users want”, and “when a system’s power is measured by the number of its features, quantity becomes more important than quality”.
Solving the problem of software bloat
But instead of just complaining, how do we actually solve this problem? Concretely, I think we need to start doing the following:
- Care about size: this sounds obvious, but things only change when people think they’re important.
- Measure: both your executable’s size, and your program’s memory usage. You may want to measure over time, and make it a blocking issue if the measurements grow more than x% in a release. Or you could hold a memory-reduction sprint every so often.
- Language: choose a language that has a chance.
- Remove: cut down your feature set. Aim for a small number of high-quality features. My car can’t fly or float, and that’s okay – it drives well.
- Say no to new features: unless they really fit your philosophy, or add more than they cost over the lifetime of your project.
- Dependencies: understand the size and complexity of each dependency you pull in. Use only built-in libraries if you can.
Raw size isn't enough
A few months ago there was a sequence of posts to Hacker News about various “clubs” you could post your small website on: the 1MB Club, 512KB Club, 250KB Club, and even the 10KB Club. I think those are a fun indicator of renewed interested in minimalism, but I will say that raw size isn’t enough – a 2KB site with no real content isn’t much good, and a page with 512KB of very slow JavaScript is worse than a snappy site with 4MB of well-chosen images.
...[Instead, it's about] an “ethos of small”. It’s caring about the users of your site: that your pages download fast, are easy to read, have interesting content, and don’t load scads of JavaScript for Google or Facebook’s trackers.