robertogreco + via:jslr   7

Magnum Nominee Sim Chi Yin • Magnum Photos
"I think we’re in the era of blending, bleeding, though of course each discipline and genre has its peculiarities and ethics. The terminology — researcher, photographer, artist — I have difficulty with. I’m just making and doing, thinking, growing!"

"Also, I’ve been thinking about the difference between reach and impact. It’s great to reach millions of people through being on the front page of the New York Times, but having impact on a smaller number of people in a different form is just as valid — if not more so, in our crowded and noisy world."

[via: ]
via:jslr  simchiyin  photography  blending  bleeding  interdisciplinary  multidisciplinary  crossdisciplinary  transdisciplinary  crosspollination  art  making  doing  growth  reach  impact  2018 
september 2018 by robertogreco
Poetry Kōan (@poetrykoan) | Twitter
"Poetry prescriptions for cracking open hearts & minds, bodies & souls. Mostly self-prescribed by/for @stevewasserman_. Always paper, ink, human faces."

[See also: ]
poetry  poems  daily  twitter  via:jslr 
june 2018 by robertogreco
Designing better file organization around tags, not hierarchies
"Computer users organize their files into folders because that is the primary tool offered by operating systems. But applying this standard hierarchical model to my own files, I began to notice shortcomings of this paradigm over the years. At the same time, I used some other information systems not based on hierarchical path names, and they turned out to solve a number of problems. I propose a new way of organizing files based on tagging, and describe the features and consequences of this method in detail.

Speaking personally, I’m fed up with HFSes, on Windows, Linux, and online storage alike. I struggled with file organization for just over a decade before finally writing this article to describe problems and solutions. Life would be easier if I could tolerate the limitations of hierarchical organization, or at least if the new proposal can fit on top of existing HFSes. But fundamentally, there is a mismatch between the narrowness of hierarchies and the rich structure of human knowledge, and the proposed system will not presuppose the features of HFSes. I wish to solicit public feedback on these ideas, and end up with a design plan that I can implement to solve the problems I already have today.

This article is more of a brainstorm than a prescriptive formula. I begin by illustrating how hierarchies fall short on real-life problems, and how existing alternative systems like Git and Danbooru bypass HFS problems to deliver a better user experience. Then I describe a step-by-step model, starting from basic primitives, of a proposed file organization system that includes a number of desirable features by design. Finally, I present some open questions on aspects of the proposal where I’m unsure of the right answer.

I welcome any feedback about anything written here, especially regarding errors, omissions, and alternatives. For example, I might have missed helpful features of traditional HFSes. I know I haven’t read about or tested every alternative file system out there. I know that my proposed file organization scheme might have issues with conceptual and computational complexity, be too general or not expressive enough, or fail to offer a useful feature. And certainly, I don’t know all the ramifications of the proposed system if it gets implemented, on aspects ranging from security to sharing to networks. But I try my best to present tangible ideas as a start toward designing a better system. And ultimately, I want to implement such a proposed file system so that I can store and find my data sanely.

In the arguments presented below, I care most about the data model and less about implementation details. For example in HFSes, I focus on the fact that the file system consists of a tree of labeled edges with file content at the leaves; I ignore details about inodes, journaling, defragmentation, permissions, etc. For example in my proposal, I care about what data each file should store and what each field means; I assert that querying over all files in the file system is possible but don’t go into detail about how to do it efficiently. Also, the term “file system” can mean many things – it could be just a model of what data is stored (e.g. directories and files), or an abstract API of possible commands (e.g. mkdir(), walk(), open(), etc.), or it could refer to a full-blown implementation like NTFS with all its idiosyncratic features and characteristics. When I critique hierarchical file systems, I am mostly commenting at the data model level – regardless of the implementation flavor (ext4, HFS+, etc.). When I propose a new way of organizing files, I am mainly designing the data model, and leaving the implementation details for later work."
tags  tagging  design  folksonomy  files  filing  computing  organization  via:jslr  hierarchy  hypertext  complexity  multiverse  search 
april 2018 by robertogreco
"Pilgrim is something like a combination of a bookmarklet and web-crawler. It provides a better experience for consuming long-form text and exploring related materials on the web.

It works by extracting the content of an article, and loading any links clicked inline on the page. As you go deeper into supplemental material, your path is maintained, giving one a better sense of where the relevant information flows.

