It has taken a little time for technology like GraphQL to settle in. I find myself in conversations with folks about the use of GraphQL and whether or not it makes sense to use for their project. Maybe GraphQL is good for you, perhaps it is too soon - but

Save yourself some time debugging whether or not you have the correct paths to modules you are importing. I have found myself in a lot of discussion around Javascript standards and style. I have been a long time fan of the airbnb javascript style guide [https://github.com/airbnb/javascript]

I have been interviewing recruiting and coaching engineers since early 2013. During that time I have developed frameworks, onboarding strategies, and interviewing workshops that help folks succeed in recruiting. In this post, I wish to share with you one process for the technical screening, commonly known as the phone interview,

Stepping into ES2015 Here is a starter guide I had put together to help people get to know at least some of the more common constructs found in ES2015 / ES6. It references some of my favorite materials I have come across and sets up a few questions for you to

I have been a huge fan of Meteor.js [https://www.meteor.com/] and the thinking behind the framework for the past couple of years. From the first time I hacked up a small todo's application over a weekend to building a large scale web application like ClassMate.

In this tutorial will make the following assumptions: 1. That we have a document set we are acting upon that is provided the Schedule symbol to be acted against. This is common in Meteor.js applications. 2. We are using ES2015+ 3. The code you are about to see is

Before we get into some of the code we will make the following assumptions: 1. Our document set is named Schedule 2. We are using ES2015+ Take this example document structure: { _id: '123-456-789', ownerId: '123', schedule: [ { _id: '432-1234-12', sectionTitle: 'Section 1', }, { _id:

I Love the Term ES6 It easily rolls off the tongue and is slicker to write about. ES2015 sounds clunky and is hard to say. I always want to abbreviate it in conversations. I would say "ES15" or "Modern JS" or "ESNext", which of

Good Developers are a Rare, and Expensive Commodity -------------------------------------------------------------------------------- A Developers time is best spent doing the work that really makes a difference for your team and your product. While there are many topics to cover for how Developers may manage their time, there are things we can do to