4 ms·
When I have had to filter a pile of fresh collage graduate resumes to pick 2 candidates to call for a phone interview, I did not check for which specific progra
by dilippkumar 7y ago
When I have had to filter a pile of fresh collage graduate resumes to pick 2 candidates to call for a phone interview, I did not check for which specific programming language they knew. In my experience, most people pick up 80% or more of their programming skills at their first job.
What always caught my attention when giving through these projects was any project they had worked on. The actual project didn't matter so much. But almost always, how well they were able to understand what they worked on directly translated to their ability to present it in simple and concise few sentences.
Putting these pieces together - my advice is to go find something you want to build and build it. You'll figure out the best language, the libraries to use and all the good stuff on the context of figuring out how to build what you want to build.
The only real skills I strongly recommend you learn:
- git
- Makefile
- shell scripting
Bonus if you can run Linux on your primary computer. You'll learn a lot from just using a Linux box for daily use.
Go build something for fun. Write a text adventure game. Write a Sudoku solver. Write a reddit bot to count how many times someone said "wubalubadubdub" per day.
At some point, you'll have to transition from fun projects to projects that will look good on a resume. Keep that in mind and don't get lost in the woods and forget that you are on a mission.
Happy coding!
- yash8141 7y agoHi, are you hiring?Because I am looking for internship.I can send you my resume if you are.
- muzani 7y agoSo far all the jobs I took, it was not knowing the language and picking it up on the job. First job: PHP, Yii, Java, Android (I had a C/C++ EE background). Second job: cobbling together the whole back end. Third: JavaScript/Node. Fourth: Angular. Fifth: Cordova. I actually crammed C# for two weeks for another job, but didn't get that one. In most of these jobs, it took about 1-3 days to start writing useful code. I guess you could come in with 5 years of experience in something, but if they like you enough, you'll figure it out. Skill in a language or architecture also doesn't mean you have skill with the code itself. Like a language, the best way to learn is immersion.
- sumosudo 7y agohttps://git-scm.com/book/en/v2 https://git-scm.com/book/en/v2 https://tldp.org/LDP/abs/html/ https://tldp.org/LDP/abs/html/ https://www.gnu.org/software/make/manual/ https://www.gnu.org/software/make/manual/
- sheepybloke 7y agoI completely agree with this! In the end, languages are fairly straightforward to learn, but the skills learned in projects like architecture, design, and problem solving are what will actually land you the job. You can teach anyone to code, but you can’t teach everyone to be an engineer, which are the skills companies want and projects develop.
- slipwalker 7y agoalso recommend a strong understanding of SQL ( https://training-nyc.com/learn/sql/why-learn-sql https://training-nyc.com/learn/sql/why-learn-sql )