When hiring, I ignore certifications at best and actively discount them at worst.
These things generally mean very little and seem designed to extract money from large corporations with an education budget.
GitHub Certifications (Beta)
71–80 of 129 posts
Re: GitHub Certifications (Beta)
#72I hate these types of certifications if only for the fact that I get asked by people outside the development community if getting the cert will help them enter the community and get a job.
I always have to give them a deflationary speech about how software development is about the practice and not a one-time certification.
Re: GitHub Certifications (Beta)
#73Earlier quoted context omitted.
> Personally I've found certifications are a good way to show you're good at passing certifications, and nothing else. Some are good. I did AWS Solution Architect Pro, and this one was tough, one needs years of hands on to pass. Anyone with this one will get an instant plus in my book. I did not bother renewing it though, after 3yrs expired :)
Being difficult != good. It can take years to prep and pass a CCIE as well but it’s not really a good indicator of being a good network engineer, despite the esoteric protocol details you have to memorize.
> Being difficult != good.
I did not say that. I said some are good, and named one.
Re: GitHub Certifications (Beta)
#74Earlier quoted context omitted.
I got an MCAD once because my employer was offering it for free. This was so they could secure a "partner" status and get a license discount. That's mostly why people bothered with it. It was completely no use whatsoever. In fact looking back the contents were stupid and dangerous.
got an MCAD once because my employer was offering it for free. This was so they could secure a "partner" status and get a license discount. Same here, but MCSE used to come with all sorts of goodies like a free TechNet subscription. That ceased long ago however.
Indeed. Although now I just fire up an instance in AWS for a bit if we need to play with something. But I rarely if ever touch windows now past using it as a shell for some electron apps and terminals :)
Re: GitHub Certifications (Beta)
#75Ugh, this has Microsoft's playbook written all over it. Introduce a certification, thus increasing the gap between developers who (had their employee) pay Microsoft and developers that didn't. Conflate a generic concept (Git in this case) with Microsoft's specific implementation (Github), muddying the difference in managers' lexicons. Attempt to set Github as a standard to reach in everyone's mind. I mean there's a c…
> Introduce a certification, thus increasing the gap between developers who (had their employee) pay Microsoft and developers that didn't. Did anyone ever take Microsoft's "Microsoft Certified Application Developer" or "Microsoft Certified Solutions Architect" titles seriously? I was still in high-school when I heard about it. I asked some SWE friends of mine who told me that they didn't take it seriously due to the…
Did anyone ever take Microsoft's "Microsoft Certified Application Developer" or "Microsoft Certified Solutions Architect" titles seriously?
Most developers generally didn't, but certainly back in the early 2000s I heard lots of managers and other people responsible for hiring being impressed by it. To be blunt, if you where a mediocre developer with a mediocre resume, it was for a while a pretty efficient way to stand out among other mediocre developers.
Microsoft also used to offer some nice goodies and discounts to Microsoft Certified Professionals that could make it worth having, financially, if you where a freelance developer or worked for a smaller company.
Re: GitHub Certifications (Beta)
#76I hope this dies. I've been around long enough to remember the hell of Java certifications in the late 90s.
We have AWS and Google cloud certifications though. I don't find those any less "enterprisy" than Microsoft to be honest. And they definitely remind me of the Java certificates of the 90s.
Re: GitHub Certifications (Beta)
#77Earlier quoted context omitted.
Github recommended that you choose a license even before MS acquisition
Sure, but it's a poor choice for the one statement that "best describes a project to be truly open source"
Yeah that's weird, it's incomplete basically. As if the question were 'what's potentially more open source, licence or no licence?'
Re: GitHub Certifications (Beta)
#78Dumb enterprisey 'certification' aside, I can see the free course being effectively used during onboarding (esp. intern/grads, but anyone can not have used GitHub or even git before, just because it's not what previous employer used) at which point being 'certified' becomes a handy 'get out of going through that again' card...
Re: GitHub Certifications (Beta)
#79We will soon be able to hire github certified engineers. Thanks Microsoft, talent driven towards the skills our industry needs will make us all more productive: https://youtu.be/rR4n-0KYeKQ
for the down voters, I'm pretty sure this is satire
Re: GitHub Certifications (Beta)
#80Who is seriously looking for these things? If you are still hiring based upon what certificates a person has, I have some really shitty news for you.
If I wanted to know if someone could use GitHub, I would ask them to get on a Teams screenshare and tell them to set up a pull request for something quick, like the repo's README.md, link it to the issue and adjust labels. That would tell me in 60 seconds everything I needed to know about the experience level someone has with GitHub.
Anything beyond code, issues, labels and pull requests is just one-time configuration or occasional project management duty. Not really a whole lot of complex scary shit going on here. I don't really see the need to start credentialing people for operating within what is arguably the least risky domain for newcomers when it comes to software engineering. Absolutely worst case you just revert your prior commit or re-open the issue...