Menu

Posts tagged “writing”

There and back again: a tale of two book editions

My first online purchase ever happened on September 5, 1999. I was in college at the University of Stellenbosch in South Africa, I really wanted to read Lord of the Rings, and after doing the math I realized that buying the book from this online bookseller in America called Amazon.com would be cheaper than buying it from a local bookstore—even when I took international shipping costs into account.

The book arrived a few weeks later, just in time for the summer holidays to start. I did very little that December that wasn’t reading Lord of the Rings. In fact, I distinctly remember missing the turn of the millennium because at 12:00am on January 1, 2000 I was deeply engrossed in the Entmoot proceedings to figure out whether or not the Ents should go to war against Saruman.

The book ended up traveling with me all over the world. To Australia where I lived for a few years, back to South Africa, all the way to the US, then back to South Africa again, and now here, in Portland, OR. It has served me well:

Robin Sloan has a new edition of his newsletter out. It’s called Crossing the Sunshine Skyway and it is wonderful, as always. Towards the end he links to Adam Roberts’s reflections on re-reading Lord of the Rings. It is long and it looks great so I saved it to read over the weekend. But then Robin says this:

I’ve just completed a reread of LOTR myself: a beautiful one-volume edition with Tolkien’s own (slightly wonky) illustrations included, plus some lovely rubrication.

He posted a photo of the edition he purchased and I was immediately smitten. It looked beautiful, and the idea of seeing some of Tolkien’s own illustrations as part of the story? Heck yeah! I decided that it was time. 24 years after purchasing my first copy of Lord of the Rings—and after many years of resisting lots of wonderful editions because I didn’t want to “cheat” on my original—I purchased The Lord of the Rings Illustrated By The Author. Robin only posted one photo in his newsletter, which made for a bit of a surprise when I received the book. It is so much more beautiful than I had imagined.

I am excited to embark on my own re-read of Lord of the Rings this year, something I’ve been planning to do anyway. And I don’t feel so bad about cheating on my 24-year old copy any more. I mostly feel grateful for the internet and blogs and newsletters and how they can help us find our people and make meaningful connections that sometimes end with a beautiful piece of art in our hands that we wouldn’t have known about otherwise. Maybe, at least sometimes, we can have nice things.

Obsession, endless curiosity, and the joy of iterative projects

I love when people get obsessed with a topic and then turn that obsession into an “iterative project” where they do the same thing over and over until the topic has nothing left to give. An example: my friend Dave watches sci-fi movies hundreds of times and obsesses about the typography for his blog Typeset in the Future. I think his post on Alien is my favorite:

The opening credits for Alien are nothing short of a typographic masterpiece. You can watch them in their entirety on the Art Of The Title web site, but here’s the general gist: a slow, progressive disclosure of a disjointed, customized Futura reveals the movie’s central theme over 90 seconds of beautifully-spaced angular lettering.

Dave’s book is also amazing and you should buy it.

Clive Thompson wrote about this topic recently in his essay The Power of Indulging Your Weird, Offbeat Obsessions. His point about the value of following your obsessions is this:

It’s enormously valuable to simply follow your curiosity—and follow it for a really long time, even if it doesn’t seem to be leading anywhere in particular. Surprisingly big breakthrough ideas come when you bridge two seemingly unconnected areas.

A few other recent examples got me thinking about this again. Ander Monson watched Predator 146 times and wrote a book about it. From an interview with him:

In following every rabbit hole of his obsession with the film through to its end, Monson creates a book that is truly one-of-a-kind—not just a dose of nostalgia for movie buffs, but a revelatory investigation for anyone who’s ever really loved a singular piece of culture, enough that it got tangled inextricably in their identity and could never quite be excised. In Monson’s own words: “I believe that if you look long and hard enough at what you loved best at fourteen and how you lived then and what you saw in the world, it will reveal both the world and you.” As the pages turn, a question inevitably arises: What have you loved in the way that Monson loves Predator? And, for better or worse, how has it made you who you are?

A few weeks ago Monson published an essay about a similar project: Sean T. Collins’s “Pain Don’t Hurt”, an out-of-print book of 365 essays about the movie Road House (you can read every essay on his website). Monson starts off by calling this a “bad idea essay”, and if anyone is qualified to say that, it’s the guy who watched Predator 146 times. But he goes on to say this:

The reason I love bad idea essays is not because they seem dumb or bad but that they’re hard. Anyone can write a good idea essay. But only a real pro—or a real fool, and it’s hard to tell which you are when you start one, which is the entirety of the stakes of the bad idea essay—can write a bad idea to its exhaustion/completion. Only after exhausting yourself will you see if it was worth it.

But it’s these paragraphs that really get to the heart of the matter for me:

365 essays about Road House is an idiotic thing, and its idiocy is part of its appeal. I am often moved by iterative projects, because in repeating an action every day or every week or every year you make time a subject. […]

The reason I love iterative projects is that the plot is inevitably the movement of the mind (or the life or the body) through time. Every piece is a technical problem: oh shit, what am I going to do today? And the technical problem just gets harder as it goes deeper: How can I not bore myself on essay 241?


The reason obsessive projects like these—or what Monson calls iterative projects—are so appealing to me is two-fold. One, there is The Sad, Beautiful Fact That We’re All Going To Miss Almost Everything:

Surrender, on the other hand, is the realization that you do not have time for everything that would be worth the time you invested in it if you had the time, and that this fact doesn’t have to threaten your sense that you are well-read. Surrender is the moment when you say, “I bet every single one of those 1,000 books I’m supposed to read before I die is very, very good, but I cannot read them all, and they will have to go on the list of things I didn’t get to.”

Two, if we agree that we’re going to miss almost everything, there is a certain beauty in picking a small number of things you want to know everything about, and then sharing that with those around you. We know from the African philosophy of Ubuntu that “I am because you are”, or:

Humanity is not embedded in my person solely as an individual; my humanity is co-substantively bestowed upon the other and me. Humanity is a quality we owe to each other. We create each other and need to sustain this otherness creation. And if we belong to each other, we participate in our creations: we are because you are, and since you are, definitely I am.

One of the most tangible ways we can “owe humanity to each other” is by crawling deep into the corners of a specific topic and picking out the best pieces of it for the people around us. It’s saying, “I know we’re going to miss almost everything, but on this thing I got you. I’ll go deep so you don’t have to, and I’ll share what I learn so we can both enjoy what makes it special.”

There’s one more thing that really drove this point home for me recently. Substack has an interview up with Nicola Lamb, author of the Kitchen Projects newsletter. Nicola has built a very large following on Substack, and her answer to the question “What have your subscribers taught you?” summarizes this entire post so well. In essence, her audience taught her that we all want to hear about each other’s obsessions:

[My audience taught me] to be unashamedly obsessed with whatever you are into. To not shy away from details and to get deep into whatever it is that you love. Thank you for that.

So maybe this is something for all of us to ponder a bit more. What are you obsessed with that seems so niche that surely no one else would care? I’ll say this: if someone can write a fascinating book about watching Predator, I guarantee that your “bad idea essay” is probably actually a really good idea for an iterative project. I, for one, would love to read it.

Letting books talk to each other

I love this bit from Austin Kleon’s Letting books talk to each other:

If you read books on different topics and different genres and different formats at the same time, your brain can’t help but find weird connections between them.

This is one of my favorite things—not just with books, but with articles too. It’s such a good feeling when your brain makes those connections. I’ll add that I think this is what makes blogs like Kottke so effective and compelling. When you are able to find and share the connections between things, you have something special going on.

How to communicate effectively as a developer

Via Chris Coyier I found this great post by Karl Sutt on How to communicate effectively as a developer. I especially appreciate him pointing out the importance of communicating clearly in short-form writing like Slack messages. His example of “low-resolution” vs. “high-resolution” writing in that context is a useful reminder for all of us:

In both cases, the example on the left is what I call “low-resolution writing”. There is very little context, too much reliance on pronouns and unclear references. The writing is not emphatic—the reader has to spend extra energy to work out what is being said. The examples on the right, on the other hand, try to make the reader do less work, even though it is more effort for the writer. The writer clearly has thought about how the message will be read.

This idea is similar to what Erin Meyer refers to as “high-context” vs. “low-context” communication in her (excellent) book The Culture Map: Breaking Through the Invisible Boundaries of Global Business. She explains in this HBR article:

