Does anyone else here participate in the selfhosting hobby without a formal IT related education or a career in a similar field? I’ve only had one or two programming courses as part of my university education, but it was only very basic Python and C. I’ve never formally learned how to use containers, version control or anything else. Sometimes I regret not pursuing an education in IT/programming because there are so many things I’d like to accomplish but can’t (for example if there’s a feature missing in some project, or to feel safe in my abilities to harden my servers and my network in order to expose services to the open internet).
I have no formal training but have been in IT for over thirty years.
You write “participate” which sounds like a free choise, but I don’t do it out of my own free will. I do it because the web is so enshittified, that it forces me to selfhost more and more of my own websites that only I use.
I fucking hate doing any devops. I think it’s the most boring, soul sucking task there is. Fucking yamls and .env and config files in different places for every app with it’s own syntax.
I tried passing it to an LLM but it’s always subtly wrong, so in the end I still have to read everything, correct everything, generate keypairs, configure something on each client etc.
Every day a million bots are hammering my services, so I have to run crowdsec and fail2ban and make sure there are no ways in, everything is behind a login, up to date, constant manual migrations to newer versions cause one of my hunders of apps always has a breaking change.
I’ve written more devops and security related stuff on my CV than my carreer programming experience. I got a job because now I am not just a fullstack developer, but a fuller stack devsecops-veloper. Showing my homelab and docker setup during a fucking java + react interview landed an immediate yes at the wage that I wished.
I fucking hate devops. Now I have to do it in my free time and at my job. Why does the world force me into devops? Please take it away. Let somebody else handle it. I want to enjoy my life again.
/notsarcasm
Well, I’ve had a computer in front of me since the 70s. Don’t conflate longevity with knowledge tho. I’ve had no formal training, even tho I ‘ran’ the IT dept for a small construction company in another life. One of my jobs was to train old head construction workers on how to use a lap top, a digital camera, how to interface with our servers to upload data from the field. That was wild.
But, no formal training here. Most of what I know I learned by: Reading, screwing it up, doing it again, ad nauseam. And then when something worked, write that shit down.
Great post. For those who don’t know, breaking shit is a good way to learn.
Basically same here except Millennial timelines. I only really know what I use myself.
I only really know what I use myself.
That’s basically how I know just about anything. Hands on failure until it works. And when you think about it, success is merely a string of failures. Given that, I’m succeeding like a mofo. lol
I was that guy. And then ended up with that career partly because of it.
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:
Fewer Letters More Letters ISP Internet Service Provider LAMP Linux-Apache-MySQL-PHP stack for webhosting NAS Network-Attached Storage Plex Brand of media server package VPN Virtual Private Network
5 acronyms in this thread; the most compressed thread commented on today has 11 acronyms.
[Thread #78 for this comm, first seen 15th Aug 2026, 15:50] [FAQ] [Full list] [Contact] [Source code]
I work in the medical field. All my it IT skills are self taught, starting way back with coding in BASIC in C64 and taking apart RC cars.
With enough interest and persistence, you can learn what you need to. IT skills are pretty democratic.
Self hosting stuff is a great gateway drug because it introduces…complications. The path between A and B always seems to take detours, which is where the learning happens.
It’s interesting reading people talking about problem X, with everyone confidently advocating solution Y. I often find myself thinking “well, that’s not been my experience. I would just do A”.
It’s good to see how other people solve similar problems. Eventually you’ll arrive at that old homily “the way you do one thing is the way you do everything”, which is useful too.
Ultimately, just… start anywhere. Soon enough something will piss you off enough that you roll up your sleeves and work the problem - don’t look, but you’ll be learning those IT skills IRL without having to crack a textbook.
It’s always interesting when someone asks this question because while I do have a formal education in computer science. I’ve had this hobby since before I had that formal education. Linux and self hosting are what made me pursue the formal education part and not the other way around.
That’s funny since I didn’t even know what Linux was when I started my CS education, nor that there were so many services you could host yourself. I was egged on to try Linux and (eventually) get a small homelab by my uni friends, who were probably more like you
