Re: Re: Colej ejecashun

IT guy here.

Not sure why everyone seems to think it's so damn complicated (it really isn't - most people just don't pay a basic sense of attention under the guise that it's super complicated (their minds turn off)- kinda sad being this is coming from someone with ADD). It really depends on where in IT you want to end up, and who you end up working for.

Coding languages are for developers these days, you're not going to need to know every language in existence like in the old days when you had to code a mainframe in Cobol (and for those  extremely rare and fringe cases where Cobol is still in use, they have developers who write the code, you usually end up on the machine and networking side of things). Developers are going to blame their idiocy and inadequacies on you and your hardware. (99.9% of the time, it's not your problem) IT guys these days hardly ever code anything except when it comes to automation of their time consuming tasks. And to be frank you can pretty much do that with any language you chose to learn (C, Perl, Python, etc).

All protocols are standardized, while there maybe new protocols and whatnot in development, most companies try to milk their environment for every last drop of worth before they start adapting new ones. Great example of this, IPv6 (Internet protocol) has been in the works since circa 1998, and it has yet to be fully adopted. They got a 2020 goal for unilateral deployment, but there's only like 19% adoption (not sure on the exact number but it was like 10% last december) to it and we're out of available addresses on the internet and should have already moved to it years ago.

I still find guys running Windows XP and they're causing me problems because they're so far behind and can't correctly connect to my servers because they don't support modern encryption.

Technology moves at a blinding pace, but unless you're working Fortune 500 or at a lean startup, and depending on what you do, you're likely going to spend 90% of your life fixing "my email doesn't work" rather than deploying new groundbreaking technologies. Now, I'm not saying you shouldn't advance your career by learning these new things (you have to stay relevant in this field), but that I've spent a lot of my career doing so only for them to die or stave off in popularity to obscurity enough to know that with most companies your job is going to be maintaining an aging infrastructure and needing to maintain backwards compatibility with numerous clients that hate change. It's a thankless job. When everything is working you get asked "What do we even pay you for?" And when something goes wrong you get asked "What do we even pay you for?!"...

Enter this field if you desire to be constantly blamed for everything despite having undeniable proof of their inability to type in a password correctly let alone ensure they didn't rip their lan cable out of the jack with their foot. Be prepared for inexplicable failures and damage to hardware. Yes, that GBIC transceiver is flapping again. Yes, the one you just replaced.

It's not an easy job, but if you're up to the task, it's not the hardest.

Sent from my SM-G930V using Tapatalk