|
|
|
|
|
|
by bob1029
2066 days ago
|
|
|
Who 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... |
|
|
The mass recruiters (or modern indenture owners) that import and place engineers by the bulk. They don't have the time to bother looking for actual practical skills.