---
title: "Friday fun: my .zshrc has more aliases than I have memory"
description: I opened my .zshrc for the first time in months and found aliases I don't remember writing, for tools I don't remember installing. This is what I found.
canonical: https://lukeocodes.dev/my-zshrc-has-more-aliases
type: article
locale: en_GB
published: 2026-05-29T00:00:00.000Z
modified: 2026-05-29T00:00:00.000Z
authors:
  - Luke Oliff
section: Developer Experience
tags:
  - Developer Experience
  - Engineering
feed: https://lukeocodes.dev/rss.xml
search: https://lukeocodes.dev/search.json?q={query}
schema:
  - "@context": https://schema.org
    "@graph":
      - "@type": Organization
        "@id": https://ably.com/#organization
        name: Ably
        url: https://ably.com
      - "@type": WebSite
        "@id": https://lukeocodes.dev/#website
        url: https://lukeocodes.dev
        name: Luke Oliff
        alternateName: lukeocodes
        inLanguage: en
        publisher:
          "@id": https://lukeocodes.dev/authors/luke#person
        description: Personal blog and writing by Luke Oliff — developer relations, voice AI, developer experience.
        potentialAction:
          - "@type": SearchAction
            target:
              "@type": EntryPoint
              urlTemplate: https://lukeocodes.dev/blog/search?q={search_term_string}
            query-input: required name=search_term_string
      - "@type": Person
        "@id": https://lukeocodes.dev/authors/luke#person
        name: Luke Oliff
        url: https://lukeocodes.dev/authors/luke
        description: Staff engineer and Staff Tech Lead for Developer Experience at Ably. Writing about developer relations, AI, and the voice industry, from the UK.
        mainEntityOfPage: https://lukeocodes.dev/authors/luke
        givenName: Luke
        familyName: Oliff
        image: https://lukeocodes.dev/authors/luke.jpg
        jobTitle: Staff Tech Lead, Developer Experience
        worksFor:
          "@id": https://ably.com/#organization
        sameAs:
          - https://www.linkedin.com/in/lukeocodes
          - https://github.com/lukeocodes
          - https://bsky.app/profile/lukeocodes.dev
          - https://x.com/lukeocodes
          - https://hashnode.com/@lukeocodes
          - https://dev.to/lukeocodes
        knowsAbout:
          - Developer Relations
          - Developer Experience
          - Voice AI
          - Text-to-Speech
          - Answer Engine Optimisation
          - Search Engine Optimisation
          - Open Source
          - Developer Tooling
          - API Design
          - Speech-to-Text
          - Voice Agents
          - Community Building
        knowsLanguage:
          - English
        nationality: British
        alumniOf:
          - "@type": Organization
            name: The Open University
  - "@context": https://schema.org
    "@graph":
      - "@type": Organization
        "@id": https://ably.com/#organization
        name: Ably
        url: https://ably.com
      - "@type": Person
        "@id": https://lukeocodes.dev/authors/luke#person
        name: Luke Oliff
        url: https://lukeocodes.dev/authors/luke
        description: Staff engineer and Staff Tech Lead for Developer Experience at Ably. Writing about developer relations, AI, and the voice industry, from the UK.
        mainEntityOfPage: https://lukeocodes.dev/authors/luke
        givenName: Luke
        familyName: Oliff
        image: https://lukeocodes.dev/authors/luke.jpg
        jobTitle: Staff Tech Lead, Developer Experience
        worksFor:
          "@id": https://ably.com/#organization
        sameAs:
          - https://www.linkedin.com/in/lukeocodes
          - https://github.com/lukeocodes
          - https://bsky.app/profile/lukeocodes.dev
          - https://x.com/lukeocodes
          - https://hashnode.com/@lukeocodes
          - https://dev.to/lukeocodes
        knowsAbout:
          - Developer Relations
          - Developer Experience
          - Voice AI
          - Text-to-Speech
          - Answer Engine Optimisation
          - Search Engine Optimisation
          - Open Source
          - Developer Tooling
          - API Design
          - Speech-to-Text
          - Voice Agents
          - Community Building
        knowsLanguage:
          - English
        nationality: British
        alumniOf:
          - "@type": Organization
            name: The Open University
      - "@type": BlogPosting
        "@id": https://lukeocodes.dev/my-zshrc-has-more-aliases#article
        headline: "Friday fun: my .zshrc has more aliases than I have memory"
        alternativeHeadline: "Friday fun: my .zshrc has more aliases than I have memory"
        description: I opened my .zshrc for the first time in months and found aliases I don't remember writing, for tools I don't remember installing. This is what I found.
        datePublished: 2026-05-29T00:00:00.000Z
        dateModified: 2026-05-29T00:00:00.000Z
        url: https://lukeocodes.dev/my-zshrc-has-more-aliases
        mainEntityOfPage: https://lukeocodes.dev/my-zshrc-has-more-aliases
        inLanguage: en
        author:
          - "@id": https://lukeocodes.dev/authors/luke#person
        isPartOf:
          "@id": https://lukeocodes.dev/#website
        keywords: Developer Experience, Engineering
        articleSection: Developer Experience
        about:
          - "@type": Thing
            name: Developer Experience
        abstract: I opened my .zshrc the other day for the first time in maybe six months. Not to fix something, just curious. The file was two hundred lines long.
        speakable:
          "@type": SpeakableSpecification
          cssSelector:
            - .post-tldr
            - h1
        image: https://lukeocodes.dev/blog/my-zshrc-has-more-aliases/hero.png
        wordCount: 597
        timeRequired: PT3M
        publisher:
          "@id": https://ably.com/#organization
      - "@type": BreadcrumbList
        itemListElement:
          - "@type": ListItem
            position: 1
            name: Home
            item: https://lukeocodes.dev
          - "@type": ListItem
            position: 2
            name: Writing
            item: https://lukeocodes.dev/blog
          - "@type": ListItem
            position: 3
            name: "Friday fun: my .zshrc has more aliases than I have memory"
            item: https://lukeocodes.dev/my-zshrc-has-more-aliases
