Photo by Sigmund on Unsplash

If you were in the frontend space for more than 2 years or working in a startup company, there’s a big chance that you need to write reusable components. It might just be for a small team or even preparing for the next batch of engineers to come. Either way, you will need to know these basic understandings to avoid rewriting the reusable components since you’re not doing it correctly.

Before we dive right into it, here’s the most important reason to use Reusable Components? DRY your code; that’s pretty much it. You can write 10 of the same colored…


From Unsplash.com by https://unsplash.com/@rainbennett

Before we start, let me write some disclaimers before anyone going to a conclusion without any context.

  1. I have been in the frontend space since 2010. I still remember being taught to do psd slicing to make a website. Spent years of building websites with plain HTML, CSS3, and jQuery (yes I know, I’m just joking). Then I learnt the React way and it changed my life.
  2. Started working on the Frontend space since 2015 with internship which then followed up full time job in the Bay Area.
  3. These are the common mistakes are based on what I see from…

Photo by Moritz Mentges on Unsplash

Here’s another common mistake that people made when you need to overwrite styling from an external library. It’s easy to do, but hard to get it right. In this case I will be using the 2nd most popular React Component library by the time this post is written.


Photo by Greg Rakozy on Unsplash

CSS Pet Peeve

I realized this topic is very subjective, but looking back 6 years that I’ve dealt with CSS I think I have some right to say about this topic. Before you start raging in the comment section on why it’s okay to use percentage, there are some special cases though where it’s acceptable to use percentage .

The reason I want to talk about this: I’ve reviewed a lot of Pull Requests lately and I was reminded that a lot of engineers using percentage where it’s not supposed to. …


Photo by Austin Distel on Unsplash

Make it WET, don’t DRY!

As you all know DRY stands for Don’t Repeat Yourself, and that is common for engineers to say all day long. But communication is different; people tend to forget when a communication only happened once. So we need to make sure that we have a follow to make sure that people don’t forget. Or make your communication WET; Write Everything Twice. Now let’s get down into the nitty-gritty why I wrote this.

As I progressed in my software development career, I learnt that coding is not the only thing that matters. I naively believed that when I first made a…


Photo by Pankaj Patel on Unsplash

I had this topic in mind since about a year ago when my company decided to move forward with functional programming, more specifically using Redux-Observable, RxJs, and Ramda.

I had a hard time understanding how functional programming works since I was taught with the imperative programming since Junior High. I wasn’t trying to be against it, but my brain would not follow the thought process of functional programming as if it were imperative programming. And not just about the functional programming, but now I also have to understand how the Redux-Observable works. …

Bernardus Billy Tjiptoning

UC Berkeley Alumni 2015. Frontend Software Engineer in the Software Security Company — working remotely from Indonesia due to H1B!

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store