Structure your Projects as Experience
Give them a timeframe in which you did them, provide yourself a title eg. Full Stack Developer.
I greatly disagree. If those projects did not hold you accountable like a job does, you do not pretend they are such to inflate things. You'll have background checks wanting to know who your manger was at this "Github" thing or reference requests for how you manged time and requirements on what was a hobby project. Be true to what happened -- if it was a project, keep it listed as such in its own section. I'd only consider projects experience if it happened while at work with formal expectations for how it would get done.
Not suggesting he passes them off as working at Github. I have small windows of time to contribute comments on DEV.to so I would hope readers would give me the benefit the doubt.
For personal projects, timelines help you understand how fresh and how long work has been invested in a project
Providing a title can help understand the role in the project.
If the goal says he's switching careers and working on multiple open-source projects to showcase his self-learned experience there is no deception here and in-honest it's not hard to infer they are hobby projects. The github project links are a dead give away.
Initially misread it -- yeah, having things formatted consistently would absolutely help the readability of this (though I more noticed education seemed copy-pasted from an old resume). I thought the advice was to consolidate things into one section, which my corporate work has shown that would be a nightmare.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I greatly disagree. If those projects did not hold you accountable like a job does, you do not pretend they are such to inflate things. You'll have background checks wanting to know who your manger was at this "Github" thing or reference requests for how you manged time and requirements on what was a hobby project. Be true to what happened -- if it was a project, keep it listed as such in its own section. I'd only consider projects experience if it happened while at work with formal expectations for how it would get done.
Not suggesting he passes them off as working at Github. I have small windows of time to contribute comments on DEV.to so I would hope readers would give me the benefit the doubt.
For personal projects, timelines help you understand how fresh and how long work has been invested in a project
Providing a title can help understand the role in the project.
If the goal says he's switching careers and working on multiple open-source projects to showcase his self-learned experience there is no deception here and in-honest it's not hard to infer they are hobby projects. The github project links are a dead give away.
Initially misread it -- yeah, having things formatted consistently would absolutely help the readability of this (though I more noticed education seemed copy-pasted from an old resume). I thought the advice was to consolidate things into one section, which my corporate work has shown that would be a nightmare.