Hello! I was doing some thinking today and figured that rather than bouncing ideas around in my own head, I'd borrow your heads too.
I've been working in my current position for about 2 years now. I've gone from having a *very* basic understanding of Python and nothing else, to being the sole internal IT guy for a 150-ish person business. And to be frank, I'm good at what I do. However, I've learned just about everything I now know by having problems that need to be fixed, finding the solution, then pattern-recognition-ing my way through future issues. This gives me a great practical understanding of concepts, but I'm now noticing that my knowledge feels... almost *too* practical, with not enough theory to back it up.
I've set up and done troubleshooting on our domain, IP phone system, individual workstations, networking, etc. and I've built programs myself for various use-cases in the business, as well as working on various projects in my own homelab. But I don't have the intuitive verbal connections for what each part I've worked with is actually called. Like when I fix issues I go "Based on the symptoms the thing is failing at This Part, which is fixed at This Point of the process. I can fix it by doing That". But then I talk with any other IT guy and I immediately feel like a poser wearing merch for a band I've never listened to.
"The computer's IP was resetting on startup occasionally, I guess another device could take that IP if it was powered off for long enough, so when it came back on it was given a new IP which the service wasn't prepared for."
"Oh do you guys normally have issues with DHCP leasing?"
".... huh?"
With context clues, I figure DHCP is the method used to assign IPs, and a lease is how long a device can retain it's IP (With a quick google search to confirm). But needing to use context clues for basic A+ level stuff makes it feel like I don't have a basic understanding of fundamental concepts. I'm sure there's an argument for being effectively "book smart" versus "street smart", but this is more about the feeling that if I can't effectively communicate with the correct terminology, then obviously I don't understand those concepts, which means I've just gotten lucky up to this point, and eventually someone is going to figure it out.
The obvious solution is to go ahead and just get my A+ certification, which I'm now getting the ball rolling on and thankfully not struggling with, but I wanted to see what you all thought. I know IT folks run on collective knowledge and constantly learning, but does there come a point for you where you feel like you only *really* know just enough to get by? Or that by not retaining enough specific information you're not "part of the club"? How can I come back from having my foundational knowledge be 2 years of Tutorial Hell?
Edit: Just wanted to say thank you for the kind words. Definitely comforting to know I'm not the only one, and that worrying about it in the first place is apparently a good sign. I'll keep plugging along, overall I love my job, just get a little caught up in stuff like that from time to time. Wishing you all an uneventful week!