# Init III, Another One

###### Jul 27, 2024

Hi, I'm Dave _\*(Group: Hi Dave)\*_ , and I have a refactoring problem.

I re-did this website. Again. And moved hosting-servers. _Again_. Am I happy with how it is right now? Sort of, yea. Will that change in a few months? Given history, probably. But someone has to stop me, because clearly that person isn't going to be me.

On the positive side, the way this refactor ended up, I think I've given myself room for future expandability: better possibility for addition of front-end bits, cleaned up the backend (or, dare I say, _Gleam-ed up_), and made the deployment process nice and easy.

There's something nice about starting a project over and redesigning it from the ground-up, sometimes...

...well, only if you finish it. There's a few projects in the backlog of my mind and behind the curtain of my Codeberg sitting in partial states, but in time I hope to complete them.

Refactoring and reconstructing is often viewed like it's the worst idea of all time ever, and there's definitely merit to that. The larger the application, the larger the length of time needed to remake it, and projects that make money or lack resources can't justify spending the time on redoing a functional product.

But perhaps in smaller bouts, like some `chore/refactor_this_small_bit` branches accumulated over time, you can prevent a complicated cobbled-together amalgamation of _x_ many contributors writing _y_ different ways to write code. Or one developer evolving with new strategy and tooling, now fixing flaws of past decisions.

Or if you're one sole person making your own personal link-tree/blog/knowledge-resources(someday)/who-knows-what-else(-or-when) website, just strike it all and do it again.

Or don't do that last one. Maybe.

Anyway, it's been done. So, hello world... **again**.