Intern prep....
-
@BMarie said:
I'm not at the challenging stage yet. Sorry @scottalanmiller
Trying to be ahead of the curve.
Being ahead of the curve means having well-supported challenges. But I understand what you mean.
-
I have learned that after twenty-five years in IT, and thirty-seven years of exposure to computers - I still have quite a bit to learn.
-
@thanksajdotcom said:
For the record, I have won debates with two different engineers at NTG, both a current and former one. Both were regarding printers. I rest my case.
To be fair, Printers/MFPs/Copiers aren't IT they are machines. They are about as much IT as a car that is connected to a computer for testing/monitoring is IT.
-
@thecreativeone91 said:
@thanksajdotcom said:
For the record, I have won debates with two different engineers at NTG, both a current and former one. Both were regarding printers. I rest my case.
To be fair, Printers/MFPs/Copiers aren't IT they are machines. They are about as much IT as a car that is connected to a computer for testing/monitoring is IT.
They aren't strictly IT, but the context of both conversations was IT related. One was with @scottalanmiller about an HP printer and their terms as it applied to consumer/business applications. The other was with @alexntg in regards to a solution for a customer.
-
Knowing how to research and troubleshoot is the bulk of IT. If you know how to research products and have a base knowledge of the technology available, your possible wisdom is infinite. Of course experience plays a major role and how you implement technologies.
You will feel more comfortable once you dive into that lab and gain experience in research, troubleshooting, and test deployments.
-
@IRJ said:
Knowing how to research and troubleshoot is the bulk of IT. If you know how to research products and have a base knowledge of the technology available, your possible wisdom is infinite. Of course experience plays a major role and how you implement technologies.
You will fill more comfortable once you dive into that lab and gain experience in research, troubleshooting, and test deployments.
This times a GOOGLEPLEX!
-
@IRJ said:
Knowing how to research and troubleshoot is the bulk of IT. If you know how to research products and have a base knowledge of the technology available, your possible wisdom is infinite. Of course experience plays a major role and how you implement technologies.
You will feel more comfortable once you dive into that lab and gain experience in research, troubleshooting, and test deployments.
The test deployment won't fully compare you for a live deployment. Every IT person will tell you, that things can go wrong (even if its out of your hands) during deployments . Stay cool and focused on the issue(s). Once you learn this, deployments will be second nature to you. Of course our goal is to never have anything go wrong during a deployment, but realistically it happens even if it isn't your fault.
-
Seems like the nature of Interning is that you don't need to do very much prep for it.
-
@Reid-Cooper said:
Seems like the nature of Interning is that you don't need to do very much prep for it.
That was my thought
-
@thecreativeone91 said:
@Reid-Cooper said:
Seems like the nature of Interning is that you don't need to do very much prep for it.
That was my thought
she's just excited. Just have an open mind, and be honest if you dont understand anything. probly a pretty good group of folks to intern with.
-
@Hubtech said:
@thecreativeone91 said:
@Reid-Cooper said:
Seems like the nature of Interning is that you don't need to do very much prep for it.
That was my thought
she's just excited. Just have an open mind, and be honest if you dont understand anything. probly a pretty good group of folks to intern with.
They are.
-
There is a reason I'm still so close to so many of my former co-workers. It's just a great group of people.
-
@scottalanmiller said:
@thanksajdotcom said:
Also, don't be afraid to challenge Scott.
Change that to be afraid NOT to challenge Scott. Although far less as an intern than a staffer, but the sentiment is important. We are an idea company, not a hierarchy. I get emergency technical veto power when pushes comes to shove, but if I'm arguing with you, that means I'm not in a position to put the brakes on - keep arguing. If you have a good point, it should be defensible.
This is one of the things I've definitely noticed and appreciated about you. While others might see you as beating a dead horse, if you're still talking it's because it's clear that either your points aren't understood, or the other person is making points that might be changing your position.
-
@Dashrender thanks! I hope that is what I am doing. Sometimes I wonder if I'm beating a horse too
-
@scottalanmiller said:
@Dashrender thanks! I hope that is what I am doing. Sometimes I wonder if I'm beating a horse too
It's true.. sometimes the other wise just won't listen when they've clearly made a logical mistake, or more likely an emotional decision they don't want to fess up to.
-
I assume that some of it too, is that there IS a dead horse being beaten. To anyone who pays attention, the same conversations, the same reasoning is repeated over and over again. But the person who is at the center of the discussion is either "new" to wherever it is taking place or just hasn't paid any attention and isn't aware of how often the same things are said over and over including, very often, the same tired points that they make. They could easily look up other threads to see how other people made those same points and they were discussed and they didn't come out as the valid points. But they don't.
So to the people involved in the discussion directly, it's a new discussion (more or less, one can argue the semantics of ignorance) while to the bulk of the observers it is a dead horse being brought back for another beating.
-
I hear you. Though reading through the countless threads here or elsewhere is time consuming. So most people just want answer to their question, regardless to the fact that it's been asked 100+ times before.
No real good easy answer for that problem.
-
@Dashrender said:
I hear you. Though reading through the countless threads here or elsewhere is time consuming. So most people just want answer to their question, regardless to the fact that it's been asked 100+ times before.
No real good easy answer for that problem.
There isn't. It is just really hard to get people who do read all of those threads to them figure out how to handle see it for the 101st time. Do you berate the OP for not reading anything, ever? Do you link to the list of conversations that have come before? Do you jump in? Do you see the whole thing as the dead horse problem?
-
Exactly - if you berate them, you just end up hurting the community. But because people don't like to post the same information over and over again, you often get techs who are burnt out and give up on a site (kinda like I have for SW).
-
@BMarie, when people are waffling on about RAID arrays and you have no idea what they are talking about, here is a pictorial guide that I found a few years ago.
Ā
You probably won't need to know about this from day one but you might like it for reference later on.
