• Inspiration


ID Status Learning Item Type Related Project Date Completed
1 Complete How I got my first developer job at age 40 after 10 months of hard work Blog8/27/2020
2 Complete The tools and resources that landed me a front-end developer job Blog8/27/2020
3 Complete My journey to becoming a web developer from scratch without a CS degree Blog8/29/2020
4 Complete Learning How to Learn - Powerful mental tools to help you master tough subjects Course04/2020
5 Complete Problem Solving Blog9/16/2020
6 Complete Build a network of peers Blog9/20/20
7 Complete Meeting People Blog9/20/20
8 Complete How to Learn to Code Video9/18/20
9 Up next Getting Started Blog
10 In progress Your First Year In Code Book
11 In progress How to get a job as a web developer Blog
12 Not Started Learn to Type Blog
13 Not Started Ship in Six Course
14 Complete Just F---ing Ship Book9/30/20
Not Started The Truth about Success - Brick by Brick Blog
Not Started Teach Yourself Programming in Ten Years Blog
Complete If There Aren't Any Typos In This Essay, We Launched Too Late! Blog
Not Started Web Developer Job Preparedness Sessions Video
Complete Web Developer Job Preparedness Sessions Video12/01/20
Complete Building and Effective Dev Portfolio Book12/16/20
Complete Learn Regex Course02/03/22

You have to be willing to work hard, learn a lot, and be consistent. You need to persist when things get tough. Talk yourself out of the moments of desperation when you feel like you are not cut out for this. That’s all it takes, and everyone can do these things with a bit of practice.

The two biggest mistakes I found at first were:

  1. Fear of failure. Because I was the new guy, I was constantly in fear of my code being wrong or poorly made, so I spent a lot of time double-checking everything and adhered to coding best practices. Because of this, I rarely attempted solutions in creative new ways because of my fear that it might not work correctly at the end. This effectively shut down my drive to learn new things.
  2. Doing things because “X” person who knows better than me said so. I did this a lot at first. While not completely wrong, doing things in a certain way only because “X” expert on the matter said so — without knowing why — lead to me not really knowing when to why things were done the way they were. I soon learned that there were exceptions to everything, and that you always should know the reason behind best practices.

“Libraries and Frameworks may become obsolete, but the concepts and solutions they propose often survive the test of time.”

I’ve met a lot of developers over the past 2 years I’ve been a web developer. Along my journey, I’ve met a few developers who really stood out — developers who were clearly in a league of their own, and to whom me and everyone else looked up to. I found these individuals shared quite a few characteristics, which I’d like to share with you right now. These are in my opinion the secret sauce to being a successful web developer:

  • Love what you do. This is simply the most important characteristic of them all. If you don’t love what you do (be it CSS Styling or JavaScript), it will truly show in what you do. Those who are passionate about what they do often clearly stand out from the crowd.
  • Be generous and share your knowledge. It’s very easy to want to keep that new CSS/JavaScript hack you found that solves the project’s issues a secret, but please don’t. The people who share their knowledge the most are often the most valuable, since they can be placed in any kind of team and improve it’s quality by a huge margin.
  • Always be on the lookout for new things. Most of the successful developers I’ve met share this common trait. Whether it be by reading blogs, spending lots of time in programming related discussions, or even talking about what’s new in web development during lunch breaks. Being on the lookout for new things all the time allows the best developers to always stay ahead of the curve.

Guided resource to prep for technical interviews:

VS Code Tips

Keyboard Shortcuts

Open the command palette

  • Ctrl + Shift + p

Select whole word under cursor

  • Ctrl + d

With nothing selected, add whole line to the clipboard

  • Ctrl + c

Shift line contents vertically

  • Alt + up or down arrow keys

Copy line contents vertically

  • Alt + Shift + up or down arrow keys

Custom shortcuts can be created and support conditions!


Snippets are saved as either a local or global json file that can be modified. There are some really great examples in this video that demonstrate how to build efficient snippets.

To access, click on the settings cog in lower left, then select “user snippets.”

VS Code also comes with Emmet snippets enabled by default! This allows you to generate lots of structure quickly. For example:

div>ul>ui*4 and tab turns into


You can take this to extremes like div.content#intro>table>tr.headers>th*4^tr*7>td*4, which creates a div with an 8x4 table, and adds some classes and IDs to elements.


If you use the command palette to turn on setting sync, you can export all (or some) of your settings with your GitHub account.


The video also contains a great overview of using debugging. Debugging looks incredibly powerful, and I feel a little foolish for not looking into it sooner! I will definitely be trying this out soon.

Version Control

From the git tab, you can perform all of your basic git actions. With GitHub integration, you can actually publish new repositories right from inside VS Code!