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

You should decide what type of front-end position you're interested to get into; the front-end is now so broad that it's tough to know everything.

First, prove you are proficient with the following:

http://learn.shayhowe.com/html-css/

http://learn.shayhowe.com/advanced-html-css/

Here's a contest today that can test your skills

https://a-k-apart.com

Learn javascript and show you know ES5 inside and out. If you already know ES6/ES2015, awesome, show that too.

Any project where you've written the code from scratch (not using Bootstrap), where you teach others what you did, will show you're on the right track.

Want to contribute to Github? Look for a language, project, framework, library you're interested in, fork the project and improve the code. Doing this regularly, every day if you can, will show you're eager to learn and contribute.

If you're already at this level, pick up a specialty. It could be templating within WordPress, .NET or Java, or it could be MVC based coding using React+Redux, Angular, or Ember. Pick your favorite from these, get super proficient and even blog about your progress.

Finally, once you've gotten this stuff done, you will set yourself apart by learning cutting edge tech like Service Workers, Offline first, progressive web apps and just about anything the Google Chrome Developers are talking about here: https://www.youtube.com/channel/UCnUYZLuoy1rq1aVMwx4aTzw

My favorite is Totally Tooling Tips (all three seasons are gold).




Btw OP if you succeed at this guy's post, you are already a senior engineer in a lot of places, and middle-level in the rest of the more difficult places.

People with less skills than this earn 3x as much as a junior would make.


Thanks for all the suggestions! Really helpful.

For Github: How could a newbie ever improve the code of someone who's experienced enough to create a library or framework?


When you fork a Github project, you'll have to examine the code to see what it's doing and how.

With HTML and CSS, it's mostly visual but you can find improvements on semantics or simplifying what's there. If you can improve performance by rewriting a javascript function into CSS, such as animations, submit a pull request with your suggestions.

With Javascript, look for bugs and improve the code that's written. Javascript easily becomes a mess and is often referred to as spaghetti code when it becomes hard to manage.

Overall, look for ways to simplify the code, even if it means more code overall although usually it means less code. Two examples:

https://philipwalton.com/articles/untangling-deeply-nested-p...

http://www.heydonworks.com/article/on-writing-less-damn-code




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

Search: