Here is my latest post for Stackify
Are you looking to get up and running with logging in Node.js? Do you want to understand best practices (and pitfalls) for structuring application logging in Node.js?
If that’s what you’re looking for, you’re in the right place!
Here is my latest post for Stackify.
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 Scaylr.
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.
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…
Here is my latest post for Simple Programmer…
There are many lists of books about becoming a better programmer. They likely include books like Refactoring, Code Complete, The Mythical Man Month, etc.
However, in the workplace, it isn’t just programming knowledge that we programmers need. Learning programming is an essential part of our work — but it’s not everything.
The authors of iconic programming books had remarkable careers, but it wasn’t just their coding knowledge that made their careers noteworthy. They were well-rounded experts and we should strive to emulate that quality as well.
Here is my latest post for Simple Programmer…
As programmers, we have a lot on our plates. Understanding the newest technology, the business, navigating politics in the business and in our teams, and all of the tools, languages, and everything else that comes with the territory. It is overwhelming.
When it comes to making improvements, it’s easy to be in favor of our own personal development over that of our teams. Choosing to focus on gaining personal skills over improving the output of the team or the business. After all, these improvements are a manager’s responsibility, right? Possibly. But this type of thinking can backfire on us if we’re not careful.
Why? Because, ultimately, we get paid for the value we deliver to our business. So if we want more pay, more recognition, and ultimately a better career, it makes sense to keep an eye on what the business wants and needs, not just our own personal development. That’s how our checks are paid and how we keep a roof over our head.
This type of thinking can seem somewhat counterintuitive, and maybe even scary, as we’re focusing on areas that feel outside of our control.
Here is my latest post for Simple Programmer…
It looked something like this: Become extremely knowledgeable in a given programming language until eventually you become a senior programmer.
Once you’re a senior programmer, you ride out the rest of your career as a programmer. Or you make a leap out of the technical world and into a strategy- or management-focused role.
For many programmers, this is a hard decision. Programming is what we love and we don’t want to lose our hard-earned skills. As programmers, we’re often very aware of how quickly our skills fade when we’re not in the business of putting out code anymore.
But it doesn’t have to be this way. There is another option that allows you to straddle both areas of the so-called softer and technical side of the profession.
And that’s in the realm of professional services.