I compare cultures along the Communicating scale by measuring the degree to which they are high- or low-context, a metric developed by the American anthropologist Edward Hall. In low-context cultures, good communication is precise, simple, explicit, and clear. Messages are understood at face value. Repetition is appreciated for purposes of clarification, as is putting messages in writing. In high-context cultures, communication is sophisticated, nuanced, and layered. Messages are often implied but not plainly stated. Less is put in writing, more is left open to interpretation, and understanding may depend on reading between the lines.

Choosing the right communication style for the right context is an important skill for everyone, but especially product (and other) leaders. If we assume too much context is known, people will misinterpret what we mean with our words.

So where should we post now?

I’m sure I am not the only one who is currently re-evaluating where I spend my time online. Two tangentially related articles gave me lots of food for thought on this topic over the past couple of weeks. First, Dave Rupert makes this point in It takes one person to knock down a silo:

Wherever you end up I want to offer an idea; you are the value. Your ideas, your insights, your compassion, your ability to help someone in need, your dumb puns and dank memes; that’s what’s valuable. This situation has me thinking hard about where I’m distributing my contributions, where I’m adding value (modest as it may be), and who is benefitting.

Second, Jamie Zawinski asks that we Do Not Use Services That Hate The Internet (please read the whole thing, it’s great):

If posts in a social media app do not have URLs that can be linked to and viewed in an unauthenticated browser, or if there is no way to make a new post from a browser, then that program is not a part of the World Wide Web in any meaningful way.

I like how these posts urge us to consider how, before Facebook and modern social media, the “social web” was pretty much just labors of hypertext love, loosely held together by the online equivalent of duct tape—RSS, trackback links, blogrolls, IRC, etc. I’m not saying we should go back to those old tools specifically (although ooh.directory—”A collection of 951 blogs about every topic”—is pretty sweet). But maybe it’s worth going back to why we invented those awkward solutions in the first place. We saw an opportunity to connect with like-minded people online, to form communities around niche interests, and to make our worlds bigger. Those are worthy outcomes, even if the solutions we had at the time might not be ideal any more.

So where should we post now? I’m going back-and-forth on that a lot. Depending on the day/time/mood, I either want to go all-in on this blog again, or revive Tumblr, or give Mastadon a solid try, or just double down on the newsletter… In short: I have no idea at the moment, but I know I want to keep writing, so I’m trying a bunch of things and hoping at some point I find something that works and that doesn’t make me feel gross. Wherever I end up, I hope that it’s a place like the one Dave describes in the post above:

I hope you’re somewhere that values your value. Somewhere where the stars, hearts, and thumbs up feel like authentic relationships. Give your contributions to someone or some place that appreciates them. In Biblical agrarian parlance, “Cast not your pearls before swine.”

Use asynchronous standups to improve team communication

Ted Bauer and Michael Boykin take on daily, synchronous standups in their article The Daily Standup is Broken, What Should You Do Now?

Asynchronous daily standups or check-ins help to put an end to boundless, traditional standup meetings and get the whole team on the same page with fewer meetings. And corresponding written status updates within a team coordination tool or platform — something that allows every team member to share and review updates from today, yesterday, or even last week — allow everyone to consume updates easily and on their own time.

We landed in a similar (asynchronous) place with our standups, and I wrote about it a while back in Useful daily standup meetings for remote teams:

The issue is always the same: How do we have standups that are useful and that don’t feel like busywork that just takes us away from the jobs we’re supposed to be doing? By using an asynchronous bot and adapting the questions to our needs, we accomplished a few important things:

  • Every member on the team takes a few minutes every morning to plan out their day, and troubleshoot anything that might have gone wrong the previous day.
  • Instead of weekly meetings of an hour long where we discuss what everyone’s working on, we now have focused 30-minute meetings every Monday where we solve problems and discuss issues that came up during the week.
  • I am much more equipped to fulfill my role as Product Manager because our updates are more frequent and the signal to noise ratio is extremely high.

🎉 Elezea turns 10! Introducing memberships and a revamped newsletter.

