Published by

Gemma’s site in AIGA Eye On Design

Read “There’s More Than One Way to Share Your Design Work: Four fresh takes on the portfolio” on AIGA Eye On Design.

They spoke to Carly Ayres, Prem Krishnamurthy, David Reinfurt, and Gemma Copeland about their approaches to an online portfolio / website. Gemma spoke a bit about how we designed and built her site together, it was a lot of fun. See her site gemmacope.land, or take a look at the GitHub repo. BIG thanks to Howard Melnyczuk for fixing a bug I totally missed. 🤦🏻‍♀️ 🙏

Published by

An endless loop

Just finished the article “Ontological Design Has Become Influential In Design Academia – But What Is It?” by JP Hartnett for AIGA Eye on Design, via the Feminist Open Source Investigations Group chat.

This is somewhat related to the previous post, the “we are our experiences” concept. But much more formal than my ramblings, better philosophical underpinnings for sure!

I’d heard of ontological design but hadn’t really dug in to it. This article is a useful dive in.

In very few words (specifically professor of design theory Anne-Marie Willis’s words, not mine): “Design designs us”. In more words, from Hartnett’s article:

A human being cannot exist independently of its surrounding environment — it is not possible to be without being-in-the-world. Being, then, is always relational: with everything that surrounds us, including the full complexity of the completely designed worlds that we inhabit. This point is crucial for ontological design theorists: design doesn’t just perform certain functions — a car transports you from A to B, a poster displays information, etc. — the interrelated totality of designs construct the world through which humans are brought into being and come to be defined through. Human beings, in turn, design the world, which, in turn, designs them… and so on. The process is circular, like an endless loop.

And on the consequences of embracing ontological design in practice instead of relegating it to theory and academia:

One welcome outcome of an embrace of ontological design theory would be the death of the individualism that has plagued the design profession — “iconic” designs, individual designers, celebrated in isolation as they usually are in design publications — don’t make any sense in this context.

That would be welcome indeed.

I don’t quite see how it can happen unless there is a true revolution in the way we talk and think about design—more holistic and less about singular problems, more collective and less individual—but maybe circumstances are ripening for such a change.

Published by

Lemon Olive Oil Cake & Bosworth Jumbles (links)

This Lemon Olive Oil Cake from the Food Network is fabulous. It didn’t get quite as dark as their picture, maybe need to turn the heat up a little? At any rate, it was so tasty, and useful because I was out of butter. Didn’t make the candied lemon slices because… it seemed like a faff. Totally great without it anyways. Might be worth sprinkling poppyseeds over top next time.

Would also like to make the lemony Bosworth jumbles from this Guardian page soon.

—

Edit 18.06.21 — I made the jumbles, glazed them with the same icing sugar + lemon juice glaze from the cake recipe above. They were divine, and so very easy. The texture was like a delicate shortbread, but they hold together so well because of the muffin tin. I did butter and flour the tin, but that’s because mine is old and beat up. You might be able to get away without it.

Published by

Two articles on SPA or SPA-like sites vs alternatives

I missed these two articles by Tom MacWright from last year.

Second-guessing the modern web, 10 May 2020
If not SPAs, What?, 28 October 2020

In both, he outlines few upsides and downsides about the single page app (SPA) approach to websites and has a few points that I have really struggled to articulate in the past.

From “Second-guessing”:

There is a swath of use cases which would be hard without React and which aren’t complicated enough to push beyond React’s limits. But there are also a lot of problems for which I can’t see any concrete benefit to using React. Those are things like blogs, shopping-cart-websites, mostly-CRUD-and-forms-websites. For these things, all of the fancy optimizations are trying to get you closer to the performance you would’ve gotten if you just hadn’t used so much technology.

I’ve dabbled with React and Vue in small side projects and experiments. But the point above is the big reason I’ve never taken the time to sit down and learn either of them properly. For almost every client site I’ve ever done, it just didn’t make sense to make it an SPA.

And I’m not 100% sure, but I think this might contribute to longevity. Some of my clients are still working with the same sites I built for them nearly 10 years ago, a few with just minor security-related updates in the meantime and no other maintenance strictly required. That’s not to say that those sites couldn’t use a “lick of paint” to bring them in to the 2020s; the point is that they work. And for organizations working on really tight budgets, or budgets that fluctuate wildly due to public funding, stability is really important. They can’t afford a developer on retainer to keep things running smoothly.

But of course the SPA vibe is pretty attractive, particularly for cultural orgs. MacWright has some decent alternatives suggested in “If not SPAs” including Turbolinks, Barba.js, and instant.page. Will also mention MoOx/pjax since I’ve used it before for page transitions with very good results, but probably won’t use it in the future as it hasn’t been updated in a while.

And again, there’s the rub. The more non-native scripts, plugins, etc I use in a project, the more likely that it’s going to be a major headache (and thus major time/money for the client) for me to change things down the line if or when that bit of tech is no longer supported or has changed significantly.

So it’s not even so much about being wary of React or Vue, it’s about not making assumptions, being cautious and cognizant of future needs or restrictions when proposing a tech stack. Any tech stack you choose will ultimately become a ball-and-chain, not just those based on JavaScript frameworks. It’s just that the ball can sometimes be heavier than it needed to be, and you can anticipate that with a little foresight.

Published by

“we will be making marmalade”

Read Letting go: my battle to help my parents die a good death by Kate Clanchy in The Guardian, published 6 April.

They don’t know if she will ever come off [the ventilator], but if she does, they say, she will live a very limited life in a nursing home. “We must hope she dies,” says my dad when I put down the phone. My parents are devout atheists: they believe there is no God and therefore we must live well. So do I. We pray.

This is probably one of the more moving things I’ve read in the past year. I came across it via Kate’s Twitter profile where she often shares poetry by her students.

Published by

To read: “On Immunity” by Eula Biss and “Pond” by Claire-Louise Bennett

Book recs for the list.

***

From an old friend: On Immunity: An Inoculation by Eula Biss

Recommended to me due to relevance with the pandemic, and since the book came about as Biss was navigating the birth of her first child.

Biblio (secondhand) | Graywolf Press (publisher, US) | Fitzcarraldo Editions (publisher, UK)

***

From a new friend: Pond by Claire-Louise Bennett

Recommended to me in relation to mundane creative acts, the quiet and everyday, solitude and maybe domesticity, but not in the 50s please-your-husband-and-the-neighbors sense.

Biblio (secondhand) | The Stinging Fly (publisher, IE) | Riverhead books, imprint of Penguin Random House (publisher, US)

Published by

“It is also difficult to express the full magnitude of our disinterest in passing some Internet Randolorian’s ‘free speech’ litmus test”

I’ve hosted this site with NearlyFreeSpeech.NET (NFSN) for a few years now and have always been happy with their service.

It’s super bare-bones and no-nonsense—probably not the right platform for people or orgs that need more hands-on support or maintenance, so not one that I usually recommend to clients—but it does exactly what I need it to at just about the lowest cost out there (about $1.96/mo for my site at time of writing). This blog post by Blake Watson is a decent introduction to what they’re like as a host.

They don’t have a flashy website and aren’t ones to post often on their blog, but they did recently post a response to the extremists that have been trying their luck on the platform post-insurrection in no uncertain terms.

We’ve received quite a few emails (and signups) from them in the past week or so. They appear to believe that “free speech” means they can say whatever they want without repercussions. (It does not.) They expect us to agree with them about that. (We do not.) And they believe they’re entitled to our reassurance and, in some cases, assistance. (They are not.)

We have zero time and even less energy to waste on such nonsense. It is also difficult to express the full magnitude of our disinterest in passing some Internet Randolorian’s “free speech” litmus test.

It’s worth reading in full, read “Free Speech in 2021” on the NearlyFreeSpeech blog.

They know what they’re about, as they say they’ve been in the game for 20 years. This post reinforces my satisfaction with them as a hosting provider.

Published by

To read: “Maintenance and Care” by Shannon Mattern for Places

Read the article “Maintenance and Care: A working guide to the repair of rust, dust, cracks, and corrupted code in our cities, our homes, and our social relations” by Shannon Mattern for Places, published in November 2018.

Yet even if we build an army of repair robots (a longtime sci-fi dream) and maintenance AIs, their hardware and software will still require upkeep. They’ll still depend upon well-maintained, interoperable technical infrastructures. They’ll still require cleaning staff — “industrial hygienists” — to maintain pristine conditions for their manufacture. We’ll need curators to clean the data and supervisors for the robot cleaning crew. Labor is essential to maintenance.

As Jay Owens reminds us,

There will be dust. There is always dust. By that I mean there is always time, and materiality, and decay. Decomposition and damage are inescapable. There is always the body, with its smears and secretions and messy flaking bits off. There is always waste and it always has to be dealt with, and shipping it out of sight overseas to the developing world does not change the fact this work has to be done (and it is dirty, dangerous work that demands its pound of flesh).

That’s true whether we’re talking about ditch-digging or dam-building or data-diving. Maintenance at any particular site, or on any particular body or object, requires the maintenance of an entire ecology: attending to supply chains, instruments, protocols, social infrastructures, and environmental conditions.

A lot of this relates to the push and pull between maintenance and innovation, how much more attractive innovation, the shiny and new, is in the public consciousness.

This brings me back, yet again, to Ursula K. Le Guin’s The Carrier Bag Theory of Fiction. The heroic versus the contemplative, the careful. The spear versus the receptacle. The linear versus the cyclical. Resolution versus the infinite.

What about a Carrier Bag Theory of Everything?