These questions keep popping into your head. It gets even scarier by the minute, doesn’t it?
It seems impossible to get a job as a web developer. Each job ad you see says need to know React, Vue, Angular, Node, Gulp, Webpack, Sass and plethora of skills you may have heard about, but don’t understand at all!
Is it possible to get hired without knowing all of them? Can you learn on the job? Will you get rejected for not having enough experience? And how much experience do you really need? 2 years? 5 years? Or more?
Can you even get a job without spending three years coding things yourself? Can you win boot camp graduates without going to school yourself? Why is it so hard to get a job as a web developer?
In this article, you’ll find my thoughts about getting a job as a web developer. You’ll also hear how I found my first job as a developer.
Many people feel that
this is incredibly confusing. Because it’s so confusing, they argue that
But no more. Let today be the day where you learn to think like a programmer.
Have you had instances where you wanted learn something, but it completely eludes you?
In each of these cases, no matter how hard I tried, I can’t seem to make the knowledge click on a deeper level. I read books, articles, and tutorials, but the knowledge I gained simply vanishes into thin air the very next moment.
Should I give up? I would ask myself occasionally. Am I just stupid?
For a long time, I wondered why this pattern kept going on. I finally understand now.
Are you confused by the
But that doesn’t mean you can go on without understanding
this is sooner or later. Once you understand
this, you’ll realize that it’s much simpler than you think it is.
By the end of this article, you would have demystified
this for yourself. You’ll know what it is, what it does and how to use it.
That’s what today’s article is for! You’ll learn what callbacks are, why they’re important and how to use them. 😄
You cannot remember what methods are available. You need to search google even for something as simple as
You’d love today’s article if you had these problems. I’ll show you how to tackle them all in one swoop by setting up your development environment.
Changing the DOM used to be difficult. We needed jQuery to make things easier. Luckily, there’s no need for jQuery anymore.
In this article, I’ll show you the things you need to be familiar with as a frontend developer.
If you read my past articles on CSS architecture, you would have noticed I took parts of techniques created by experts and mixed them into a set of rules that I follow. Some of my rules helped others understand how to use a technique, while others sparked public outrage (like my unconventional BEM usage. People exclaimed that I broke BEM rules).
I’d like to confess today that I broke more rules than that. Breaking rules is my way of finding out what to take in from techniques mentioned by experts. It’s also my way of figuring what to change to adapt to my personal belief. Today, I’d like to dig into this rule-breaking process.
We’ve already talked about writing Modular CSS with BEM and namespaces in the past two articles. In this article, I want to veer away from the process of writing CSS selectors into the mystical art of file structure and organization.
If you’ve ever wondered what’s the best practice for organizing files, how to find any CSS file easily and how big or small each file should be, this article is written for you.
Last week, I shared how I use BEM to create a sensible CSS architecture. Although BEM is awesome, it’s only part of the solution. There’s another part I’ve yet to mention — namespaces.
In this article today, I want to share with you why BEM isn’t enough and how I use namespaces to bridge the gap.
Have you worked on large websites that spans more than a few pages? If you did, you probably realized the horrors of not conforming to a robust CSS architecture. You probably would also have researched on ways to write maintainable CSS.
Since our industry is awesome, we don’t only have one recommended solution. Experts have jumped in and provided us with suggestions like BEM, OOCSS, SMACSS, Atomic Design and many others.
Now, instead of suffering from “I don’t know what to do”, the question becomes: “there’s so many ways. Which should I try?” Should I use everything, only one approach or create a custom architecture from the possible picks out there?.
I started off with only one approach. Then, as I tried different approaches, I began to include what I thought made sense into my process. In this article, I want to share with you how I structure my CSS and why I do so. Hopefully, it’ll help you find your preferred method.
Oh look! Everyone is talking about Webpack now! Should I upgrade my workflow to use Webpack?!
“Hmmmmm… Maaaybe I should use PostCSS since expert X highly recommends it. I can’t decide…”
“OH WOW. FACEBOOK USES REACT! REACT MUST BE HAWT! I NEED TO LEARN THAT TOO!”
Are you familiar with any of these conversations? It’s not surprising if you are! New tools pop up in the frontend world incredibly quickly. Whenever something new pops up, people scream about how cool it is. Even industry experts begin using them. Heck, the expert you love and follow may even recommend you to use them!
Do you feel pressured to try the new tool out? Do you feel like a shitty developer if you don’t keep up with the latest tools?
If you do, you’re not alone!
Today, I want to share with you a simple framework to determine if you should learn/switch to [insert shiny tool]. Read on if it sounds any interesting.
The act of choosing two typefaces is probably the first (and often most difficult) task you do when creating a new design. Many people get stuck here, myself included.
Recently, I discovered a simple method to pair typefaces effectively and I’d love to share them with you. (Hint: it’s a 3×3 grid).
It’s common for designers and web developers to suffer from decision paralysis. You know you’ve battled with it if you had problems like:
- Spending hours choosing the right typefaces
- Obsessing over choosing the right framework
- Scratching your head over what to learn next
- Facing writer’s block
Does any of them sound familiar?
Decision paralysis has been the bane of my life so far. I battled against it again recently and I’m happy to say I finally got out of the rut (today!).
In this article, I’d love to share my experiences with you and how I handle decision paralysis.
Reading is a skill I wanted to improve for ages. I wanted to read faster, because reading faster means I’ll learn faster. So, I tried to learn how to speed read many times in the past.
Speed reading wasn’t too difficult. The sad thing is, I can’t seem to remember anything I read, which makes the speed useless.
In 2017, since my theme for the year is experimentation, I wanted to see if I could improve my reading capabilities. This time, I found some success: I read 1.5 books and remembered most of what I read in three weeks.
I’m so elated by the discovery of this technique and I’m happy to share it with you!
2016 was a strange year. It was full of up and downs. On one hand, I had eye-opening experiences that taught me a lot about myself. On the other hand, I was horrified at the amount of time I wasted accomplishing nothing, so much that I ended the year loathing myself to the core.
But that’s enough. The new year is here. It’s time for me to recollect my experiences and regrets and move on. This article is a summary of my learnings in 2016 and my plans for 2017.