MobX has slowly built itself up as Redux’s main competition for state management real-estate. Which is definitely not a coincidence. Because, not only is MobX incredibly easy to use; it’s also very powerful. And, believe me when I say this: I’ve never seen React perform any better than when I mix the two of them. But, instead of me telling you, why don’t I show you instead?
A little bit of History: I’ve been working with Redux since version 1.0.0 came out. I was one of the early adopters at my previous company, gave courses on it, and tried to evangelize everyone to my cause. Pretty standard stuff.
Which means that, by the time I found out about MobX, I was already pretty familiar with the competition. Making me change sides was going to be no easy task.
And that’s when I ran into this video by Matt Ruby:
But, since it’s 42 minutes long, I’ll summarize it for you: Mixing MobX and React is like giving your car a consistent Nitro Boost while also reducing its fuel consumption by 90%.
What do I mean by this? The combination literally reduces the number of updates and (by extension) rendering to the bare minimum. Which brings your application to the peak of its performance.
If that doesn’t convince you to give this combo meal a try, nothing will. But, if being super fast is something that interests you, then boy do I have a treat for you next.
Should developers know design? Or should designers know development? This is an argument that’s been around for several years, although it was mostly aimed at the design crowd. But that could all change with the recent advancements in front end development. Developers could benefit now, more than ever, from understanding design and its principles. Ever since the good ol’ days of yore there have been tales of a magical being. This powerful hero was said to wield the powers of both a developer and a designer. With this might, she was able to walk amongst members of either guild as one of their own. And, should she deem them worthy, legends told she even had the power to unite them under her flag. I am speaking, of course, of the unicorn designer/developer. This particular role is still very much sought after. You will often find job listings including both “X years of design…
To do that I have prepared a list of my 5 favorite features about it. But, don’t get me wrong. I don’t mean these are the best ES6 features; that’s definitely up there for debate.
What do I mean then? Just that these are the 5 features that keep me installing Babel on all my projects. And I’m not even kidding. They just make my life that much more awesome.
So without further ado (and in no particular order) here are the 5 reasons why ES6 ROCKS, yo:
Author’s Note: This post is a sequel to last week’s Lessons from Remote Work Job Interviews around the world. – Pt 1. If you haven’t read that one, I highly suggest starting there.
Last week we talked about the first three lesson’s I got from my 4 month remote work interviewing process. We mainly learned that:
- There will always be someone better, but that doesn’t have to stop us.
- Saying “I don’t know” can be surprisingly powerful.
- Reinforcing your fundamentals can lead you to discover new strengths.
Now, this week, we’re going to be discussing the final three lessons I got from this journey, starting now:
I’ve spent the past 4 months of my life with a single focus: Getting a Remote Job. This was a process that led me into a journey of self-discovery, learning and personal growth. Here are some of the lessons I learned from Remote Work Job Interviews around the World.
Now, don’t get me wrong, I didn’t just spend 4 months throwing resumes out there and hoping for the best. That wouldn’t have been enough. These were three of the most hard-working months of my entire life: I’m talking 16 hour days of work and study.
And while I know that it may sound excessive for some people, to me it only made sense. I knew I wanted to change Jobs, and I knew I wasn’t about to settle down for more of the same. I didn’t want another 9 to 5, different office, similar commute.
No, my friends. To me, getting a remote job meant obtaining freedom. Freedom to be wherever I wanted to be, and to visit my friends and family more often.
But, as some of you may already know, remote work isn’t an easy perk to come by. And it’s not that hard to understand why: you’re competing against the whole world for a job like this. This also meant that remote work job interviews were going to be a little more competitive than usual.
So I had to make my mind, was I willing to fight for the kind of life I wanted? And not only was the answer yes, but by now I can also say: It worked.
But this process didn’t come without it’s fair share of challenges. It wasn’t easy. And yet I would be lying if I were to say I didn’t learn anything from it.
I gained more than just the job I wanted from this experience – I gained valuable lessons that will forever change the way I see life. And these are the ones I want to talk about today.
Choosing a career can be daunting, and it can feel like the whole world is on your shoulders. Here we’ll explore how to choose a career that fulfills you.
What is Test Driven Development? How does TDD benefit us and our team? And, How can we write effective and efficient Unit Tests for our code?
There’s a lot of talk about what organizations get out of pair programming. But, what about developers? How does it help us grow as professionals?
There are still a lot of questions around React Fiber. This article seeks to answer one of them: What does Fiber mean for rendering in React?
What makes a good user experience? Is it about making the user feel good while doing it? Should we even let the user know that this experience is designed?