i killed my old blog
i killed my old blog.
not because it looked bad.
not because it was broken.
i killed it because i made it too complicated.
it started simple.
just a place to write and share ideas.
but then i kept adding things.
more api routes.
more features.
more logic.
i told myself i was “improving” it.
but really, i was just overengineering.
after some time, it stopped feeling like a blog.
it felt like a system i had to manage.
then traffic started growing a bit.
that should have been a good thing…
but it made everything worse.
more requests.
more edge function calls.
more cpu usage.
suddenly, i wasn’t writing anymore.
i was fixing things.
optimizing things.
worrying about performance.
all for a blog that barely had content.
that’s when it hit me:
this isn’t what i wanted.
i didn’t start a blog to manage infrastructure.
i started it to write.
so i made a decision.
i didn’t refactor it.
i didn’t try to optimize it.
i killed it.
and i built this instead.
something simple.
something i can actually maintain.
something that lets me focus on writing.
no unnecessary api routes.
no complex setup.
just posts.
this blog is an experiment in doing less.
we’ll see how it goes.
if you’re building something,
don’t turn it into a system before it needs to be one.