Digital Minimalism: Cleaning Up Your Digital Life

How I pivoted from digital hoarder to minimalist engineer. Cleaning up local environments, cloud resources, and mental clutter to ship faster and learn harder.

Every day, you wake up and the internet screams at you. New JavaScript frameworks. A new AWS service that does exactly what the old one did but costs 10% more. Slack notifications. Jira tickets. The endless scroll of "hustle porn" on X.

If you are trying to build things-real things, scalable systems-this noise is the enemy. It is friction. It is latency in your brain.

I used to run a high-volume WordPress shop. I managed dozens of sites, hundreds of plugins, and thousands of database tables that I was too scared to delete. My digital life was a hoarder’s paradise. It worked, but it was heavy. It was slow.

Now that I’m pivoting to Cloud Engineering and Indie Hacking, relying on stacks like Next.js and Supabase, I realized something critical: You cannot build scalable, high-performance systems if your own digital environment is a dumpster fire.

Digital minimalism isn't about having zero apps or a blank desktop wallpaper. It's about optimizing for signal and killing the noise. It is about reducing the cognitive load required to start working.

Here is how I cleaned up my digital life to ship faster, learn harder, and keep my sanity while tackling a Masters in Cloud Computing.

The Browser Bankruptcy

Let’s start with the portal. The browser.

I used to be that guy with 60 tabs open. You know the type. "I'll read this documentation later." "I need this StackOverflow thread for a bug I might encounter in three weeks."

This is RAM abuse, sure. But it is also mental abuse. Every open tab is an unfinished task loop running in your subconscious.

I declared bankruptcy. I closed them all.

Now, I use a strict system. If it’s not relevant to the current feature I am shipping or the current assignment I am writing, it gets bookmarked or it dies.

I switched to Arc Browser recently. It forces you to organize. But the tool doesn't matter as much as the rule: One context, one window.

If I am coding a SaaS dashboard, I have one window open. It has localhost, the Supabase dashboard, and the Tailwind docs. That is it. No email. No Twitter.

The Local Environment: removing the friction

Nothing kills momentum like npm install errors or a cluttered terminal.

When I moved from generic freelancing to serious engineering, I had to treat my local machine like a production server. It needs to be deterministic. If my laptop explodes today, I should be able to be up and running on a new one in 30 minutes.

This meant standardizing my dotfiles and cleaning up the bloat.

I audited my installed packages. I had global npm packages from three years ago. I had Docker images for projects I finished in 2021. This is digital plaque.

I wrote scripts to nuke the garbage. Here is a simple alias I use to clean up Docker, because Docker is the biggest hard drive thief in existence:

# In your .zshrc or .bashrc
alias docker-nuke='docker system prune -a --volumes'

I run this weekly. It hurts to redownload images sometimes, but it keeps the machine lean.

I also standardized on a package manager. Homebrew for everything on Mac. If it's not in Brew, I question if I really need it.

For my development directory, I stopped naming folders test, test2, final-project-v3. Every project needs a proper name and a Git repo. If it's not worth pushing to GitHub, it's not worth keeping on my drive. I wrote a script that scans my dev folder for directories that haven't been modified in 3 months and aren't git repositories. It lists them, and I delete them.

The Stack: Minimalism in Code

Digital minimalism extends to the code you write.

In the WordPress world, the solution to every problem was "add another plugin." Need a contact form? Plugin. Need SEO? Plugin. Need caching? Plugin.

This creates a web of dependencies that is impossible to secure or scale. It is maximalist chaos.

Moving to the Next.js/Supabase stack was a breath of fresh air because it enforces minimalism through architecture.

I don't need a separate server for authentication. Supabase Auth handles it. I don't need a complex API layer for simple CRUD. The Supabase client handles it.

I don't need 50 CSS files. I have Tailwind.

Tailwind CSS is controversial, but it is the definition of digital minimalism for a developer. You aren't context-switching between a .js file and a .css file. You are styling right where you define structure. It reduces the file count. It reduces the mental overhead.

When I build now, I use Shadcn UI. Why? Because I don't want to install a massive component library like Material UI that brings 5MB of JavaScript I won't use. Shadcn gives me the code. I own it. I can delete the parts I don't need.

Here is what a minimalist component looks like in my codebase. No external stylesheets, no complex state management if it's not needed. Just pure functional UI.

import { Button } from "@/components/ui/button"

export default function CTA({ action }) {
  return (
    <div className="flex flex-col gap-4 p-6 border rounded-lg">
      <h2 className="text-xl font-bold">Ready to Ship?</h2>
      <p className="text-muted-foreground">
        Stop configuring. Start building.
      </p>
      <Button onClick={action} variant="default">
        Deploy Now
      </Button>
    </div>
  )
}

Simple. readable. minimal.

Cloud Hygiene: Your AWS Account is a Mess

I see this all the time now that I am deep into cloud engineering. People treat AWS accounts like a limitless hard drive.

They spin up EC2 instances to test something and forget them. They create S3 buckets with random names. They leave unattached EBS volumes that cost money every single month.

This is digital clutter that hurts your wallet.

In my Masters program, we deal with Azure and AWS. The first thing I learned wasn't how to provision servers, but how to kill them.

I use Infrastructure as Code (IaC) for almost everything now. Terraform or Pulumi. Why? because it acts as a manifest of my digital existence in the cloud. If it's not in the Terraform file, it shouldn't exist.

When I want to clean up, I don't have to click through the AWS console looking for hidden resources in the wrong region. I just run terraform destroy.

I also use AWS Budgets. It’s not just about money; it’s an alarm system for clutter. If my bill goes over $10, I know I left something running. I investigate immediately.

Digital minimalism in the cloud means using tags. rigorous tagging. Every resource gets a Project and Environment tag.

resource "aws_instance" "app_server" {
  ami           = "ami-0c55b159cbfafe1f0"
  instance_type = "t2.micro"

  tags = {
    Project     = "SaaS-MVP"
    Environment = "Dev"
    Owner       = "Emmanuel"
    ManagedBy   = "Terraform"
  }
}

If I find a resource without these tags, I kill it. Ruthlessly.

The Information Diet: Protecting the Input

As engineers, our output is code and systems. Our input is documentation, tutorials, and tech Twitter.

If the input is garbage, the output will be garbage.

I realized I was hoarding information. I had a "Read Later" list on Pocket that was 500 articles long. I had YouTube playlists of tutorials I would never watch.

I deleted the lists.

This sounds scary. "What if I miss something?" You won't. If a technology is important enough, you will hear about it again. If a tutorial is vital for your project, you will find it when you need it.

I adopted a Just-In-Time (JIT) learning strategy. I do not study Kubernetes just in case I might need it one day. I study Kubernetes when I have a cluster I need to deploy.

This keeps my mental hard drive defragmented. I learn what I need to ship now.

On social media, I unfollowed the noise. I don't need to see hot takes about how "AI will replace developers" every 10 minutes. I follow builders. I follow people shipping code. I follow official accounts for the tools I use (Supabase, Vercel, AWS).

If an account makes me feel anxious or inadequate, unfollow. If an account teaches me something, stay.

Notification Zero

My phone is permanently on Do Not Disturb.

My laptop has zero notifications enabled. None. No Slack popups. No email dings. No iMessage.

Context switching is the most expensive operation for a human brain. It takes about 23 minutes to get back into deep flow after an interruption. If you get interrupted every 15 minutes, you are effectively never in flow.

You cannot write complex backend logic or debug a race condition if your watch is vibrating because someone liked your tweet.

I check email twice a day. Mid-day and end of day. If it's an emergency, they will call (spoiler: it is never an emergency).

The File System: The Second Brain

I used to scatter notes everywhere. Apple Notes, Notion, random .txt files on my desktop, physical sticky notes.

I consolidated everything into Obsidian.

Why Obsidian? Because it's just markdown files locally on my machine. It’s minimal. It’s future-proof. If Obsidian goes bust tomorrow, I still have my text files.

I use a simple folder structure:

Inbox: Where new notes go initially.
Projects: Active work (Indie hacking apps, Freelance gigs).
Areas: Ongoing responsibilities (Cloud studies, Finances).
Resources: Reference material, code snippets, config cheatsheets.
Archive: Dead projects.

Every Sunday, I clear the Inbox. File it or delete it.

This "Second Brain" allows me to dump my thoughts out of my head so I can use my actual brain for processing logic, not storage.

Conclusion: The ROI of Less

Since cleaning up my digital life, my output has doubled.

I’m shipping features for my SaaS projects faster because I’m not fighting my environment.

I’m absorbing my Cloud Computing coursework better because my attention isn't fractured.

Digital minimalism isn't about being an aesthetic monk. It is about being a professional. It is about respecting your tools and respecting your own mind.

We build complex systems for a living. Don't let your life become a legacy code monolith that you're afraid to touch.

Refactor your digital life. Deprecate the noise. optimize for the build.

Now, close this tab and go ship something.