Weeknote 2025-W42: Magical and terrifying

Work

  • Wrote this weeknote on an airplane flying to Delhi. Magical and terrifying.
  • Zero progress on the novel this week. Instead, I spent most of my time rushing to doctors’ appointments, preparing for my Delhi trip, and collapsed facedown on my bed after driving across the city for three hours straight.
  • Next week is likely to be a wash, too.
  • I should probably check my calendar before I set writing goals.
  • I’m hoping to at least get some reading done. Looking forward to finishing Fingersmith and moving on to Close to the Machine: Technophilia and Its Discontents.

Not work

  • I’m mildly allergic to eucalyptus and English plantain. The allergies clog my nose when I’m outdoors, which makes me susceptible to upper respiratory infections. On my allergist’s recommendation, I’ve been taking supplements, regularly washing out my nose with a saline nasal spray, and using a nasal decongestant at night. Thanks to these treatments, I haven’t been sick as sick this year as I usually get. Last month, the allergist recommended that I start immunotherapy, which could fix my upper respiratory issues once and for all. So for the past few days, I’ve been putting a tiny drop of custom-made medication under my tongue right after I wake up. I can’t tell if it’s doing anything, because it feels like nothing.
  • To scratch my programming itch, I’ve started learning Clojure. I’m treating it the same way people treat Wordle or the daily crossword: an entertaining way to give my brain a vigorous workout. I’m not expecting to use it for production projects, at least not in the immediate future.
  • I wasted too many hours reading tech news last week, which is something I only do when I’m trying to hide from negative emotions. It’s not surprising. I’ve had a tumultuous few months. But thankfully I’m doing better this weekend, and I’ve set up an appointment with a therapist for when I get back home to Bangalore.
  • I don’t like being in Delhi. It’ve never felt at home there. But I’m looking forward to seeing my brother and parents after a while, and probably some cousins I haven’t seen in over a decade.

Just read

I wrote this post as an exercise during a meeting of IndieWebClub Bangalore.

I started this year with a goal to read thirty-six books. Towards the end of last year I was easily averaging two to three books a month, so thirty-six seemed like an achievable goal.

I clearly overestimated myself, because I’ve only read ten books so far in 2025. In fact, this might end up being my worst year of reading since I started tracking my books on Goodreads in 2013.

So what happened this year that prevented me from reading more? It wasn’t a lack of time, energy, or interest. I didn’t take up a new hobby, start a challenging job, or get into a new relationship. I didn’t travel more than usual, nor did I fall sick more often than I usually do.

What went wrong was that I kept getting in my own way.

I turned reading into a chore by insisting on taking detailed notes on everything I read. Instead of relaxing on my couch with a good book and a hot beverage, I read at my desk with a pencil in hand, underlining interesting passages and scribbling in the margins. For some books that I considered particularly important, I typed up extensive notes.

This changed my relationship with reading. Instead of something I did for pleasure in my free time, it started feeling like work. Instead of something I could pick up and put down whenever I wanted, books became sacred objects that could only be approached at specific times in specific parts of my house. I started avoiding reading, which bred guilt, which bred resentment.

Today, reading has gone from being a normal part of my daily life to something I do once or twice a week, something I have to put on my todo list and check off like a chore.

It sucks.

So I’ve been trying something new: I’m reading without taking notes, highlighting important lines, or even trying to remember everything I read. If I encounter something important, I re-read it or stop to reflect for a minute. But at no point do I turn my reading time into a study session.

I’m finding this surprisingly difficult to do. I’ve become so used to extracting maximum value out of my books that to just read them for pleasure feels like a radical, uncomfortable act. Without that pencil in my hand, I’m actively anxious while reading.

But I keep reminding myself to just read. To not try to remember and catalog every little bit of information I come across. Books are not resources to be mined, but meals to be enjoyed. If something is important, it will come back to me. If it’s not, no amount of highlighting or note-taking will make it stick.

I’m hoping by allowing myself to just read, I can change my relationship to reading and go back to enjoying it like I used to. The number of books I finish this year is not even important. I just want reading to once again become something I do as a matter of course in my daily life, not as a sacred act that requires complex rituals.

I miss reading for pleasure. I’m hoping I can find that joy once again.

Weeknote 2025-W41: Starfish on the floor

Work

  • What do novelists do between getting a promising idea for a story and starting to type out their first lines? Is there a planning phase of some sort? Do they sit at their desks and just think really hard? Do they draw diagrams? Meditate? Go on walks? Consult the oracle? I’ve spent a lot of time learning about the writing processes of a whole bunch of authors, but I still have no clue what happens during the pre-writing process.
  • For my own novel, I’m spending my time researching, thinking, planning, and frantically scribbling notes to myself. Sometimes I starfish on the floor of my home office in despair. I’m not sure if this is valuable work or plain old procrastination. There is no way to tell.
  • That said, I’ve made satisfactory progress this week. The broad strokes of my plot are now clear to me, though I still have to iron out the specifics. I vaguely understand the mysteries behind the fantastic elements of my story world. I have a deeper understanding of my themes, and with it my protagonist’s psyche.
  • Next up, I need to figure out my main cast outside of the protagonist, outline some important climactic events, and finish reading the seventy three Wikipedia tabs I’ve opened in my browser. I’m hoping to draw up an outline for at least the first chapter by the end of the upcoming week. If I’m good and kind and brave, I might even be able to outline the first two or three chapters.
  • I’ve finally found a home for all my long-form writing in Ulysses. I’d prefer to use Scrivener for this work, but I don’t want to deal with its archaic and unreliable cloud sync. I briefly considered iA Writer, which is my default Markdown editor on all my computers, but it doesn’t have the tools to manage projects that contain more than two or three of files.
  • I will not be evaluating any other writing apps. I’m done with that life.

Not work

  • I’m going back to therapy. I recently had an insight about an issue that had stumped me for years, and I need to work through it with a professional.
  • I haven’t been able to make time for Hades 2. In general, games have taken a backset in my life this year. That’s fine, I suppose? Different seasons and all that. I don’t see myself putting significant time into a game again for a few months at least.
  • I’m itching to write code again. I haven’t worked on a significant programming project since March. Ugh.
  • I’ve started tracking my habits using Streaks. It’s silly, but watching that little star appear in the app motivates me to keep journaling and cleaning the litter boxes every day. Just goes to show I’m so easily manipulated, I can do it to myself.
  • I’m grateful for all the new friends I’ve made this year at IndieWebClub Bangalore and other local events. I’m also grateful for all the old friends I’ve reconnected with. If you’re reading this, know that I love you!

Weeknote 2025-W40: Just one chapter

Work

  • I’m writing a novel!
  • To track my progress and keep myself accountable, I’m restarting my practice of regularly publishing weeknotes.
  • I’m terrified. Never in my life have I been more afraid of starting a new project. Send love and reassurance and chocolate.
  • So far, I have a basic premise and an inciting incident to kick off the story. I also have a rough idea of the themes I want to tackle. My protagonist remains a mystery, but I hope to discover who she is in the process of writing the first few chapters. I have an ending in mind, but I’m not tied to it at this early stage.
  • I’m planning to write this book one chapter at a time. Thinking about the full story all at once gives me a panic attack. My immediate goal is to write just one chapter and email it to early readers without worrying too much about what comes next. Any plot problems I create today are Future Ankur’s responsibility, not mine.
  • To figure out how to structure my story, I’m reading Sarah Waters’ Fingersmith and doing a sort of reverse outline. For a book that was shortlisted for the Booker, Fingersmith is highly entertaining and tightly plotted. I want my story to have the same kind of pacing, structure, and plot.
  • I’ll probably share more details about the general shape of the novel when I’m a few chapters in.

Not work

  • I’ve started using Jujutsu for all my personal projects. My friends are sick of hearing me talk about it, which means I must find a fresh audience for my sermons. Reader, have you accepted our Lord and Savior jj into your life yet?
  • Megabonk is crack. No brain, only bonk.

Tech hot takes presented without nuance, context, or evidence

