@MrMalachiCrunch:
Jermofoot, my job is not to inform you of what the rest of the world is saying about windows 8, YOU should be curious, if you are not then I really can’t help you.
I’m more concerned about what I think, and I’m fine with it at this point. It’s not perfect, I just think it gets a lot of undue criticism.
Education is good, I commend you on that. I would offer you some advice, learn linux as well. Your MS ticket can be declared outdated just like an older version of windows where support is no longer provided.
I do have some experience with Linux, however it is not a requirement nor worth my time for my current job as exactly 0 clients utilize it.
Microsoft cans three ‘pinnacle’ certifications, sparking user fury
http://www.theregister.co.uk/2013/08/31/microsoft_cans_three_pinnacle_certifications_sparking_user_fury/
Part of the risk with any cert, but there is reason behind this. Did you read anything beyond this article? They will simply be unavailable, will have a replacement, and do not devalue the certification of those that already have it/will have it before the retirement date.
You might be interested in this…
Windows 8.1: Microsoft’s reluctant upgrade has a split-screen personality
http://www.theregister.co.uk/2013/09/12/windows_eight_one_review/
Thanks, I just kinda skimmed it for now, will read it more in depth later. So far, for work very few people are using Win8 just yet. Most are on XP, haha.
@MrMalachiCrunch:
Jermofoot, really? I would qualify your statement with “some”, especially at microsoft. Do you personally know a developer?
I wrote a really quick response on my break, so not the best phrasing. What I was meaning was that all developers of O/S have lifecycles for their products, where support ends. This is reasonable, and to expect otherwise is ridiculous.
Extends hand…. Pleased to meet you Jermofoot. If you didn’t know a developer personally before, you do now. I fancy myself a renaissance man so I won’t claim I have 31 years of software development just because I got paid for my first program in 1982. But over the years I obtained a 4 year BSc in computer science and software I wrote over 15 years ago is still running just fine on fortune 500 companies and in fact some modules are still being sold unchanged 15 years later. Of course, I didn’t weld my software to microsoft solutions. I modularized them and my modules still work and sell whereas the modules where I isolated microsoft specific technology don’t. Microsoft broke them. Specifically the MDAC dll database connectivity stuff. RDO upgraded to ADO then upgraded to ActiveX gosh all over the span of 4 years. All quite defunct now. All the database stuff switched over eventually from SQL server to a linux based and now cloud based system. My modules STILL work untouched in the new paradigm.
I’m glad for you, that’s wonderful. And while I will defer to your expertise on programming, I can see a situation where older deployments/builds will not work as technology advances, or vulnerabilities are addressed - where a new platform is adopted and older ones are obsolesced. In a vacuum, many things can work just fine, however that never seems to be case in real world deployment.
Software and operating systems don’t have to break every few years. You should research emulation, you’d be surprised how many legacy software solutions are running decades and decades later on simulated computers running on cloud platforms.
I’ve brought up emulation and virtualization in this very thread and have noted it’s uses. In one such example, I had to deploy an XP virtual machine to install 32-bit software that updated their compliance info at a bank when printing their forms. This software was 15 years old at this point and the company was just NOW creating an updated software for newer OSes and 64-bit environments. It was quite the hassle and unnecessary, but we made it work for the time being. However, I don’t think in all cases should it be approached as “if it ain’t broke, don’t fix it” - there are real needs to address that spurn updates and upgrades, not to mention efficiency and functionality in general. Not in my example, mind you, but overall I think this is true.
Just be flexible with technology ‘camps’ and diversify the knowledge portfolio.
I agree, and at some point it will become that. I have quite a track to choose from as I work my way through rudimentary and required certifications off my job (MCSE 2012 and CCNA). From there I can branch out into whatever interests me. However, by and large it deals with Microsoft products and while not on 2012 for the most part, some are and more will at another time. Most places lag behind from the release to when they actually employ it, and that’s been no different than the late 90s when I got my MCSE NT 4.0 - it took quite some time for anyone to move to Server 2000.