[nitrogen]

I do think this is for the best. Education, whether traditional or applies technical, shouldn't be locked to a single vendor. This may make hiring harder, but other certifications will arise, and in the mean time qualified but uncertified applicants might have a better chance at getting employed.

[syshum]

That depends, there is absolute a place for Vendor Certifications. There should also be general and non-vendor certifications.

I dont believe MS doing away with all OnPrem Certifications is "for the best"

[jasoneckert]

Nearly all colleges are not locked to a single vendor - CompTIA, Cisco, EC-Counsil, LPI, Red Hat, etc. are taught equally. The point I was hoping to convey earlier was that Microsoft is now going to disappear from that vendor and organization list.

[tarellel]

I beg to differ, I went to a community college and everything was locked in to Microsoft; certs, software, and MS approved coiurse guidelines (MS had given them some sizable grants to push the students to leave and use their products. I know work for our states biggest university and it’s still the same way. Literally out of thousands of employees our small group in IT are the only ones using macs and building/deploying products in a Linux environment. Being in the position I’m in allows me to get a look at the other Colleges/Universities across the state and it’s pretty much the same process across the board. A fair enough chunk of CS students coming in are disappointed about the M$ based CS tracks. They came in expecting to learn Linux, Python, Ruby, JS, Docker, and k8s. I’m hoping in the future in the CS guidelines will diversify and let people choose either a OSS/programming, MS, and Cisco/Networking tracks to be a little more open to real world needs.

[rjbwork]

I'm surprised there's any emphasis on Windows in a CS course. I'm a C#/cloud dev and I use Windows as my daily driver, but we were allowed to use any OS we wanted. Only catch was that for some courses our final projects had to run on the school's Linux server, which we could SSH into and compile and run our code on.

[gerdesj]

Good riddance. I say that as the owner of an MS Partner! I want potential consultants, not people with one trick up their sleeve.

Blow Red Hat: I want an applicant describing how they installed Arch or Gentoo and only use say RH or whatever to tick supportability boxes for something. Someone who can install Gentoo already knows how to fix all other broken Linux boxes, without breaking into a sweat. A completely broken Linux box does not faze me because I spent many years repairing the fallout of running emerge.

Cisco. Hmm well at least it is reasonably easy to translate into Dell or HP. Juniperese on the other hand is rather different. Given that Cisco invented nearly everything including some horrendous security exploits, I'll let that slide!

[freedomben]

What do you mean by, "Blow Red Hat?"

[gerdesj]

Sorry, en_GB. "Blow" something here does not mean what most people would translate it to, ie a sexual act.

"Blow that" or in this case "blow RH" here means the object of the phrase is not wanted. It is a reasonably polite way of putting some emphasis on saying "that's not for me." A more aggressively emphatic idiom could be "fuck that" or "fuck RH".

If you heard me actually speak it, instead of type it would probably make sense! I should probably lay off the idia and fall into line with generic en_*.

Bugger that!

[freedomben]

Haha, no worries, thanks for the explanation :-)