I wrote this post as an exercise during a meeting of IndieWebClub Bangalore.

  • There has never been a difference in the quality of user experience between Windows and macOS. They’re slightly different spins on the exact same idiom.
  • Graphical interfaces are strictly superior to command line interfaces in every way that matters.
  • Any sufficiently complicated UI framework contains an ad hoc, informally-specified, bug-ridden, slow implementation of half of HTML and CSS.
  • HTML and CSS are the best technologies for building user interfaces in 2025.
  • Learning CSS expands your mind in the same way learning Common Lisp or Haskell expands your mind. If you dislike CSS, you probably don’t understand CSS.
  • Mobile operating systems (iOS/Android) require as much skill and knowledge to use as desktop operating systems (Windows/macOS). Anybody who can comfortably use a smartphone today can also learn to use a desktop computer.
  • LLMs are not such a big deal. Learning to use them well nets you marginal productivity gains, but ignoring them completely at this juncture won’t do much harm.
  • LLMs will only improve productivity when we build better UIs for interacting with them. A chat box is the worst possible way to use an LLM.
  • git is an impediment to good software engineering. Its baroque and confusing UI results in hundreds of thousands of wasted developer hours across the world every year, costing organizations tens of millions of dollars in developer salaries.
  • Social media as it exists now should be regulated the same way we regulate gambling.
  • Bonus non-tech take: writing is not thinking, good writers are not necessarily good thinkers. You don’t even need words to think.

The ducks incident

I wrote this post as an exercise during a meeting of IndieWebClub Bangalore. It was inspired by the prompt for this month’s IndieWeb Carnival: second person birds.

When I was ten or twelve, Dad had a brief interest in keeping birds. This post is about the ducks incident.

(Honestly, they could’ve been geese. I can’t say for sure now. I’m going to go with ducks.)

On my parents’ wedding anniversary one year, Dad called home from work and told the entire family that he had something special planned for Mom. This was a time before cellphones, so this was all the information we got out of him before he hung up his office landline.

The whole family—me, my brother, Mom, and our grandparents—spent the rest of the day waiting eagerly for him to come home. He got back just as the sun was setting and parked our old Maruti 800 in the verandah. We sensed his excitement as he asked everyone to come outside and gather around the back of the car.

When we were all outside and had displayed the appropriate level of enthusiasm, he opened the boot of the car with the air of a magician about to pull a rabbit out of a hat. Out stepped two ducks.

I don’t know what any of us was expecting, but it was definitely not this. Mom was so bewildered by the giant white birds now pecking at things in the verandah that she forgot to be angry at Dad. My grandparents just shook their heads, while me and my brother were thrilled with this new addition to the family.

There were questions. Like: where will the ducks live? Or: don’t ducks need a lot of water to survive? Or, most importantly: who the fuck told you that ducks made for good anniversary gifts?

I’m sure my parents had some, uh, disagreements about the presence of the birds in our lives, but we had them and we couldn’t just let them loose in the city. So we had to figure out a way to keep them healthy and happy.

We made a haphazard coop for them on the rooftop using bits of old furniture. Dad bought the biggest plastic tub they would sell him and filled it with fresh water every few days. In the morning, we’d let the ducks out of the coop and dad would spray them with water from a hose. We’d let them walk around the rooftop in the daytime, where they’d peck at the bird feed we’d scattered around and stick their necks out of the railing at the edge of the rooftop to watch people passing by.

There were honks. Loud ones. They echoed across a neighborhood that was otherwise distinctly lacking in waterfowl. Soon enough, everyone figured out where the ducks lived, and we were known as that family that had ducks on the rooftop for some reason. In the evening, mothers would bring around their kids so they could look at the birds. Many kids got pecked that summer.

At night, the task of getting the ducks back into their enclosure fell to me and my brother. We were young at the time, and these ducks were not small. Every night, we’d spend half an hour trying to herd them into the coop, and get pecked, smacked, and pooped on in the process. Did you know birds can smack you with their wings? I didn’t, but then I got smacked.

After six months, Dad decided he’d had enough. I don’t know if it was the upkeep, the parade of children and their parents ringing our doorbell at all times, the bruises, or the noise, but he decided to let the ducks go.

One Sunday morning, me, my brother, and our parents went to a nearby lake, where we let the ducks go. We were concerned that that they wouldn’t be able to survive in the wild, but they seemed to do okay.

For a few months, we visited the lake to check if our birds were doing well. They had found a family with another group of ducks that lived in the same lake.

And that’s end end of the ducks incident.

PKM apps need to get better at resurfacing information

I’m a happy user of a number of apps that can be classified under the nebulous category of Personal Knowledge Management (PKM) software:

  • Obsidian (note taking)
  • Things (task management)
  • Drafts (quick capture)
  • Readwise Reader (RSS and read-later)
  • Raindrop (bookmarking and archiving)

These apps allow me to work with vast amounts of digital information. They let me:

  • Quickly capture information from my computer or physical environment
  • Organize captured data using categories and/or tags
  • Connect related information using bidirectional linking
  • Annotate information (by e.g. highlighting parts of web pages, PDFs, or EPUBs)
  • Quickly capture my own fleeting thoughts as I engage with the information (or the world in general)
  • Synthesize what I’ve learned by writing my own notes, potentially creating new knowledge in the process

