Hacker News new | comments | show | ask | jobs | submit | xissy's comments login

What a great idea & execution.

As a programmer, I manage my resume on my github pages where can bring many benefits. - eg. make a new branch for a new company, easily add/remove related projects, install google analytics for checking who is interested in me, and so on.

Recently I've needed to submit my resume to several companies. What I surprised is that they, HR people, wanted only pdf/doc formatted resume even they work for software companies. What a silly.

VisualCV can be a proper solution between a old-fashined pdf resume file and too much opened LinkedIn page.


I'm curious - why branch for new companies? Your resume represents the linear flow of time, it's not like we get to try out alternate versions of ourselves :)


I'm from South Korea.

To apply for a Korean company, they usually require a formal photo, SSN, parents' jobs, house income, written self introduction, etc. No kidding. And I have a few years military service experiences as a Korean army that might be not related with software engineering.

So for those reasons, I had to split branches to appeal myself to diverse companies properly. I don't want to make companies confused with unnecessary info.


Hey, could you recommend any books or tutorials for C++1y/C++14? I had learned C++ in my CS courses but I've used java/python/javascript these days. I'm thinking of coming back to C++ because C++14 looks cool.


Start with Bjarne's new book, "Tour of C++", it shows how to make proper use of C++11 without those C unsafe influences.

C++14 is mostly fixing what was left out in C++11, so the book is already a good starting point.

C++14 is definitely cool, I use JVM/.NET nowadays at work, but am an old C++ dog (since 1993), so I always used the language on a few side projects.

C++14 kills quite a few complaints I had about the language. Now if we just could get proper modules.


Sometimes I've thought what might be the next GitHub. The answer is Docker. Can't imagine to develop, test and deploy without Docker totally.


Yes, but sometimes like difficult papers and articles.


Cool, I totally agree with this post. Traditional developing culture has many problems for developers who make values. Remain super developers' flow - I think this could be one of answers.


Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact