<- All posts

Why I build everything so simple

Simplicity is discipline at its peak. here's how I build web apps that are fast, maintainable, accessible, and boring on purpose.

Featured

By Dayton3 min read

If you didn't know before, there's homework-app. A homework tracking application that also acts as a mini Reddit, a journal, a seating arrangement generator using Genetic Algorithms (GA), and a probabilistic / GA group picker. I added way too many services (RabbitMQ, MongoDB, Redis, MeiliSearch, MinIO, Docker, Next.js, Rust, etc.), and they confuse me now.

I really want to say that the complexity was intentional, but past me just wanted to flex on myself. Now the tech debt is catching up. It's like a bad mortgage—promising in the short term, pure pain in the long term. I have no idea how to read the codebase anymore, and it has essentially become abandonware. I no longer maintain it... at least it's a good project to show off what I can do, even if it's not something I can practically maintain.


My definition of overengineering is when a website has way too many features for its scope—microservices for a two-page static site, RabbitMQ for tracking homework, or Redux where a simple useEffect would do. YAGNI (You Aren't Gonna Need It).

A good rule of thumb to avoid overengineering is to build things Boring on Purpose. Do not add RabbitMQ and microservices when a monolith will do. Do not add fancy animations if they end up being visually confusing.


I tried applying that philosophy directly to this blog post... please ignore that it still has KaTeX support. I built the markdown system earlier; decoupling KaTeX takes way too much effort, and besides, what if I want to write math equations in the future? Ooh, e=mc2e=mc^2.

  • Animations are as minimal as possible, and if prefers-reduced-motion is enabled, they don't run at all.
  • The background isn't distracting—just a subtle dot grid and a soft gradient at the top so it doesn't feel lifeless.
  • Cards on the front page are kept simple with clean hover states (which also respect prefers-reduced-motion).
  • Descriptions are kept at a straightforward reading level, because flashy vocabulary means nothing if people can't easily parse it.
  • And best of all: zero Redis and zero RabbitMQ.

The payoff?

  • 100 / 100 / 100 / 100 on Lighthouse desktop (and 90+ on mobile).
  • 0 pnpm audit errors for dependencies.
  • Friends and recruiters can navigate and understand the site immediately.
  • A tiny bundle size for a Next.js app.

Of course, there are always tradeoffs. Simple doesn't mean it scales forever with zero effort; you adapt when real problems show up (like following the rule of three).

"Simplicity is prerequisite for reliability." — Edsger W. Dijkstra

A complex system have a lot more attack surface, dependency chains, and fragile handling that developers miss. A simple one has leses of all of them, leading to a reliable sytem.

This blog post is rendered through that exact same pipeline. Clean markdown, as much server rendering as possible, and zero fluff.

Join the mailing list
Get new posts delivered to your inbox. No spam, unsubscribe anytime.