My first computer was the TI-99/4a, and unlike Tim's first computer, it had no geek cache' whatsoever. My parents purchased the computer from JC Penny's when the store decided it was never going to carry electronics again (a promise that they've kept for the most part, excluding the junk).
So, my parents exchanged $125 for any chance I had at normalcy. I am, of course, grateful for the experience, as I learned how to program in BASIC on the device (Basic programming is apparently a bad habit I will never break). Although I chronicle my experience growing up with the TI-99/4a here, I should mention that my big brother also had quite a bit of experience with the computer. He was the one that taught me several of the commands I would later use to create little programs that used the Speech Synthesizer, the joystick, etc
So, the point here isn't necessarily a trip down memory lane... I'd like to make a different point in this particular post:
It's hard to overstate the importance of having a mentor when you're a programmer or other technician.
I've seen programmers and network techs struggle throughout my career, and the MO is always the same: they have no one to look up to, they work by themselves, and they frequently are working in an area where they're trying to gain experience. It's so easy to hop down a bunny trail when it comes to tech - and when you do that, you might never be seen again.
Knowing others - networking - is important in a tech's career, and most techs get this pretty quickly.
But getting a tech that knows when to ask for help is another story altogether. I'm not talking about a person that'll never learn - one that asks the same questions all the time, but rather one that is constantly expanding their knowledge base. These are the types of techs that are rare: they're not looking for spec sheets, they're looking to understand and improve the business they're involved in. They take things personally.
These techs typically have the concept of mentoring in common; either they've acted as a mentor, or they've been mentored. I've done a bit of both, and can tell you, it's added an element of satisfaction to my career that's difficult to quantify.
In the early days, without my brother showing me what was possible on that little TI, I probably wouldn't have thought much about how things got onto the BIG GLOWING BOX. Later, as I was starting my career, I remember working with a guy named Kevin Zion. He took me under his wing and because of that, I learned a ton about servers / server administration. He was also a pretty fun guy - although I was running cables through walls (NOT fun), I remember the lunches and learning experiences there... Good stuff.
As you teach others, you'll learn pretty quickly what you really know and what you don't. If you sound confusing, chances are you need to know more yourself. If you're able to relay an idea quickly and clearly (relative to the complexity of the topic), then you know the topic.
Anyway - I'm not going to mention all of my mentors here, but I will say this - Thanks. If you've considered taking some time after work, or explained things to others, Thanks. If you're thinking that 19 year old intern needs some help understanding OO or Servers, or whatever, help the guy / gal out. I know I appreciated it, and we need all the good techs we can get.
No comments:
Post a Comment