[projektfu]

There's a lot that a hobbyist might find interesting from a technical standpoint that has no real relevance to their life. For example, you could learn Kubernetes as a hobby, and mess around with container orchestration, but why? What do you hope to get out of it? You could try to do a deep dive into enterprise architecture. But again, for what purpose? Hobbyists might want to make something functional, or beautiful, or solve problems, or just know they can do it. But they usually don't want to go around solving big-corp problems for free.

If you're wondering about content like Rust or Haskell programming, the jargon and implied knowledge can be a little intimidating. A lot of early Rust users were coming from advanced modern C++ and/or functional programming (FP) and use those concepts freely without assuming people might yet need to learn them. A lot of Haskell people have learned ways of thinking from other Haskell people or other FP people and they don't feel the need to explain what they're doing all the time. But it is intimidating. However, it can also be fun.

I'm the worst kind of hobbyist. I almost never create anything anymore. When I do, I usually don't use the cool stuff, just some Python, shell, or Awk. But my hobby is learning about this stuff, what people are doing, and trying to figure out how people are thinking in different ways. So I have done a bit of functional programming and read a lot of code. I find it fascinating. But nothing I have made in that area is worth looking at.