---

[Luke Oliff.](/)

- [Blog](/blog)
- [CV](/cv)
- [Uses](/uses)
- [User manual](/user-manual)
- [Living with ADHD](/living-and-working-with-adhd)
- [RSS](/rss.xml)

[Luke Oliff · Writing](/blog)

# Friday fun: my .zshrc has more aliases than I have memory

May 2026 · [Developer Experience](/blog/category/developer-experience) · 3 min read · [Luke Oliff](/authors/luke)

I opened my `.zshrc` the other day for the first time in maybe six months. Not to fix something, just curious. The file was two hundred lines long.

Two hundred lines of aliases, functions, exports, and one commented-out block that I think was related to a Raspberry Pi project I abandoned in 2022. I do not own a Raspberry Pi anymore.

### The archaeology of a config file

There is something weirdly personal about a `.zshrc`. It's a history of every tool you were excited about, every workflow you tried to optimise, every phase of your career. Looking at mine was like reading old journal entries.

I found an alias that opens a directory I haven't visited in three years. A function that formats AWS CLI output into a table - I was on a Vonage project in 2020 that used AWS for something I can no longer remember. An export for a Java home path from before I realised I never actually write Java and just kept the JDK installed in case.

The aliases were the most revealing. `alias dc="docker-compose"` from 2019, back when I thought compose was the Docker command I would use most. I don't use compose anymore. I probably should delete that line. I won't.

### The ones that survived

Some aliases made it through every clean-up though. These are the ones that earned their keep:

```bash
# this one I use every single day without thinking
alias gs="git status"

# pipe anything into this and get a quick transcript
alias stt="dg listen --output json | jq '.results.channels[0].alternatives[0].transcript'"

# the one that looks ridiculous but saves ten keystrokes daily
alias ..="cd .."
```

The `dg` one is my favourite. It pipes audio straight through the Deepgram CLI and gives me a transcript in the terminal. I added it the week the CLI launched and it's never left. That's maybe the test of a good alias: you forget it exists until you switch machines and immediately notice it's missing.

### What stayed after the clean-up

I deleted about forty lines. The things that went were the aliases for tools I no longer use, the exports for paths that don't exist anymore, and the commented-out experimental config I was never coming back to.

What stayed was about half the file. The core muscle memory stuff. Git shorthand, a few transcription pipelines, and some functions that I genuinely would not know how to do without looking up the flags.

I feel lighter. Not dramatically so. Just a little bit. Opening zsh now feels like opening a tidy desk, not a junk drawer.

Maybe that's the real value of a dotfiles clean-up. It doesn't save you time day to day. But it removes the low-grade background noise of knowing your config file is a mess. And that noise matters more than you think.

### FAQ

**How often should I clean up my .zshrc?**

When you open it and the first thought is "what is all this." About once a year for most people. More often if you switch jobs or toolsets frequently.

**What should I definitely keep in my dotfiles?**

Git aliases, shell navigation shortcuts, and any pipe you run more than once a week through a tool specific to your work. For voice AI work, that means transcription and TTS wrappers.

**Is a long .zshrc a problem?**

Not inherently. A long config file full of things you use is fine. A long config file full of things you forgot about is debt. The length is not the issue. It is whether each line earns its place.

[← Newer: 5 command-line tools for shipping voice agents](/5-command-line-tools-for-shipping-voice-agents)

[All posts](/blog) →

## Search this site

`GET https://lukeocodes.dev/search.json?q=<words>` returns matching posts as JSON, each with its page URL and its markdown URL. Add `&limit=<1-50>` for more than 10. How it works: [/blog/search](https://lukeocodes.dev/blog/search.md).

```sh
curl "https://lukeocodes.dev/search.json?q=developer+relations"
```

---

© 2026 Luke Oliff. Posts live at the root of this site.

- [GitHub](https://github.com/lukeocodes)
- [LinkedIn](https://www.linkedin.com/in/lukeocodes)
- [X](https://x.com/lukeocodes)
- [Bluesky](https://bsky.app/profile/lukeocodes.dev)
- [Email](mailto:luke@lukeoliff.com)
- [RSS](/rss.xml)

## Cookies

This site sets one analytics cookie, from Google Analytics, and only in a browser that accepts the cookie banner. A client that does not run scripts sets no cookies, so there is nothing to accept or decline here.

[Cookie policy](/cookies)
