We know Node.js for its lightning-fast performance. Yet, as with any language, you can write Node.js code that performs worse for your users than you’d like. To combat this, we need adequate performance testing. Today, we’re going to cover just that with an in-depth look at how to set up and run a performance test and analyze the results so that you can make lightning-fast Node.js applications.
Here is my latest post for Enov8.
“Wait, what actually is DevOps?”
If only I had a dime for every time someone asked me this. For many, the term DevOps comes loaded with misconceptions and myths. Today, we’re going to look at some of the common myths that surround the term so that you have a better understanding of what it is. Armed with this knowledge, you’ll understand why you need it and be able to explain it clearly. And you’ll be equipped to share its ideas with colleagues or your boss.
If you’re thinking of running a serverless setup, congratulations!
But…that means you’re running a distributed system.
With all the benefits and simplicities that come with going serverless comes this tradeoff: You potentially also have some increases in complexity.
Last year when I put out content around the new year about my plans I got a spike in traffic. I guess something about the personal nature of the post was attractive. Based on how much people seemed to like those posts, I thought I’d do another.
A round up of 2018 — and a goal set for 2019.
Containers are hot stuff right now, so it’s natural that you’re here wondering what the business case and benefits of containers could be.
If this is you—if you’re looking to assess whether containers would make sense for your company—then you’re in just the right place. Because by the end of this article, you’ll not only have a good understanding of what containers are and what they’re good (and not so good) at, but you’ll also have some decision making criteria to help you decide whether they’ll work for you in your unique situation.
Have you been thinking about wanting to write? Did someone mention to you that it might be good for your career? Or you want to write to earn some money? Maybe you just want to document your notes and share them with others?
I can’t read your mind and know your motives to want to start writing, that’s for sure. But what I can do is this: go through the fears that are currently stopping you starting to write. How do I know what these fears are? Because I have the same writing fears and I wrestle with them every day and every week.
Here is my latest post for Simple Programmer…
Recently, I conducted an experiment with my team.
This experiment was challenging enough to make even some seasoned developers sh*t their pants.
What experiment did we run? We stopped branching our code, we threw away code review, and we started pushing directly to master.
Recently I’ve been training for a long cycling event.
The event is a three day event where we will cycle around 70-100 miles each day back-to-back.
It’s very much an endurance event and for all my adult life, I’ve been a strength athlete competing in strength sports that are maximal exertion. It couldn’t be much more of a polar opposite set of skills.
I sat at a Starbucks cross-legged with my laptop on my lap. I’d gone out to try and find the peace required to focus on the job application I was completing as a front-end product developer.
The task was simple: Create a demo app that connects to an API (Foursquare) and shows the results.
As I sat there putting the finishing touches on the demo (you can actually still see it here) I had a realization…