So you finally got that job you wanted. Sure, it took some time and effort, but you managed to score a well paid position that matches all your needs. It has good career advancement plan, great benefits and to top it all off: Work from Home days. And you could not be more excited to start cashing them in. Maybe you’re on a fully remote team, managing your own business or enjoying those flexible Fridays everyone was talking about. Whatever the reason may be, you get to spend a day at home in your PJ’s drinking soda with the TV as background music. Or maybe you even decide to go out and take your work to the park, or the local Starbucks. Life is good and you start to fantasize about trips to the Caribbean, and taking pictures of your laptop with an orange drink. Then all of a sudden phone…
A conversation with a coworker had me thinking about the role of a web developer in product development. And I thought I would share my thoughts on the invisible nature of our craft. I was having a conversation with one of the guys at work regarding the architecture of a particular service. And while I don’t really intend to talk about the specifics of that service, I did want to talk about something he shared with me. I’ll put it in my own words: My work is at it’s best when it’s invisible. And, I have to admit, the thought actually resonated with me, it got me thinking about some of my own best work. And most of all, it got me thinking about the role of web developers in the creation of a product. Which is what we’re here to talk about today. Let’s talk about web applications. Before…
It’s now been about 4 months since I started my new life as a remote worker. To be quite honest, it’s been pretty great: traveling, no commute, making my own hours, etc. And yet, at the same time, I’ve been able to experience some of the realities of this way of life. So in today’s post I thought I would address some of the Myths (and truths) about remote work. Before we get started, however, I’d just like to say that I’ll be tackling these myths from the point of view of a remote worker. This whole conversation will be about how remote work affects you personally, rather than how it affects a company. With that being said, let’s dive right in. Is Remote Work Lonely? Myth: Working remotely means you’ll have a lot less company. Truth: Working remotely means your company is going to be different. This particular aspect…
By now it’s been about a month since the last post that I released on this blog. And, if I may be allowed to be totally honest, that’s too darn long.
It’s been a month packed with experiences adjusting to a new life in a new place. A month getting back in touch with old acquaintances. And a month that allowed me to finally celebrate fulfilling the goals I set out for me this year.
Except the Corgi. But we’ll get to him later.
Yet, such a lengthy celebration kept me from writing. Which is not amazing, because writing is one of the things I enjoy the most in this day and age.
However, taking a month off gave me some interesting life perspective. Which I’m compiling into next week’s post called ‘Remote Life – Work Balance’.
And it also got me to think about the reasons for which I write this blog. Which I’m going to be sharing today. It’s a little bit personal so, if that’s not really your thing, you’ve been warned.
But if you’re interested, let’s talk about it:
In this article we’re going to go over a Front End Developer’s first impressions of the Python programming language. I’ll try to keep things as objective as possible, but do keep in mind that it’ll be permeated by my own opinions. That being said, if you’re shopping for a new language to learn next, perhaps I can be of some assistance. It’s been a crazy couple of months, and I’ve barely had any time to breathe. Part of the reason for that is because I finally moved back to my hometown of Merida Yucatán. Something which I’m extremely thankful for. But that also took a lot of my everyday time. The other part is because I took it upon myself to become a Full Stack Developer at my new job. And that (in my case) meant learning Python. Which proved to have to be a little bit of a challenge.…
Last week we went over the main principles of MobX, as well as why mixing it with React is an amazing idea. That covers all of the basics that we need and sets common grounds of understanding. Which means we can now focus on building our first application using the two of them. And that’s what we’ll be doing in this MobX + React Tutorial. Our first MobX + React Application. We’re going to be building an App called a List Detail View. The App will render out a list of one line “summary” components for larger pieces of data. Additionally, clicking one of them will render a second component containing more detailed information. In this way you click on a list element to view its details. List Detail View. Simple enough right? See the Pen #100DaysOfCode: (React + MobX) List Detail View by Orlando Paredes Hamsho (@orliph) on CodePen.…
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: