Build Your Developer Brand post-mortem
I did a post-mortem for Build Your Developer Brand (which I gave last Friday). I wanted to share this review openly in case anyone is interested in my thoughts.
I did a post-mortem for Build Your Developer Brand (which I gave last Friday). I wanted to share this review openly in case anyone is interested in my thoughts.
Here’s a funny piece of data from the survey I sent out last week:
I finally understood how to work with Node, Express, and MongoDB. I want to write a comprehensive tutorial so you won’t have to go through the same headache I went through.
After a horrible experience with my 2018 Macbook, I decided it was time to buy a Windows device as my backup machine. I chose to use Windows as a backup because:
I ended up buying a Surface Laptop 3.
Setting up Windows was harder than I imagined. It was especially hard because I wanted this Windows machine to mirror everything I do on Mac.
In this series of articles, I’ll explain everything I did to configure my new Windows machine. This should help you out if you’re switching from Mac to Windows.
When I need to check a person’s details on Convertkit, I need to log in to Convertkit and search for the person’s email address. This process takes time, energy, and clicks.
I’m not in the state to check a website when I’m doing work. I want to find the person’s information quickly and get stuff done.
So I created a command line interface for Convertkit.
We’re back to the end of the month. Here’s more resources for you. This time, I want to send you some design courses.
When you build JavaScript components, you need to manage focus for both keyboard users and screen readers. The WAI-ARIA specs say there are two ways to manage focus:
element.focus
and tabindex
aria-activedescendant
Which should you use and why?
I did in-depth research on these two methods and I’d like to share my findings in this article. Take a seat and grab some popcorn because it’s going to be a long article.
Accessibility is a big part of JavaScript. If you build anything with JavaScript, you need to make them accessible.
I’ve been afraid of touching accessibility for a few years now. This fear magnified when I began writing the accessibility lessons for Learn JavaScript.
Today, I want to share with you why I became afraid of accessibility, and how I overcame this fear.
This is the third article in the Learn JavaScript design series. Today, I’ll talk about how I built the Account and Component Page.
I deleted many resources I found useful because I restricted myself to sharing only blog posts here.
I want to change things up by sharing things I found helpful. I’ll send them once a month. Let me know if you enjoy this new format, or if you have any feedback!
Without further ado, let’s jump in.