Fieldnotes

23 posts

Posts

Code injection to remove author name and photo

Thank you to Cathy Sarisky for this example of using code injection to modify the Ruby theme. I hated that my theme put my name and photo on each post. It's my site, I don't need to see my name all the time! It made me

curation (or how the half-finished becomes whole?)

It's hard to decide what to put up on this site and what to leave aside. I wish I'd just had one site for the past decade, and everything would be there, whether I liked it or not. I didn't move all of my

the shape of completion

I'm working on consolidating all of my work on this new Ghost site, and I'm thinking about what it would mean to feel complete. The blog or newsletter form often has a sense of incompletion – there's always a "next one" that you

more useful than legible

This is a phrase I wrote down from Erin Kissane's post a few weeks ago, where she discussed the concept of vernacular institutions. Vernacular institutions as I am thinking of them have three essential qualities: They emerge from highly specific local conditions. They prioritize needs on the ground

Strategy requires a diagnosis

We need to see the problem clearly so that we can create a range of solutions that make sense for that particular problem. Of course, there's never just one problem. Everything is always a maze of interlocking problems, of causes and effects, of systems issues and policy issues

How to Collect Metaphors

How to Collect Metaphors

We can reground ourselves in our lives by seeking out metaphors that actually resonate with us.

Our web domains, ourselves (a link collection)

How do we recognize the place and geography of the internet, whilst simultaneously recognizing that what we build does not have to map cleanly towards real-world geographies? Call the world you live in something new. What words do we use? What words do we ignore? What words do we

the trust thermocline

It’s the idea that for some products, irreversible consumer trust damage can happen far in advance of its impact.

Simple, Lovable, Complete

What would a “simple, lovable, complete” report look like?

administrative debt

In software engineering, technical debt is when you work quickly and take shortcuts in coding that prioritize completing the work sooner over long-term stability and consistency of the code. Essentially, you borrow time and resources from the future (to fix problems arising from these shortcuts) in order to have

Page 1 of 3
Next →