But something crucial is missing from modern PKM apps: they do a poor job of helping me re-engage with information that I’ve already captured but forgotten about. None of them can automatically resurface relevant material from my system based on my current context.

For example, if I’m using Obsidian to write a journal entry about my exercise routine, I want the app to show me every other journal entry about the same topic. I could pull them up manually, but that would require searching for multiple keywords and wading through more than a decade of writing. In 2025, even a tiny on-device embeddings model could find them instantly.

Resurfacing information doesn’t even have to rely on complex AI algorithms. I want my todo list app to show me every task that was created more than six months ago, which can be easily accomplished using a simple database query. This feature would save me a ton of time and energy by allowing me to prune outdated tasks from my system without having to manually read through each one.

With their current abilities, most PKM apps feel like inert stores of data, no different from the old paper notebooks I’ve stashed away in my desk drawer. There’s a ton of useful information in there, but there’s no way to find it unless I arduously flip through the pages.

Why is this useful?

I personally want to re-engage with the information stored in my PKM apps so that I can:

  • Remember what already exists in my system: PKM tools remove friction from the process of capturing information, which means I sometimes forget what I captured. It’s good to be reminded.
  • Prune stale data: sometimes I need to remove outdated or irrelevant items from the system. Manually sifting through them can be an overwhelming task, but it’s easy to progressively delete them as the app resurfaces them over time.
  • Reduce paralysis of choice: looking at a list of hundreds of documents or articles can be paralyzing. Having an algorithm automatically select a subset of them eases the process of choosing what to engage with.
  • Observe patterns: if I’m constantly reacquainted with information I captured at different points in my life, I can begin to see patterns in what I read and write.
  • Create serendipity: sometimes the mere act of placing two unrelated notes together can spark new ideas.

A possible solution

I love Spotify’s Home tab. It does a great job of resurfacing music I’ve already listened to or saved in my library. Right now, it shows me:

  • The eight most recent albums, playlists, or artists I listened to
  • A selection of mixes created from music in my library
  • A set of recommended albums based on my recent listening activity
  • A set of albums featuring songs I’ve added to my playlists
  • A list my favorite artists, based on recent listening
  • A list of new releases from artists I like
  • Recommended playlists based on genre and mood

If I ignore the algorithmic recommendations—as I usually do—there’s a lot on this list that nudges me towards re-engaging with music I already love dearly. This is exactly what I want my PKM apps to do for me.

A magical far-future version of Obsidian could start with a homepage containing:

  • My most recently created and edited notes
  • A “This Day in History” section, listing notes created on today’s date a year ago, two years ago, and so on
  • Notes similar to the notes I’ve recently created and edited
  • Notes I haven’t opened in a long time
  • My most frequently accessed notes
  • Notes grouped by sentiment or some other algorithmic criteria

Of course, this is only one possible solution that applies to one specific kind of app. I’m including it here in the hopes that it can serve as a starting point that can be further iterated upon.

Plugging the gap myself

I’ve built a few (admittedly very simple) tools to surface data automatically from the apps I use regularly:

  • I use a function on Val Town to take me to a random bookmark stored in my Raindrop account. I call it StumbleDrop, an homage to the beloved Web 1.0 service StumbleUpon.
  • Another function on Val Town takes me to a random article in my Readwise Reader account. Of course, I call it StumbleWise.
  • I’ve created custom views1 in Readwise Reader to show me stale RSS feed items, stale read-later items, and items with a certain combination of tags.
  • Every few days, I Command + click the Open random note button in Obsidian eleventy billion times and read whatever comes up.
  • I use the Similar Notes plugin in Obsidian to show me notes similar to the one I’m editing in a sidebar2.

These tools have improved my experience of using my PKM apps, but there’s only so much functionality I can hack together with scripting and extensions3. I want these features built into my software, not haphazardly pasted-on using third-party extensions and services.

Whoever solves this problem will have my heart forever

If I’m not careful, my PKM apps become black holes where information goes to die. I end up with thousands of notes, tasks, bookmarks, and read-later items that just sit there, completely inert and useless, making me anxious.

I could be more disciplined about what I collect, but why do difficult thing when have computer? What’s the point of using a computer for knowledge work if it can’t amplify my cognitive abilities?

If you’re building a PKM app today, I urge you to consider building features that allow your users to periodically re-engage with the information they collect. Your users will appreciate it, and I will love you forever.

Footnotes

  1. I don’t understand why more apps don’t support custom views. Some macOS apps have Smart Folders, but what you can do with them is often limited.

  2. It mostly works well, until it mysteriously breaks.

  3. Allow me to take this moment to complain about the quality of extension and automation APIs in most software. Many macOS apps still don’t support Shortcuts (looking at you, Chrome), forcing me to write AppleScript. Some apps expose more functionality via AppleScript than shortcuts, or vice versa. Some apps omit basic functionality from their automation suites, such as navigating to a list item. And don’t even get me started about REST and GraphQL APIs exposed by webapps. For many SaaS apps, it’s easier to write a Puppeteer script and extract data from the DOM than use the official API.

How to avoid writing

Some people believe it’s difficult to avoid writing. That if you have a story to tell, it will burst forth from the tips of your finger and leap onto the page at the slightest encouragement.

I’m here to prove those people wrong. I’m here to prove that it’s possible to defer your most precious dream for years, decades, your entire working life, until it’s far too late to do anything about it.

I have personally managed to avoid writing for more than half my life already, and I’m here to tell you how you can do the same. If you follow my simple advice, you too can avoid doing the one thing that fills you with joy and vitality!

Blame your environment

Your first line of defense against writing is to blame your environment.

Complain about your chair, the height of your desk, the quality of your keyboard. If its loud, complain about the noise; if it’s quiet, complain about the lack thereof. Complain that the air conditioning is too hot or too cold, that there is too much or too little natural light in your workspace. When your friends invite you out to dinner, complain about having too many social obligations; if you don’t have friends, complain about being lonely.

You will never have the ideal conditions to write. Turn this fact to your advantage. Turn every minor discomfort into a reason for not doing your life’s work.

Blame your tools

The next technique is as versatile as it is enjoyable: blame your tools for your inability to write.

Tell yourself that you can’t possibly write that novel until you find a writing app that feels just right, an app with just the right features. Try as many apps as you get your hands on, then draw up comparison tables to ostensibly help you choose the correct one. Every time you find an app that meet your needs, find something to be annoyed about: an animation that feels “off”, a feature that doesn’t work on your smart fridge, lack of support for a file format from 1998 that you might want to use.

Never mind that Jane Austen wrote on sheets of coarse paper that she stitched together herself, making marks on it using a quill pen that was made with goose feathers and had to be periodically dipped in cheap ink. Who cares about Jane Austen? She wasn’t that good anyway. The moment you find the perfect writing app, the world will forget Jane Austen even existed.

The best thing about blaming your tools as an excuse is the sheer mileage you can get out of it. Not having the right software is just the beginning, you can continue to avoid work by endlessly tweaking the tools you already have. Change the font, try different window layouts, download endless plugins and extensions, spend an entire Tuesday learning a new programming language just so you can add a new button to the user interface.

If you’re clever, nobody will call you out on it. Everyone will congratulate you for being so dedicated to your craft. The internet is full of people who only ever write about writing apps. You, too, can be one of them.

Blame your writing process

When you’ve exhausted all excuses around tools, you can move on to the question of writing process, a series of perfectly calibrated mechanical actions that will take you from blank page to published work without taxing your brain. Wait, what’s that? You don’t have a writing process? Well, then you must take the time to develop one! Preferably by reading as much as you can about writing without doing any writing yourself.

An easy place to start is to read about the work habits of other writers. This is best done on the internet, where those habits will be presented without context, completely disconnected from the work those habits were developed to serve.

Once you’ve exhausted this near-infinite well of low-calorie information, move on to reading books about the craft of writing. Writers love to give advice about writing, especially when that advice is useless to everyone but the advice-giver. These books should keep you busy for a few years without bringing you any closer to writing anything worth reading.

And if it happens that you somehow manage to exhaust even this vast resource of non-information, you can always fall back on the one resource that is truly inexhaustible: podcasts and video essays about writing.

Remember: 2x speed is for people who want to do the work. You must live your life at 0.75x.

Take notes

While you’re devising the perfect writing process, take detailed notes on every piece of media you engage with. Did you know that you can double the time spent reading a book if you insist on rewriting everything the author says in your own words on a stack of index cards?