The first article I published on Elezea was called The dangers of “test and learn”. It was about A/B testing, it was badly written, and it went live on August 3rd, 2009. Since then I’ve posted 1,282 links and articles on this site (that’s an average of 2-3 posts per week).

It’s ridiculous to think that Elezea is coming up on being 10 years old. It is not an exaggeration to say that it sparked most of my career development and helped me meet countless people who I now consider friends. Starting this site was one of the best decisions I ever made. I wish I could go back in time and choose a less impossible-to-remember URL, but such is life.

So what do I do now, after all this time? On reflection I realized all I really want to do is keep writing. I took a couple of breaks over the years, but for the most part, this has been one of the few constants in my life. And I’d like to keep that going in a sustainable way.

So today I’m announcing two things to help set this in motion.

The Elezea Newsletter

For the past few years, the Elezea Newsletter has been simply a list of the articles that went on the site that week. That’s useful as a Twitter/RSS replacement, but not much else. Since my interests extend beyond the product management world into the broader impact of technology on our work and our lives, I am relaunching the Newsletter this Friday to include a wider variety of topics:

  • Useful articles and resources about product management and software development.
  • Resources for leading teams, and working better together.
  • Industry-wide product and technology news you should know about.
  • Book and tool recommendations.

If that sounds interesting to you, please sign up!

Monthly memberships

On the “sustainability” side of things, I decided to launch memberships to help cover the ongoing costs of running a site (and newsletter) like this. I have no ambitions for this to become my main job — I like my job! But I would very much like for the site to at least pay for itself in terms of domain, hosting, and subscription costs.

So if you’ve been reading Elezea for a while and have found it valuable, please consider becoming a member. It costs $4/month, and will help keep Elezea independent and free from advertising.


Whether you’ve been with me from the start, or if this is the second post you’ve ever read, I want to say thank you, thank you, thank you. Elezea is a small part of the internet, but it’s a big part of my life. And it’s your encouragement and support over the years that make it so.

Here’s to the next decade 🤘

(Now go become a member!)

The value of product-specific internal wikis

I am intrigued by the idea of product-specific wikis, as outlined in North Star Product Management. The idea is to have a living document that explains how each product component works, why it exists, why certain decisions were made, and what the future looks like:

The purpose of North Star Docs is not (at least, not necessarily) to minimize changes — changing the North Star Docs is just fine, and is of course actually encouraged, if we can find a better way to do something.

The purpose is, instead, to help map complexity for systems-level, rather than localized, problem solving. They are comprehensive and detailed specs like a Waterfall, yes, but they serve a very different purpose.

This can then be paired with project-specific specs as and when needed. But separating those from the main “this is the overall vision of the product/component” document provides a clear decision-making framework and builds organizational memory.

On making the web with a text editor and a few hours

This essay about the building blocks of the web by Rachel Andrew is really important. From HTML, CSS and our vanishing industry entry points:

There is something remarkable about the fact that, with everything we have created in the past 20 years or so, I can still take a complete beginner and teach them to build a simple webpage with HTML and CSS, in a day. We don’t need to talk about tools or frameworks, learn how to make a pull request or drag vast amounts of code onto our computer via npm to make that start. We just need a text editor and a few hours. This is how we make things show up on a webpage.

The future of books is how they’re created, not what they are

In The ‘Future Book’ Is Here, but It’s Not What We Expected, Craig Mod writes that after years of believing books will fundamentally change in the digital age, it’s simply not happening:

I think we can agree that, in an age of infinite distraction, one of the strongest assets of a “book” as a book is its singular, sustained, distraction-free, blissfully immutable voice.

What has changed, instead, is how books are created:

Instead, technology changed everything that enables a book, fomenting a quiet revolution. Funding, printing, fulfillment, community-building—everything leading up to and supporting a book has shifted meaningfully, even if the containers haven’t. Perhaps the form and interactivity of what we consider a “standard book” will change in the future, as screens become as cheap and durable as paper. But the books made today, held in our hands, digital or print, are Future Books, unfuturistic and inert may they seem.

Or, more succinctly:

Our Future Book is composed of email, tweets, YouTube videos, mailing lists, crowdfunding campaigns, PDF to .mobi converters, Amazon warehouses, and a surge of hyper-affordable offset printers in places like Hong Kong.