Focus is important. It tells us what element we’re currently focusing on. Most developers suggest keeping the default focus style.
I think there are problems with the default style. I tried searching for inspiration to design a better focus style, but I couldn’t find anything on this topic. So I did some quick research by visiting sites I use and paying attention to their focus styles.
I want to document my research and findings in this article. I hope it helps you:
- Understand the problems with the default focus style
- Give you some inspiration to design your own focus styles
Have you noticed you write a lot of asynchronous code in Express request handlers? This is normal because you need to communicate with the database, the file system, and other APIs.
When you have so much asynchronous code, it helps to use Async/await. It makes your code easier to understand.
Today, I want to share how to use async/await in an Express request handler.
It’s easier to work with Promises (or Async/await) compared to callbacks. This is especially true when you work in Node-based environments. Unfortunately, most Node APIs are written with callbacks.
Today I want to show you how to convert callbacks to promises.
As I created applications with Express and Node, I learned about three useful middlewares:
- Remove empty properties
Of these three, Morgan is an actual middleware. You can download Morgan from npm directly. The other two are middlewares I created with camelcase-keys and omit-empty respectively.
I want to share what these three middlewares do, and how they make life easier for me when I’m creating applications.
I noticed browsers were inconsistent in how they handle a click on
<button>. Some browsers choose to focus on the button. Some browsers don’t.
In this article, I want to show you my test and findings. Then, I want to talk about a way to overcome these inconsistencies.
Fears and doubt often pop into my head when I work.
When I code, I wonder:
- Am I using best practices?
- Did I structure code in the best possible way?
- Am I doing it correctly?
When I write, I wonder:
- What makes me qualified to teach anything?
- Will people understand what I’m trying to say?
- THIS THING IS TOTALLY OFF-TOPIC. IT’S NOT TECH RELATED! OH MY GOD!
When I run my business, I wonder:
- Should I reply to every single email?
- Should I continue to focus on articles?
- Can I see pre-orders for courses?
- What if I can’t complete my courses on time?
- Are my products and sales emails persuasive but not coming off too sales-y?
I hate having these thoughts because they make me hesitate. And I slow down in my work.
But I love these thoughts because they tell me I’m doing the right thing.
When you write tests for the backend, you need to test for four different kinds of operations:
- Create (for adding things to the database)
- Read (for getting things from the database)
- Update (for changing the database)
- Delete (for deleting things from the database)
The easiest type to test for is create operations. You put something into the database and test whether it’s there.
For the other three types of operations, you need to put something into the database before you write the test.
The hard part about testing a backend application is setting up a test database. It can be complicated.
Today, I want to share how I setup Jest and Mongoose.
I played around with testing lately. One thing I tried to do was to test the endpoints of my Express application.
Setting up the test was the hard part. People who write about tests don’t actually teach you how they set it up. I could not find any useful information about this, and I had to try and figure it out.
So today, I want to share the setup I created for myself. Hopefully, this can help you when you create your own tests.
I always use MongoDB as a database when I work on an app. And I like to connect to a database on my computer because it speeds up dev and test-related work.
Today, I want to share how to create and connect to a local MongoDB Database.