(July 9, 2012 at 7:27 pm)Napoleon Wrote: If their job is installing routers and software, which you admitted they can probably do better than you, and not their job to learn about what the configuration is actually doing, then why would you be hired for the job and not them?
Because I can offer more, do more, expand my value for more.
On a deeper level, because I'm trained in design, analysis, software development, I can learn and make those same IT networks.
In fact, I can usually do it better because I know exactly that is needed and can assemble a custom, small set of equipment.
Show me an IT tech who does all that and I'll show you a developer (and not the run-of-the-mill IT monkey).
(July 9, 2012 at 7:27 pm)Napoleon Wrote: I reckon both have positives, ofcourse there is more knowledge from a computer science guy than an IT guy about computer systems as a whole, but I think IT is just as relevant as computer science, they just lead you down different paths.
From the business perspective, the man who makes the stuff that brings in the bacon is more valuble than the man who sits on the equipment all day like an expectant hen.
An IT tech is to an actual developer like a automechanic is to an mechanical engineer.
Apples to Oranges.
Less valued apples.
Slave to the Patriarchy no more