Pilgrim is an open source project by initiated with generous support from the Knight Foundation Prototype Fund"

[via: ]  via:jslr  bookmarking  hypertext  reading  text  longform  instapaper  howweread  online  bookmarklet 
april 2018 by robertogreco
Shira Erlichman on Twitter: "I teach writing. A lot. & If I had to distill the lesson that comes up the most it would be: Sensuality > Concepts Sensuality > Concepts Sensuality > Concepts Sensuality > Concepts Sensuality > Concepts Sensuality > Concepts"
"Dear poets-I-chaperone-through-the-process-of-exploring-creative-writing: this thread is to be considered #requiredreading. And then some." ]

"I teach writing. A lot. & If I had to distill the lesson that comes up the most it would be:

Sensuality > Concepts
Sensuality > Concepts
Sensuality > Concepts
Sensuality > Concepts
Sensuality > Concepts
Sensuality > Concepts

Sure, I'd like to know what you think about the world. But only if I can trust that you can invite me into the world: sense by sense. If you write "That year was really hard for me" I don't know what year it is, I don't know what "hard" means for you. Give me bone, give me break.

If I wrote, "When we moved to the US my dad protected us" like, okay? What is protected? What do I mean? The same thing you mean? What if I said "We lived in a basement apartment. The first time I saw snow it blocked our whole front door. My dad dug us out."

& Then, there's so much room for specificity. "Aba" instead of "my dad." My language is not conceptual; it's based in migration, country, movement, slang, whozeewhats, whatevertheFiwant.

You are the only you, you-ing right now.

Be specific.

Be sensual.

Give us the gift of your aliveness.

The second thing that comes up the most when teaching is a total misunderstanding of editing. I get that. Because about 7 years ago I was really skeptical of a 2nd, let alone 19th draft. However, the palace I live in now is the Utter Joy of the (Literally) 21st Draft Palace.

What changed?

For one, I was writing so much that sometimes I'd go back (years later!) to an old 1st draft & see the second Russian Doll hiding inside it. "Whoa, that's weird," I thought & I'd open up that second Russian Doll. Behold, a third Russian Doll (draft) inside it. [image of Russian dolls]

I banished the idea of editing as boring, reductive. Poems were suddenly turned inside out, upside down. I'd find a hidden gem (an image, let's say) & like Sardines, there'd be all these possibilities tucked up beside it. Editing. Became. More. Creative. Than. Writing.

The proof was in the pudding. I'd write a poem, work on it with my little chisel for years & then BAE WOULD ARRIVE! This poem would suddenly strut, sing, thank ME! As if I hadn't been chasing her for her number all these years!

This poem, "Barometer," 2 years before publication basically read like a Dream Journal LOL. Not great. But necessary! Maybe if I get brave I'll post that first draft here. I send it to students to show them the journey!

Think about going 2 the doctor. When you go, you want a listener. Tenderness. Empathy. Thats how I approach a draft: How can I best listen to u? To whats hiding here? Can I have patience for ur glitches & starts? What might u already know––& if I ask the right questions––show me?

& Always remember baby!

There's nothing wasted!

Even if you get to draft 22 & throw that lil beast out. So what? So you sat there, refining & chiseling & flipping language & seeking secret caves & spelunking?

You're muscular as fuck for it. I promise. You'll glow for it."
shiraerlichman  writing  advice  howwerite  classideas  editing  poems  poetry  via:jslr  sensuality  aliveness  individuality  tenderness  empathy 
february 2018 by robertogreco
THE WONDER YEARS, Involuntary Memory, and Mourning | judgmental observer
"This scene was just one of many that has resonated with me in new ways since I began rewatching The Wonder Years, some 24 years after it first aired. This experience has resulted in a doubled viewing position. On the one hand, I am watching as a 35-year-old and so the historical and cultural touchstones that I missed when I was 12 (the changing meaning of the suburbs in America in the 1960s; the anti-war movement; the students protests of 1968; The Feminine Mystique) are suddenly visible and significant. But at the same time, as I watch, I am still watching as a 12 year old."
thewonderyears  memory  nostalgia  childhood  parents  2015  via:jslr  amandaannklein  television  tv  proust  memories  mourning  age  aging  relationships 
april 2015 by robertogreco

Copy this bookmark: