Published by

What a cake

EL and KT came over for dinner last weekend and brought cake. WHAT A CAKE.

It was a chocolate coffee crunch cake. I asked EL, basically it’s this chocolate cake with coffee whipped cream and honeycomb as per this Serious Eats recipe.

It was insanely good. Super decadent, but also somehow very light. Just the perfect texture.

The cake itself kind of reminded me of a cake from a long time ago, so I dug out my grandma’s recipe book again. Turns out my great-aunt’s Texas Sheet Cake recipe (jump to recipe, though I recommend reading the critical notes first) is pretty similar in a lot of ways. Most of the measurements are the same, and both are pretty much one-bowl recipes that call for boiling water.

I haven’t made it recently, but it seems to me that it might be a bit denser / richer than the cake recipe linked above since it has more fat and less milk (1 c butter and ½ c buttermilk in the sheet cake versus ½ c oil and 1 c buttermilk/milk in the layer cake). A denser texture would make sense I suppose for a single-layer cake.

I think the recipe above makes more sense for a layer cake, but I’ll write my great-aunt’s recipe out below since the many-times-Xeroxed version in my grandma’s cookbook is almost unreadable and since it might be worth trying this out with the coffee whipped cream + honeycomb topping.

A few critical notes about the sheet cake recipe:

  • The most notable differences between the sheet cake below and the layer cake linked above is the quantity of cocoa (3 T = ⅛ c in the sheet cake versus ¾ c in the layer cake) and the presence of espresso powder (none in the sheet cake versus 1 t in the layer cake). I suspect it would benefit from a stronger chocolate kick… So maybe it would be worth adding more cocoa powder.
  • I’ve added the metric measurements below by using the Traditional Oven converters online. They’ve never failed me yet, but I should say that I haven’t tried these exact metric measurements so can’t vouch for them. If you want Marie’s original version, go with cups.
  • I’ve written the “preparation” section more or less exactly as my great-aunt wrote it. I do actually think it could be simplified though, probably more along the lines of the recipe that EL shared and linked above where you essentially mix all of the dry ingredients + sugar, then beat in the wet ingredients, then carefully beat in boiling water. But I haven’t tried it myself!
  • This recipe calls for buttermilk, whereas the layer cake recipe linked above calls for whatever milk you have on hand. I have a feeling that you really do need to use buttermilk or faux buttermilk (milk + lemon juice or vinegar) for this recipe to work since it only calls for 1 t of baking soda. If you don’t have buttermilk or can’t make faux buttermilk, I’d probably add some baking powder.
  • This recipe doesn’t call for salt, I think because she assumed you were using salted butter. If using unsalted butter, add ½ t salt as well.

Texas Sheet Cake

Marie Longman

Ingredients

  • 2 c (400 g) sugar
  • 2 c (250 g) flour
  • 2 sticks (1 c, 226 g) butter
  • 3 T (⅛ c, 15 g) cocoa powder
  • 1 c (235 ml) water
  • ½ c (118 ml) buttermilk*
  • 2 large eggs
  • 1 t baking soda
  • 1 t cinnamon
  • 1 t vanilla

Preparation

  1. Oil and flour a 15″×10″×1″ jelly roll pan, and preheat the oven to 350F (175C).
  2. In a large mixing bowl, briefly stir together 2 c sugar and 2 c flour.
  3. In a small pot, bring 2 sticks (1 c) butter, 3 T cocoa powder, and 1 c water to a boil, then pour it over the flour and sugar mixture.
  4. Add ½ c buttermilk, 2 eggs, 1 t baking soda, 1 t cinnamon, and 1 t vanilla to the bowl with the other ingredients, then beat everything together just until smooth.
  5. Spread the batter in to your prepared jelly roll pan, then bake for 17-20 minutes at 350F (175C) until a toothpick inserted in to the center comes out clean.
  6. Let cool completely, and then top with the frosting of your choice.

* To make ½ c buttermilk, pour ½ T of lemon juice, distilled white vinegar, or cider vinegar in to a ½ c measurement and then top it up the rest of the way with the milk of your choice. Actual dairy products will curdle when they hit the acid, which is what you want.

Published by

To read: 2015 essay from the lead of Twitter’s Engineering Effectiveness group

To read: “Let a 1,000 flowers bloom. Then rip 999 of them out by the roots.” by Peter Seibel

Peter Seibel was the lead of Twitter’s Engineering Effectiveness group. This 2015 essay is an extended version of a talk that he gave on the same subject. The TL;DR as he describes it: “as an industry we mostly don’t know how to do it and consequently massively under-invest in making our engineering orgs actually effective.” It’s a really interesting play-by-play of how the complexity and scale of Twitter as an app changed and grew over time.

Side note: With what’s going on at Twitter now, I’d bet my booty that the Engineering Effectiveness group is no longer of this world. Though perhaps that happened before Elon, who knows.

Shared by RS during one of our SuperHi Engineering chats.

Published by

“I think crypto…is an amplifier”

Read “Eric Hu Will Not Take Web3 For Granted” on the Zora blog.

I think crypto…is an amplifier: if you’re a libertarian asshole, it’s going to help you become an even more libertarian, more asshole-y person. But if you believe that the people that help you out should be taken care of, and that we can have a place where we could take care of our friends, and our friends can take care of us, and it’s not about fighting over scraps and the narcissism of small differences, we can take part.

I think this is pretty spot on. So maybe people’s opinions of whether Web3 is going to be “good” or “bad” on the whole comes down to whether they feel optimistic or pessimistic about humanity at large. IDK.

Also:

I think when people are like, ‘Oh, Web3 is going to liberate people’, I get really angry. I’m like, ‘Dude, when you say that, it just makes us all more lazy; we just expect that Web3 is going to be inherently better than Web2’.

No, this is a conscious choice. We have to make protocols that aren’t trying to be extractive—all of that takes effort. I have full faith in Web3’s ability to do some amazing things, but I also have full faith in humanity’s tendency to just become selfish once it gets to a certain point. Web3 has a lot of promises it can offer, but it’s not going to happen automatically.

Also, Eric mentions that some people prefer using the term DISCO (Distributed Cooperative Organization) instead of DAO (Decentralized Autonomous Organizations). I like this, much prefer DISCO. “Autonomous” makes it feel very robot-y. “Cooperative” is much more human.🕺🏻

Twitter can make it seem like the Web3 “war” is purely binary. But there are so many more nuanced takes out there, including this interview and others. Thx SB for sharing it with me.

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.