If you’re truly adventurous, build a Zettelkasten. Of all the techniques humanity has invented to prevent actual work from occurring, the Zettelkasten is the most ambitious, the most baroque, and the most effective.

I recommend keeping a copy of How to Take Smart Notes on your desk at all times. It’s a treasure trove of techniques that help create pointless busywork without yielding anything in the way of useful output.

Create busywork for yourself

Talking of busywork, here’s something familiar that’s employed by every schoolchild, bureaucrat, and project manager on the planet. Busywork creates a flurry of activity without resulting in anything worthwhile getting done, perfect for all of us who want to appear important and industrious without being either.

This one is easy: make elaborate plans for work you will never actually do. Make task lists, reorganize your notes, catalog all the books you want to read, clear your email inbox, pay your utility bills, update your operating system, clean up your phone contacts, rearrange your browser tabs, prune your photo gallery, and indulge in any other activity that involves moving information from one location to another.

The trick is to shuffle information around until it feels like it’s vaguely organized, without using it for anything that resembles real work. Type the words “personal knowledge management” into a search engine and watch the possibilities unfold.

Do research

You cannot be expected to write a novel about friendship unless you know everything there is to know about friendship, right? That would be absurd. Draw from personal experience? Pshaw, that’s for amateurs! Does a brain surgeon draw from personal experience? Does a rocket scientist draw from personal experience? Then why should a novelist be expected to draw from their personal experience of normal everyday human emotions?

Novelists must draw from years and years of difficult research and study. Books! Newspaper articles! Blog posts! Scientific papers! Gotta read ‘em all. How else are you going to give your readers a sense of verisimilitude?

The best part about doing research is that you don’t even have to read the material. You can spin your wheels for weeks, even months, doing research about the research you’re planning to do.

Make elaborate lists of everything there is to read about friendship, why you should read it, where to purchase it, which order to read it in, and who recommended it. Collect as much metadata as you possibly can. Make mind maps and spreadsheets, databases and infinite canvases. Don’t read the material, just read the text surrounding the material: reviews, meta-commentary, abstracts, Wikipedia articles, anything but the actual research material.

Stay in the shallows where it’s safe, away from the groping tentacles of success and creative fulfillment.

Journal

There will come a time when looking into the screen with your eyes glazed over will no longer suffice. The usual flurry of busywork will no longer suffice. Shuffling other people’s words from notes app to notes app will no longer suffice. You will want to type words into your computer, using your own ten fingers, produced by your own spongy brain.

There will come a time when you will want to at least feel like you’re writing, but of course without putting in the effort to write. You will want to appear, to any external observer, like you’re producing a great deal of work, but without having to shoulder the burden of producing any work at all.

This is when you begin keeping a diary. Call it something impressive, like morning pages or freewriting. If someone asks why you’re journaling, come up with a reason that makes you sound spiritual and enlightened. Journal every day for hours and hours, far more than is necessary or reasonable. Do this for a year, five years, a whole decade. Document every little minutia of your life. Tell yourself you’re collecting material for future stories. Try to ignore the fact that the only story you’re telling is the story of your refusal to do the work.

Do self-care

If all else fails, take a year long vacation from all your responsibilities, burning through the money you were saving for retirement. If anybody objects, use the magic words: self-care. That will shut everyone up.

At the end of the year, start over with a new creative pursuit, something that “feels more authentic”.

You, too, can successfully avoid writing

If you follow my advice, you can forever put off writing that thing you always wanted to write! Before you know it, you will be old and feeble and close to death, having accomplished nothing, leaving behind hundreds of megabytes of rough notes half-filled with half-thunk half-thoughts.

If you set your mind to it, you can avoid writing forever. Even if it’s the only thing you’ve ever wanted to do.

I'm trying to change my relationship with my desk

(This post was written and published as an exercise during a meeting of IndieWebClub Bangalore.)

My physical space determines the kind of creative work I’m able to do. This is both a blessing and a curse.

For example, the moment I sit down at my dinner table with a cup of chai, my mind automatically shifts into journaling mode. I don’t have to make an effort, it just happens. I can write thousands of words from that specific spot in my house.

Sitting in the comfortable chair in my home office, with my 27” monitor and external keyboard, I get in the mood for writing code. I’ve worked from this particular configuration of this particular desk for nearly a decade. It’s so strongly associated with technical work in my mind that I don’t have to try consciously to think about code when I’m in that space. My mind automatically shifts gears and puts me in the mood for programming.

