Being an omnivorous technology generalist is punishing to start out as and lasts for years, but becomes incredibly valuable later. That's something I wish I could have told the prior me.
Come to understand: Being a generalist is not about "lacking experience to call yourself an expert." Touching on innumerable disciplines is itself a crucial skill that lets you operate in the real world with huge autonomy. Just know your limits. Most problems don't need specialists. Generalists are the ones that ***know when to call in the specialists and give them what they need***.

I'm an IT generalist. I can troubleshoot 801.x authentication based on event logs. I can write basic SQL queries to ascertain if data is there. I know routine basic coding errors in the theory of user authentication.

And that is enough. It is enough for almost anything I get called about. And that is why I am pinged by random people chatting me each day. When I am not enough I get you to the specialists. Because I know they exist. Because I know what I don't.

@SwiftOnSecurity I never really thought about it before, but you just described what I am. I like that term "Technology generalist."

Part of it is awareness of what others are doing and then also being able to communicate things out and I feel like a lot of dedicated specialists get tunnel vision and don't look at other views that they don't consider.

I didn't set out to become a generalist, but it was just a result of what I did kept shifting. Thanks for giving it a name.