Hacker News new | ask | show | jobs
by rickyc091 3260 days ago
So I did a quick audit of your GitHub and minimal experience is definitely a correct assessment. But, don't worry! That doesn't mean you can't get a job. You'll just need to work harder or join a company that has the capacity to train you.

Legend Wings is nice, but the last several pages of commits are all just updating the README. I see that you committed your most code on the initial commit, however, I was also able to copy and paste and find exact code matches on StackOverflow. Forgot to mention, I use to be a teaching assistant so students would do this all the time.

Next up, you have a lot of boilerplate on your GitHub. You have a blank repo called VaporServer. Employers will check your most recent code as a basis of your skill. I'll ignore that one and look at the next one, WebJS (2 weeks ago). You were learning to use express and setting up a boilerplate.

The rest of your repos are tutorials or homework assignments. CalendarData is just a repo with a JSON file. Lots of forks aren't necessary good since the first thing I do is look for individual commits. Being that you come from a university I know there are a lot of group projects, I can't tell if you are the one working on the project or your peers.

This is all the information I gathered looking at half your repos more carefully. A recruiter will spend even less time than I did.

My suggestion would be to clean up any boilerplate repos or forks that don't really give much information or actually make things worse. CalendarData from April shows me that you probably don't know SQL. I can also tell you are starting to dive into node.js meaning you probably don't have backend knowledge. I noticed firebase implementation in your swift code so knowledge of APIs are good.

I would also try to find an internship as starters to get some experience and/or look for a job where they focus solely on the academia / whiteboard challenges. I'm not a big fan of those, but they have their place especially for college students without much experience. Just brush up on your data structures and algorithms and you should be good to go!

Good luck! Don't worry too much, it'll all work out in the end!

2 comments

Wow.. that indeed was a very very good advices. Thank you so much for your time to give a very detailed list in the areas that I must improve.

1) I did not understand about "most code on the initial commit". I have been updating the code basically every day. Is it because I have a dummy account? Like the accomplishment I wrote in the README, I recently put the dates I accomplish them.

2) About the repos, I think it has a lot because I recently cancelled the subscription. And I can't put them back to private. I will consider paying for the subscription and add back to private.

3) CalendarData is a repo where I can modify it with my app called: "MyAgenda" which is private since it contains a key to make HTTP requests via Basic Authorization.

I will definitely rework my GitHub page. :)

Ahh, sorry, an initial commit is the first commit you do on a repository. In this case, I noticed that most of the code logic was on this commit (https://github.com/woguan/Legend-Wings/commit/0df03c7657cc13...). It's actually better to have multiple commits to show your progress and thought process.

Well, the nice thing about git is that you can just remove the repo from GitHub and then push it back later. I would definitely recommend removing things like tutorials. I personally would rather see your school work than tutorials. Referring to (https://github.com/woguan/FlappySwift/commits/master)

For CalendarData, it might be better to add a README and add some context to it. Better yet, it's probably better to just hide it altogether since I interpreted the repo as you learning how to use JSON 6 months ago. If you need to store the JSON somewhere, one suggestion is to use gists https://gist.github.com/.

To publish private code that requires a private key, look into ENV variables.

These links might be able to help you if you don't know about ENVs already.

https://stackoverflow.com/questions/7501678/set-environment-... https://stackoverflow.com/questions/36219597/referring-to-en...

Very nice to give these advices.