Hacker News new | past | comments | ask | show | jobs | submit login

> When people are referring to using Github as your CV, they aren't talking about Github pages.

That's actually my point. They should be, and maybe you didn't read the comment I was replying to, but that is in fact exactly what we were talking about - "Unless you have your CV on github.."

Of course having a mess of github project pages is a bad portfolio, but each of the individual projects in your portfolio makes sense as a github project, and the fact that they give you a pleasant <username>.github.io site to tie it all together makes it one of the best ways to host your portfolio.

It makes perfect sense to have github projects as your portfolio parts and turn it into the 'narrative' so beloved of the original author with a github pages site.




> That's actually my point.

So then you are still missing the point. And so was the original comment you replied to. When people are talking about github as your CV, they don't care that you happened to host your website on ghpages. It's using the code repos themselves. Where you host your website is beside the point.

> It makes perfect sense to have github projects as your portfolio parts and turn it into the 'narrative' so beloved of the original author with a github pages site.

Yes. But again, that's not what's being discussed. You are in fact agreeing with the foundation of the idea.

Basically: GH Pages are merely a way to host your own personal website. The fact that it's also on GH isn't special in anyway, and you could achieve the same thing self-hosting. Remove that from the equation, and merely having GH repos is the issue.

People are saying you need that 'narrative.' How you achieve that is up to you, but relying just on the default GH repos doesn't help.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: