Are you sick of procrastinating?
I am. I have procrastinated a lot in my life, and I don’t want to procrastinate a moment further. But, somehow, procrastination always seem to creep up on me when I least expect it.
Recently, I got stuck with a serious bout of procrastination that paralyzed me for two full days. I couldn’t get any work done. I felt incredibly stressed. This incident reminded me about how awful it was to feel useless and powerless.
Having gotten past this serious bout of procrastination, I want to take this opportunity to tell you what goes through my mind when I procrastinate. I want this to serve as a reminder to myself, and also to hopefully jolt you into action.
I think it was a few months ago where someone asked me if I had any pointers to help them transit from Bootstrap’s dom-littering
.col classes to either Susy or Neat. It struck me that I haven’t talked about this even though I’ve been using Susy grids for so long!
Anyway, this transition is a fairly big undertaking if you’re doing it for the first time. Allow me to walk you through a four-step process that I use in this article.
I recently came across an article titled “Web typography is broken. Here’s how we can fix it”. A mix of emotions rushed through me while I read through it. I realized that the biggest argument Tom was making in the article was that web typography is broken because type doesn’t sit perfectly on a baseline grid.
On one hand, I was happy to see people coming up with ideas to push code to their limits.
On the other hand, I’m unsettled. I asked myself: “Is there a need to make every line of text sit on the baseline”? I knew the importance of Vertical Rhythm and the baseline grid. I also knew that details matter when it comes to design. But is this one detail enough to break web typography?
As I browsed through the internet looking for answers, I found out that even great designers like Mark Boulton remarked that it would be cool if CSS gave us a pain free baseline grid.
This increased my urge to find out if web typography was completely broken. After all, if a great designer said the same thing, then sticking perfectly to the baseline grid should be important. Right?
Have you wondered if you should use
rem for media queries? I had the same question too, and I never figured it out, not till now.
When I first created the mappy-breakpoint library over a year ago, I used
rem units. Then after a conversation with Sam Richard, I quickly switched to
em instead because I found out there isn’t a difference between the two.
In addition to
rem, a popular unit of choice for media queries is the good old pixel. I wondered if it’s possible to use pixel queries nowadays since px-zooming problem that used to exist was now resolved by all browsers.
This week, I finally decided to get to the bottom of this matter.
I talked about using rem and em for responsive typography and for building modular components in two blog posts previously. In both posts, comments about viewport based units inevitably comes into the picture.
I resisted working with viewport units for a while, believing that using them would be a pain in the ass because of the calculations involved.
Last week, I finally overcame the resistance and took a stab at exploring viewport units and how to use them in responsive typography.
You probably heard of the term Vertical Rhythm if you researched a little about typography on the web. It’s one of the most important practices when working with typography. I’ve used Vertical Rhythm on all my sites ever since I read about it.
One day, it struck me that I haven’t had a clue why vertical rhythm was important. Two more questions quickly arose following that thought: “How does Vertical Rhythm improve the design of the site? What lessons can I draw from Vertical Rhythm so I can improve my design?”
I decided to find out why. Here are my thoughts.
One of the best practices to typography on the web is to use relative units like
The question is, which should you use? There’s been a longstanding debate between
rem supporters and
em supporters, believing that you should use one over the other.
In this article, you’re going to find my take on
em. You’re also going to learn exactly what
em are, and how to use them to build modular components.
The rating element is one UI pattern that you’ll find everywhere on the web. I found myself building another rating element for the second time in my life a few weeks ago.
This article is the second part on creating a CRUD application with Express and MongoDB. We’re going to venture deep into the last two operations that were not covered in the first part – UPDATE and DELETE.
Without further ado, let’s start the second part.
If you know me, you know that I started learning about the web without having gone through any computing courses in university previously. I didn’t dare to venture into server-side programming for a long time because of my background.
I remember when I eventually picked up the courage to try, I had such a hard time understanding the documentations for Express, MongDB and Node that I gave up.
One year later, I finally understood how to work with these tools. Then, I decided to write a comprehensive tutorial so you won’t have to go through the same headache I went through.