Have you been painstakingly cranking out unit tests for the past few months, trying to hit and maintain the coveted > 90% code coverage, only to now find yourself rewriting them again and again because of minor changes to your codebase? Have your users bumped into subtle bugs that your…

Helping our team (and ourselves) write more meaningful and robust code — 🎯 The Challenge Here’s something we’ve probably all seen— component methods named after the events they’re handling: In addition to React, I’ve also seen this pattern in Angular, Backbone, jQuery…it has probably existed for as long as the first programming language that had event handlers. Here’s an example with event listeners in…

By building our own reusable component from first principles — Learning often comes from deliberate practice and repetition—making the same mistakes, writing the same code, solving the same problems over and over again. For example, how many times have you had to: Render a form with some inputs Collect data from these inputs as the user enters values Process the…

Our unit tests were suffering because of excessive abstraction — Our team had been working on a mid-sized Angular application for the past few months. Unfortunately, we hadn’t started with testing in mind at first. …

Whether we succeed or fail, it helps to know how to best represent our team in front of upper management or clients. — Speaking from personal experience, it’s too easy to fall into the trap of putting our colleagues on a pedestal when they succeed, think less of them when they fail, or otherwise unwittingly participate in creating and sustaining what I like to call “office politics”. I actively try to counteract this…

This series of articles explores my experiments in using decorators to make writing and maintaining React components more ergonomic (subjectively). While I’m sure many prefer to stick to more traditional ways of writing components, I often try to bring some features that make sense from one framework to the other…

This is the second in a series of posts on coding designs from Dribbble. If you haven’t seen the previous one yet, here’s part 1 — Venue Landing Page. — It’s close to midnight on a Saturday and I’m halfway through implementing another Dribbble shot for this series. After getting increasingly bored with it for the past few hours, I start browsing around for more inspiration. Ending up back on Dribbble again, I find myself staring at this design when…

This is the first in a series of posts on coding designs from Dribbble. The next post is already out —check out part 2 — Editorial Exploration. — Being a web developer, I will admit to occasionally having that anxious feeling when receiving a new design mockup, thinking something like: “This will take too long to implement with the technology we have today and all the old browsers we have to support”

And how to be more careful about it in the future — Today, I received a very convincing phishing attack on my personal email address. For those not familiar with the term, here’s a definition from Wikipedia: Phishing is the attempt to obtain sensitive information such as usernames, passwords, and credit card details (and money), often for malicious reasons, by disguising as…