Switching to backend

11-26-2025

a solarized image of a crane

So it seems that I am changing paths... again... OMFG, will you stick to one thing already?

Well, I think that it's not too bad because each time I change I'm refining my path a little bit.

Before, I was on the JS fullstack path mostly because I naively saw frontend as a necessary entry point; but as I move on I am feeling more and more clearly that what really interests me is the backend. Not that frontend doesn't have a lot of interesting parts, it does, but I think my interest in the frontend ends at having a good-looking but simple, minimalist personal page; after that it gets too tedious for me to think about design, color palettes, or SEO... —I really hate SEO, I don't understand why everybody just keeps playing Google's game without question. I like basic things, as in, things related to the base, the essence, low-level, how servers and networks are built. I like to know how things work from the ground up.

I think that's been a constant in my life: it's the reason I chose the bass and not guitar, it's the reason I learned how to make sourdough bread and not desserts, the reason I'm attracted to classical literature and nature.

But for now I'm testing, because backend does have a lot of things that seem pretty daunting to me but at the same time intriguing.

I found this course that apparently everybody and their mom is doing right now called boot.dev, so not breaking my head thinking too hard on the roadmap. A part of me is tired of thinking about what to study and just wants to follow some short, cozy, fun lessons on a roadmap that's carefully planned by someone who knows a lot more than I do. I do think that there's a value in forging your own path; but for now I'm gonna take a little rest from that and see if this one takes me where I want to go.


index