But having these strong associations with certain spaces in my house means it can be difficult to use them for other tasks. I’ve been trying to write short fiction over the last few months, and the only place in my house that’s comfortable enough for long hours of work is my home office—the same home office that I use for working on my software projects. Every time I try to use this space for creative writing, I have to fight the urge to work on a programming side-project instead.

If I had the space, I’d set up another desk in a different room dedicated to creative writing, but my house is not large enough for that. This desk setup is all I have. I have no option but to change the strong mental association I’ve built with my work desk.

I’ve found one solution that’s yielded positive results: instead of changing the location where I write fiction, what if I change my state of mind instead?

One way to change my state of mind when I sit down at my desk is to change my pre-work ritual. When I’m working on a programming project, I usually begin my day after I’ve taken a bath, had chai and breakfast, and spent some time catching up on news. Changing this ritual should theoretically put me in a different headspace while keeping my workspace exactly the same. This shift might allow me to form new mental associations with my desk.

To test my theory, I’ve been following a different schedule for the last few days: I wake up earlier than usual, make myself a cup of chai, and immediately begin my first writing session of the day. I do this before checking the news, responding to texts, or letting the world intrude on my thoughts in any other way. So far, this has been working well. I’ve been able to write about five hundred words a day for the past few days, which is an uncharacteristically large amount of writing for me.

I’ve only been doing this for a few days now, so it might just be the novelty that’s keeping me going. But I don’t want to jinx myself by questioning a process that’s producing results. I’ve almost finished writing a short story I’ve been struggling to finish for a few months, and that counts for something. Right?

Nothing can save us forever, but a lot of things can save us right now. When my new strategy stops working, I’ll try something else.

Writing without a plan

(This post was written and published as an exercise during a meeting of IndieWebClub Bangalore.)

Ever since I was a teenager, I’ve followed the same process for writing pretty much anything:

  1. Decide what I want to write about
  2. Dump all my thoughts about that topic into a new document
  3. Reorganize my braindump into a coherent outline in the form of bullet points, making sure there’s a logical progression of ideas from start to end
  4. Turn the bullet point outline into readable prose
  5. Fix grammar, spelling, style, and tone
  6. Publish

This is how I was taught to write essays at school, and this is the writing process taught by most writing books and workshops. On the surface it looks pretty reasonable: first you collect all the raw material, then you arrange it so that your audience can logically follow the progression of your argument, and finally you flesh out your prose so that your writing is enjoyable and memorable. What’s not to like?

For me personally, this process just does not work for most kinds of writing I’m interested in. Or rather, it works to the extent that it allows me to produce something that looks like writing, but it makes the process of committing words to paper feel robotic and utilitarian. It works on the assumption that all I need to do to produce a piece of good writing is get the facts out of my head and rearrange them to make them palatable to my readers. It ignores that fact that I might not know what I want to say, or that there might not be any real “facts” involved in what I want to write.

I’ve found this process to be perfect for producing technical writing or persuasive articles, but it hasn’t served me well for writing fiction, poetry, song lyrics, or personal essays. That’s because with all these kinds of writing, I don’t always know what to say. In fact, when I’m writing something that could be considered more “creative” than a blog post about JavaScript, I’m often looking to surprise myself. I’m writing not to communicate or persuade using the knowledge I already have in my head, but to allow my subconscious to surprise me by coming up with connections I could never have made by creating a bulleted list of facts.

So, for most of the creative writing I’ve done this year, I’ve followed a different process:

  1. Set a timer for 45 minutes
  2. Open a blank document and start typing
  3. Wrote a good thing? Fix grammar, spelling, style, and tone. Then publish.
  4. Wrote a bad thing? Move document to a Graveyard folder and try again.

I’ve found that this is not an easy process to follow. Writing without the security of a plan or an outline is nerve wracking. It’s a bit like walking on a tightrope. You never know what’s going to happen, you just react to the words you’re typing in real time, listening to your heart and mind, steering your work gently without trying to push it towards a preconceived goal with force.

But it’s exhiliarating. And incredibly fulfilling. When I follow this process, I end up surprising myself every single time. The results are never what I would’ve produced if I had started with an outline and a specific goal. Writing without a plan has made me realize that my mind is capable of making surprising connections in the moment if I allow it to react to the work I’m doing rather than follow a script I’ve written beforehand.

This blog post was written using the same process. It might not be my best work, but I feel it turned out alright.