Front-End Postwork

After you leave Turing you will undoubtedly have a bookmarks tab full of all the technology you should be learning, all the blog posts you should read, all the videos you should watch, etc etc etc.

If you’re feeling overwhelmed, this postwork document is meant to be a small list of resources and advice to keep your skills sharp in the next 3 to 6 months.

While you’re in the interview process, have an answer to the question what have you done since you graduated?.

During your first six months of the job, have an answer to the question why do you deserve a raise?.

Pick a chunk of time every day that you’ll dedicate to working through these resources. Define success for yourself by having a hard stop.

For example, if you’re on vacation, commit to doing two hours of code with your morning coffee. At the two hour mark, close your computer and allow yourself to enjoy the rest of the day. You might end up opening your computer right back up - but always know when you have ‘successfully hit your goal’.

Interview Practice

Code Resources

The 2017 Front-End Handbook by Frontend Masters

This is a guide that anyone could use to learn about the practice of front-end development. It broadly outlines and discusses the practice of front-end engineering: how to learn it and what tools are used when practicing it in 2016.

Download in .pdf, .epub or .mobi here

If you don’t want to download a pdf, check out the easier to browse 2016 version here

Review this book when you’re feeling imposter syndrome coming on. Think about how many of the topics listed here you already know!

Dig in to some of the resources and review.

30 Day Vanilla JS Coding Challenge

Build 30 things in 30 days with 30 tutorials. No frameworks. No compilers. No libraries. No boilerplace.

Make sure your fundamentals don’t atrophy.

Do these challenges. Post your results in your cohort channel.

Specific Topic Resources

Below is a list of pretty wonderful free resources on some specific topics that you could check out if you’re interested. If you only read a few docs over the next few weeks - read through these!

To dive deeper, checkout the lists of resources in the frontend masters handbook!

Community and Professional Skills Resources

Blog

Increase your value as a developer by writing blog posts. Avoid oversharing personal details, use good titles, use refactored code examples and format the post well. Imagine what blog post you had wish you had found when you were googling a problem.

Use a site like medium.com for hosting so that you have a higher chance of the post being found.

Review this lesson for more ideas/best practices.

Record Videos & Give Talks

If you want to give a conference talk someday, prove that you can do it with a screencast or a tutorial video. Make the videos small and be prepared to record them multiple times.

Upload slides on speakerdeck so that you can share them easily.

Join the #thought-leadership channel in slack and get advice, lists of upcoming conferences, etc.

Lanyard.com has a pretty comprehensive list of calls for speakers.

Leverage the Turing Community

Reach out early and often with Meg, Lia and the rest of the professional skills team.

Reach out to your instructors for advice.

Most importantly, use your cohort-mates and don’t let your groups slack channel go silent.

Contributing

This postwork is part of the front-end-curriculum repo at the Turing School of Software and Design. Feel free to send Pull Requests or raise issues in our repository.