For further actions, you may consider blocking this person and/or reporting abuse
Read next
Linux Text Cutting: Mastering Text Manipulation in the Wizarding World
Labby -
C# System.Text.Json JsonConverter masking
Karen Payne -
Finding the Right Job (OTB Ep 1: Jennifer Rorex)
Jason C. McDonald -
Using Guard Clauses Instead of Try-Catch in Async/Await: A Clean Coding Technique for Readable and Maintainable Code 🦄🚀
muthu raja -
Top comments (2)
I can’t say if Github is a measurement tool but I’ve heard that some companies do check your github and stackoverflow account to get a sense of how you work. Although I have no idea if this is the rule.
As to how to get started with github I’d say that 100DaysOfCode is a great way for you to get started. You will work on problems - one per day and keep a log. Everyday you push the new entry to github and get a nice green box saying that you pushed something on github.
If you would like to contribute to open source you can check firsttimersonly.com here you can see open source projects that need help with something and are very beginner friendly.
Also, contributing to/with documentation is very valuable even if you feel that is a bit pointless as you are not coding (or barely).
Hope this helps you a bit, if you need any further help let me know
I agree with Fabio. We do like when a candidate adds GitHub link (especially students).
We generally use GitHub to check if the technologies listed in the resume matches with any of the technologies listed. Although it doesn't play any major role in the decision making process, it does gives an idea about the candidate. Sometimes, We do check the coding style/commit frequency/level of difficulty in the problem solution, especially when he's short listed for the final round.
Also if they have any open source contributions, it tells that We don't need to train the candidate on 'git' and 'Pull Requests' after he joins the team.