What should be Git for a novice developer?

Question

Career in IT

It's no secret that github is an important part of modern development. It is also viewed when selecting for a vacancy, especially relevant for those who are looking for their first job in IT.

Often there are comments on the Internet that you have zero git or your projects are worth nothing and are not interesting. It is clear that an enthusiast is interested in picking his "special" topic, but still, judging objectively, what kind of projects (character) should be in git in order to interest the company? For example for backend. As far as the project can be "raw"?

Answer 1

Github is completely optional, it's just an option that some people look at and others don't.
Don't bother if you don't want to do it.

Answer 2

I have a terrible github. Recently changed jobs (1.5g of experience). Of the 5 social security accounts, one was asked about github, I did not show it and said that it was a shame to show it. Technically raped, but they gave an offer. But when I was looking for the first job, every third interview they mentioned github and asked to show me something. And I didn’t have anything beautiful there ... Probably then it didn’t play into my hands

Answer 3

Here Git is just important - the coder should not fall into hysterics from the words "freeze" and "branch".
And the majority doesn't care about github as an entity. Especially if you can show projects OUTSIDE the github.

Answer 4

judging objectively, what kind of projects (character) should be in git in order to interest the company?

Any direction. They will look not at the functionality itself, but at the quality of the code.

Answer 5

The project(s) can be any(s). The main thing is that it was your work in them.
They will look at:
1. code quality
2. how you arrange commits
3. is there any development over time
4. are there auxiliary tool configs in the project
But we must remember that if there is nothing to show, then it is better not to mention github in the resume at all. Here is what I myself encountered and what directly repelled me when a candidate indicates a github in a resume:
- only forks of popular projects, without a single commit from the owner of the repository
- several projects, but everything is one size fits all: 1 commit - a standard github template, 2 commit - uploaded the entire project

Answer 6

It's like the spleen. You can live without her, but it's better with her, and even better that she be healthy. Here is the github - it is better to have, and it is better to have high-quality projects in it. Good turnips allow you to get much more responses, skip the test stage more often, sometimes it’s easier to go through social security (the story of the implementation of your project is a game on the candidate’s field). But if there is any rubbish in it, it is better without it.

Answer 7

in my opinion, the desire to see someone else's github is strange - for example, I throw everything there in general, my github is a rare garbage dump, and of course all projects are private,
I don’t remember that a sane employer would ask me to show the github

Answer 8

It is also viewed when selecting for a vacancy.

don't look at all