It's about time
I made a new website. (You are probably on it right now.) It’s been over five years since I made my last one.1
I made this new website because my old website failed.
My Old Website Failed
To make a website interesting, one must post stuff on it. My old website failed because I did not post enough stuff on it.
Now, part of this is on me for simply not posting more stuff. The rest of it is also on me, but for creating a website in which posting new stuff is annoying and hard.
Allow me to present my thesis upfront: reduce creative friction. Iron out your tools, lower whatever imaginary quality bar you have, and just get on with it. Focus on making more stuff in that “quantity builds quality” kind of way.2
This very post is the first skirmish in this crusade.
Let’s start by talking about creative friction.
I’m calling “creative friction” anything that makes you less likely to produce and share creative work.3
I think that there were largely two categories of creative friction I experienced: technical factors and psychological factors.
Technical Creative Friction
I made my old website “from scratch.” By this, I mean I wrote the HTML, CSS, and web server code without any all-in-one toolkit or framework.
However, my old website made it irritating to post stuff. Let me count the ways.
Defining Rigid Categories — The way I had my old website laid out, everything I posted had to be filed under some kind of top-level heading (like “programming” or “writing”). This made it difficult to post exactly the kind of stuff that’s easier to make but harder to categorize: small notes, sketches, little projects. I could have added categories for new things, but that brings me to…
Making New Infrastructure All the Time — It seemed like every time I wanted to make some kind of new post, I had to build something new for the website. Some new way of generating the pages, fixing some thing that broke, adding some other way of displaying something. Even when I tried to fit into the categories I defined, something would go wrong. I guess this is a side effect of…
Maintaining My Own Code — Sometimes maintaining my own code is fun. When it’s some jury-rigged mess written so I could learn about node.js forty-seven versions of everything ago, and I just want stuff to work, it’s not very fun.
So those things were the fault of my website. But actually, there were other pieces of creative friction that were just inside my head.
Psychological Creative Friction
Imperfect Content — At this point, I know intellectually that the best way to get better at things is to practice them over time. This includes the act of making stuff, the act of receiving feedback on it, the act of revision, and the act of starting the next thing. For some reason, for most things I do, I have trouble connecting that understanding to my actions. I guess making imperfect stuff isn’t so scary except for that…
The Internet Is Big and Forever — Most likely, posting on a wee little personal website like this one is more or less like shouting underwater in the ocean a thousand miles from anything. But there’s always a chance that lots and lots of people read your stuff. And there are machines that go about checkpointing copies of the Internet and then saving it forever. So, if you write something dumb, and lots of people see it, you could be perma-embarrassed. Maybe this is just another way of saying that I’ve got some good old fashioned…
Fear of Shame and Criticism — I found a couple of good pieces of writing recently.4 I don’t mean this to brag (what a weird brag), but you know, some times you come across someone’s writing, and you’re like wow, they could destroy me with their words if they decided to. I also feel this way whenever I read The New Yorker profiling anyone. They drop a couple excruciatingly specific details at the beginning about someone’s clothes and demeanor, and it feels like their interviewee has suddenly been cast naked in the flesh in front of you. I’m not sure whether anyone else feels this way. Maybe I’m just crazy. But anyway, reading these writers makes me acutely aware of how vulnerable just about anything is to sharp critique. This contributes to my vague paranoia about submitting my work to the world.
Fear of Accidentally Copying Someone (plus: Not Wanting to Always Spend the Energy to Search out Related Work) — I’m seriously curious whether this is a common feeling among others. (But, by its own virtue, I probably won’t look to find out.) I find that for some things, looking for related work is exhausting.5 This is sort of bizarre, since as a grad student I spend a lot of time reading related work—papers published by other researchers. And for some things, like video game design, I find no dread in looking up techniques, effects, or ideas that others have used in making games. But for writing and producing amateur creative content, I find this sort of burden of looking for—and appropriately citing—related work to be a huge source of creative friction.
There are probably several deeper points you could try to make here. Maybe I’m burnt out from looking at related work in my day job (but then how does the exception of game design fall into this?). Maybe the creative process isn’t always on the same cognitive path as doing “background research,” so switching between them rips you out of a creative flow (plausible?). But whatever it is, especially with the medium of the internet, I find this a particularly potent roadblock.6
Feeling of Wanting to “Hide” Online — This may be another weird one. Does anyone else feel this way? I think I first got this around 2009–10, when everyone I knew was joining Facebook. There were all these little boxes where you could put the kinds of books you liked, music you listened to, hobbies, and so on. Many of my friends did this. For some reason, I remember thinking, why on earth would I do this? It’s nobody’s business! I would guess that everyone intrinsically values their personal privacy on a spectrum, some less, some more. I’m somewhere in the middle. This feeling would get reinforced over the years, whether or not it was directly relevant, with stories people being targeted online, data leaks, and hacks.
Interlude: Why Reduce Creative Friction?
Given all of the annoyances, fears, and worries above (phew! what a mess!), maybe it’s worth asking: should I even reduce my creative friction? Is it so important to produce creatively and post your work online, if all of the above ails you?
I do not think there’s an objective answer to whether it’s best to post your work online. I would venture there’s a personal component to this. Likely some folks will enjoy keeping their creative works private, and others don’t feel the need to produce creative work at all.
For me, personally, I find all of my reasons above pretty stupid, and am eager to try out building more of an online portfolio. I find that I get a lot of personal joy and satisfaction in creating things, and I have a hunch that sharing them online will lead me to do more of it. That alone is enough for me to want to reduce my creative friction.
Reducing Creative Friction
So how will I reduce my creative friction? What’s the deal with this new website?
Reducing Technical Creative Friction
My first directive to myself is to only reinvent the wheel once. Another way of saying this is: make your own version of established things only for educational purposes.7 In this context, this means that I shouldn’t build my website from scratch again, because it’s going to cause creative friction.
The more I learn about myself, the more I realize that this—reinventing the wheel once— is my preferred mode of operation. I like to really get into the details and build something from the ground up, at least once. It’s not so much the feeling of oil on your fingers or the satisfaction of getting a screw tight—though those are enjoyable. It’s discovering what the main problems are by undergoing the design yourself. After doing this, I feel much more comfortable using someone else’s solution because I know how the underlying pieces work. I also end up with a greater appreciation for things other people have made when I’ve fumbled my way through the same problem myself. It’s humbling to see designs that cut to the essence of a problem you were dancing around and didn’t quite see.8
But once is enough. After reaping the benefits of understanding how something is built, it’s just so much more efficient to use a professionally made and maintained foundation than building on your own monstrosity all the time. Writing this down, it seems hilarious to think otherwise. But at least for me, it took several years of programming to realize that just because I could make something of my own didn’t mean that I should. You might call this technical humility, but I think a bigger aspect is learning about the time-consuming factors that go into building and maintaining a seemingly simple piece of software: you will always want more features, compatibility is always a pain, and software stacks are always evolving.
There are a couple other pieces of design that I hope will help with reducing creative friction from the website itself. One is to worry less about the minutiae of how things are displayed. Another is to stop categorizing things (posts that I make). I sat down and made a list of all the kinds of things I might like to post on my website: little digital sketches; notes about doing research or teaching; new software projects I make. The more I thought about it, a one-level hierarchy of simply “a post is an item” would be the lowest barrier for me to make and publish things. This means it’s probably the right scheme for now.
Reducing Psychological Creative Friction
What about the other worries: producing imperfect work that’s archived forever, receiving negative criticism, accidentally copying someone, and revealing yourself online?
I hope that I can overcome many of these worries by a mindset shift from something I realized recently: I like people who have personal websites with more stuff on them.
It’s fun to learn about someone. It’s fun to read about how their mind works, see what they’ve drawn or animated, and spend a few minutes in a slice of their life they’ve shared.
This is likely news only to me. I mean, see Instagram, Twitter, and their ilk. Of course people like learning about other people! People are the most interesting things around.
But there’s something warm and slow and enjoyable about someone’s personal website in particular, as opposed to a feed on a big social networking or aggregator site. I remember finding the photo journal and dream diary of an old math professor, or the book reviews of a computer science theory professor. To give two concerete examples, I enjoyed reading Jacob Steinhardt’s blogs when he was a grad student, and perusing the drawings and personal essays by Karl Stratos. (Both are now professors—wow, time flies!) Having a larger slice into their lives than a simple list of publications immediately made me feel a greater connection to them.
This made me realize that there are more likely upsides than downsides to posting work online. Perfectionism and critical paranoia have a negligible chance of panning out usefully, and there’s no grand bookkeeper finding out better related work that you didn’t mention and docking you karma points. Most of what you write and post won’t matter, so if it helps you in any way, maybe by increasing your creative output or better connecting you to others, it’s totally worth it.
Put into a set of self-directives: make imperfect things. Don’t worry about making bad things. Don’t worry about copying someone. Don’t fret over related work.
I think that the next important part of this is momentum. I hope to figure that one out soon.
I am sorry if “Creative Friction” is a term already and I’m giving it another weird wrong bad definition. For whatever bizarre reason, I find the prospect of constantly looking up whether my ideas or phrases already already completely creatively paralyzing (there’s more about this in the main text), so I’m going to close my eyes and not Google this one. ↩
I’m using the term “related work” here because it’s the phrase we use in (at least my slice of) academia to describe any prior writing from others that address similar topics. Here, I’m broadly thinking about whether someone else has written about similar themes, used similar words, coined similar phrases, or expressed the same thoughts. ↩
Perhaps it’s worth asking: why do I find the prospect of accidentally copying someone, or accidentally expressing a poorly-made derivative thought or work, to be bad? After all, it seems that in many crafts and hobbies, a great way to start is by coping others. (I think there are a lot of quotes by famous people saying this.) Maybe it’s that a blog post implicitly claims originality? Perhaps because of the expectation that the author is well-versed in their subject matter, or the low barrier to looking up related work online? Option C: this is just a detail-oriented, perfectionist-driven fear: if you can look up related work, then you must do your damndest to find a comprehensive list of them, and point out the best ones. ↩
It’s also great to make your own version of something if you love the act of making the thing itself. I didn’t want to clutter up the text with this, but I personally think this is a great reason to make things: simply because you love doing it! Now personally, I’m OK-ish at making websites, but I really only loved doing it when I was working on a website that my friends and I would use. For my own website, it’s more of a means to an end. Just for completeness, I can also imagine other reasons you might want to make your own tools or components from scratch: because you can make materials that are higher quality, more customized, or cheaper than if you’d bought them or used onces others have made. I’m thinking of bartenders brewing their own bitters, bassoonists whittling their own reeds, or painters gessoing their own canvas. ↩
Technical example of an elegant solution: In my old website, I wrote server code for handing routes which retrieved the posts, filtered and sorted them, and then sent them to the user. But why do all this on every request for a static website? Jekyll, which this new site uses, solves the whole thing more elegantly: just generate your website in a build step, and serve static assets at known locations. ↩