lunos
(Lunos)
1
Hi Guys,
Just an interesting though as in terms of being in IT long term I’m quite new to this however something interesting just hit me.
Would it be having a long experience/time working in IT is the best for giving you knowledge is the best or would it be the timing i.e. having 5 years of knowledge from when Computing first started or having 5 years knowledge of what IT is like from 5 years ago?
What would you believe to be more valuable?
Let me know,
Lunos
8 Spice ups
sqlrage
(SQLRage)
2
What computers were when they first started is irrelevant.
Same with 5 years ago, unless your company just has really old tech.
What they are now and what they are in the future is much more important.
3 Spice ups
rojoloco
(RojoLoco)
3
If you have knowledge of the first 5 years of computers, you are a relic.
If you have knowledge from 5 years ago, you’re still behind the curve.
Ability to adapt to the newest, changing technologies is what you want.
3 Spice ups
lunos
(Lunos)
4
I just thought it’d be interesting in the sense of “I have 10 years in It/networking” (From early tech) in comparison to “I have 3 years experience in It/networking” from more modern tech and how companies would go about identifying what is perhaps better for themselves and the individual they potentially may hire
Current knowledge is always better then old tech knowledge unless you are going to support nothing but the old tech till it burns up.
1 Spice up
rojoloco
(RojoLoco)
6
But the best scenario is to have (for example) 10 years experience in the last 10 years (like up until last week or last month). Gaps in experience are red flags to employers.
1 Spice up
“Those who forget history are doomed to repeat it.”
That being said, my knowledge of Apple ][+ hardware is of little use today… 
Knowing the history helps with the “Why?”, which can sometimes help with the “How?”, or at least in diagnosis (the “What?”). Knowing the history also lets you recognize trends - for instance, all the hoopla over “Cloud Computing” is little different in concept than the old mainframe model. The more history you remember, the easier it is to learn the new stuff as it comes along (“Oh, that’s the same as ‘xxx’, but with a new twist - I get it.”)
In short - never stop learning the stuff that’s *now.* You’ll naturally build up your own internal knowledgebase and IT history along the way.
1 Spice up
If you have someone with a decade of experience from a decade ago, that’s not worth as much as someone with three years experience starting from three years ago (i.e. - current).
But - if both candidates are current, but one has more years of experience, then, *generally,* the one with more experience will be a better asset. They (should) make fewer mistakes (having made many of them already), and will recognize problems faster (having seen them before), and apply solutions quicker (having done them before).
2 Spice ups
epmageor
(EPMAgeor)
10
I would hire someone that has 3 years experience from a job he quit yesterday over someone who has 10 years experience from a job they quit 3 years ago. Tech changes too fast, that even if they have 10 years experience, all that means is they have soft skills that are useful in IT, but lack the tech skills
1 Spice up