What do developers showcase in their portfolio? How do you describe the projects you've worked on? What is a recruiter looking for when visiting your website?
A developers profile these days is mostly just github. Works very well for those of us that contribute back to open source but not too sure how someone who doesn't contribute to os stuff would show a portfolio...
Sorry to point this out, but you sound more like a recruiter than a designer. I'm sure people would answer your questions if you would ask them a little bit less bluntly.
My answers to your questions are:
1. I showcase the projects I've been working on
2. I don't describe the projects, just point a link to them, they should describe themselves (README, code comments, etc.)
3. Someone very skilled to make them good money with little hassle
I don't describe the projects, just point a link to them, they should describe themselves...
Can't disagree more.
If I'm hiring a freelance developer, I want to be assured of their "here's my problem, help me come up with a solution" abilities. Simply linking to an app they build for a client or a Github project doesn't necessarily tell me everything I want to know. Why does this exist, and what problem was it trying to solve? And did it end up solving said problem, if so — how?
Comments
I'm not a developer but a designer.
What do developers showcase in their portfolio? How do you describe the projects you've worked on? What is a recruiter looking for when visiting your website?
I went with case studies for sites & software projects, but those aren't always easy to come up with.
It definitely tends to be less of a visual portfolio than a designer's.
A developers profile these days is mostly just github. Works very well for those of us that contribute back to open source but not too sure how someone who doesn't contribute to os stuff would show a portfolio...
>not too sure how someone who doesn't contribute to os stuff would show a portfolio
A portfolio can also consist of project writeups/screenshots and/or links to live sites.
Sorry to point this out, but you sound more like a recruiter than a designer. I'm sure people would answer your questions if you would ask them a little bit less bluntly.
My answers to your questions are: 1. I showcase the projects I've been working on 2. I don't describe the projects, just point a link to them, they should describe themselves (README, code comments, etc.) 3. Someone very skilled to make them good money with little hassle
I don't describe the projects, just point a link to them, they should describe themselves...
Can't disagree more.
If I'm hiring a freelance developer, I want to be assured of their "here's my problem, help me come up with a solution" abilities. Simply linking to an app they build for a client or a Github project doesn't necessarily tell me everything I want to know. Why does this exist, and what problem was it trying to solve? And did it end up solving said problem, if so — how?
If the readme (or the front facinf page of the project) doesn't answer those questions I wouldn't be interested in it, and even less in its developer.