induratized

Frontend Technical Interview Prep

EDIT: Well this has been linked now so just an FYI this is still TBD. Feel free to comment if you have suggestions for improvements. Also here is an unrolled Twitter thread of a lot of the tips I talk about on here.

I've been doing frontend for a while now and one thing that really gripes me is the interview. I think the breadth of knowledge of a "Frontend Engineer" has been so poorly defined that people really just expected you to know everything. Many companies have made this a hybrid role. The Web is massive and there are many MANY things to know. Some of these things are just facts that you learn and others are things you really have to understand.

Every time I interview, I go over the same stuff. I wanted to create a gist of the TL;DR things that would jog my memory and hopefully yours too.

Lots of these things are real things I've been asked that caught me off guard. It's nice to have something you ca

induratized

Good commit messages serve at least three important purposes:

• To speed up the reviewing process.
• To find out what changed in a range of commits (e.g. for a release note).
• To help the future maintainers, say five years into the future, to find out why a particular change was made to the code or why a specific feature was added.

Structure your commit message like this:

induratized

How to setup a literally free CDN

1. Create repo on GitHub where you'll put your files.
2. Use jsDeliver or statically to get your assets.

Here is repo I'm using:

https://github.com/jcubic/static

And links to files look like this: