Github does a poor job of presenting your work to viewers, so why do developers insist on including it in their resumes. I believe its because developers take pride in their craft and to be introduced by their work.
Yet developers' best work is hidden inside private repos: the side project that might have commercial potential, that company work that can't be open source, clients and consultancy work that's covered under NDA. If you are hiring developers based on their github profile, you are optimizing for the wrong profile.
That's why I made https://gitfolio.dev - mostly to scratch my own itch: present my best work better than github does, provide evidence for what I am good at, and keep updating it on an autopilot.
If you are a developer, you can give it a try for your own portfolio at https://gitfolio.dev - you can use it even without giving it access to your code.
Github does a poor job of presenting your work to viewers, so why do developers insist on including it in their resumes. I believe its because developers take pride in their craft and to be introduced by their work.
Yet developers' best work is hidden inside private repos: the side project that might have commercial potential, that company work that can't be open source, clients and consultancy work that's covered under NDA. If you are hiring developers based on their github profile, you are optimizing for the wrong profile.
That's why I made https://gitfolio.dev - mostly to scratch my own itch: present my best work better than github does, provide evidence for what I am good at, and keep updating it on an autopilot.
If you are a developer, you can give it a try for your own portfolio at https://gitfolio.dev - you can use it even without giving it access to your code.