I would like to point out that if you are going to use a repository SaaS as github or similar, either create a new account for the task or make sure that your account is either filled with all your "perfect OSS projects" or at the least is cleaned up so that you don't show off code that would make other developers cry.
If you send a github repository link, the reviewer WILL look at your other repositories to see what else you do and how you do it, if they don't they are making a big mistake.
So when you work on your own private projects, it's quite important to pretend that someone else will read or use your code!
A) it is more important to write readable code then perfect code.
B) I really don't care about old reports. Why should I care about have the time to look through 2-year-old reports.
C) the fact that you are putting out code at all it's more important than the code quality.
D) even if I look at other reports I will try to see some kind of progress.
E) I lake the context of why this repo exists. So how can I judge it?
Maybe there are companies where this is important but it sounds more to me that this kind of companies wants solo rock stars then a band of good developers.
The "perfect" project thing was a joke. What I mean is, if you have a heap of really messy projects in your repository that you show off to someone who is considering to hire you, they will see them and they will judge you on it.
If a repository is old and not maintained, it's a lot less important in this sense, but if you have a project that you are actively working on in which every commit message looks like "fixxxxx", or "f**k it!" or similar, I wouldn't recommend showing it of.
I like to look at peoples repository history when I intend to work with them, that way you can get a quite good idea on how they work and where they are strong and weak in their knowledge.
I would like to point out that if you are going to use a repository SaaS as github or similar, either create a new account for the task or make sure that your account is either filled with all your "perfect OSS projects" or at the least is cleaned up so that you don't show off code that would make other developers cry.
If you send a github repository link, the reviewer WILL look at your other repositories to see what else you do and how you do it, if they don't they are making a big mistake.
So when you work on your own private projects, it's quite important to pretend that someone else will read or use your code!
Honestly an empty account is a much bigger red flag to me than an account with some messy side projects.
If those projects are personal it really doesn't matter what they look like IMO. At least you're doing something and exercising your muscles 😉
Messy account would make me less inclined to hire someone than a newly created empty account.
If someone writes terrible code when in solo projects, they will likely write messy code in my proprietary code too ;)
But I guess it might be a personal preference!
Here I can just speak for me:
A) it is more important to write readable code then perfect code.
B) I really don't care about old reports. Why should I care about have the time to look through 2-year-old reports.
C) the fact that you are putting out code at all it's more important than the code quality.
D) even if I look at other reports I will try to see some kind of progress.
E) I lake the context of why this repo exists. So how can I judge it?
Maybe there are companies where this is important but it sounds more to me that this kind of companies wants solo rock stars then a band of good developers.
The "perfect" project thing was a joke. What I mean is, if you have a heap of really messy projects in your repository that you show off to someone who is considering to hire you, they will see them and they will judge you on it.
If a repository is old and not maintained, it's a lot less important in this sense, but if you have a project that you are actively working on in which every commit message looks like "fixxxxx", or "f**k it!" or similar, I wouldn't recommend showing it of.
I like to look at peoples repository history when I intend to work with them, that way you can get a quite good idea on how they work and where they are strong and weak in their knowledge.
Okay I never write comments or commits with f@#k. In them but yeah point taken.