Blog Home

What We're Learning in 2017

Whether or not you believe in resolutions, the fresh start of a new year tends to herald in feelings of optimism, as well as a resolve to do better than the year before. Last week, Sara took a walk down memory lane and shared her top five lessons from 2016. This week, we’re looking ahead and determining how to make 2017 a year that’s not only proactive, but also prolific.

As a team, Reaction Commerce will continue working toward v1.0 and the official launch of our managed platform as a service. But what about on an individual level? Which frameworks, tools, and projects are we most excited to learn, work on, and engage in? We did a quick poll around HQ and tallied up the responses. Here’s what we came up with:

Patrick, VP of Business Development:
I’m excited about two things: 1) introducing Reaction's great products to the world, and 2) building, growing, and optimizing a modern, data-driven sales team. They're both goals, but I know that there is a ton of learning that I have to do along the way. I expect it to be a daily process full of discovery.

I’m also on a mission to learn all about whiskey (bourbon and scotch). It’s more of a life calling than a specific learning.

Sophie, Content Manager:
Next year, I'll be taking the metro to work more often, so I'm putting together an extensive reading list for my commute. I'm interested in the following books about the Internet and the open web:

Brent, Software Engineer:
Practically everything I learn becomes obsolete in 6 months, but more of the following:

It would be nice to get really good at something for a change. Kids these days and their front-end frameworks.

Erik, Software Engineer:
Reaction will be making the full transition from Blaze to React next year, so I definitely want to learn more about React. It would also be cool to get more into Webpack. Also, I want to eat breakfast every day.

Ryan, Sr. UI Designer:
Work on a personal design project that's not Internet-related, just to keep evolving my design sensibility. I have an idea for some packaging design, and I want actually make some real-world prototypes.

Mike, Software Engineer:
I’m putting the finishing touches on my personal project, which is an app that’s built with Node.js, npm, React, and Webpack (Mike didn’t really want to get into any details beyond that, so I guess we’ll just have to wait!).

Jeremy, Software Engineer:
Definitely GraphQL. It’s basically the core of Meteor's business model now.

comments powered by Disqus