In this post, I'll look at how DesignHammer improved our Jenkins build process by adding a testing workflow and setting up a parallel Build Flow job.

Welcome to the first edition of DesignHammer Updates where we will keep you apprised of news, tools, and tips. January can be a slow time of year, but we were busy onboarding new clients, sponsoring conferences, and staying informed on the ever-changing technological underpinning of the Web. I hope you enjoy the short contributions from the DesignHammer team; if you do, please complete the survey linked at the end to help us evolve into an even more engaging format.

One thing that makes DesignHammer unique is our diverse team. Each week team members invest time reading about individual interests to stay relevant. For example, this week a few things we read about include: Star Wars details, Google approved links, social media checklist, and improved tab sorting.

In the technical world, things are constantly changing. Because of this, our team members consistently seek ways to stay up to date. This week we address the following topics: using npm as a build tool, creating a great work environment, process, and project management mistakes to avoid.

Each week, members of the DesignHammer team share insights from readings done that week. This week we're covering: how busyness isn’t productivity, 2017 SEO predictions, overcoming IT project management challenges, and the value of having all staff members blog.

Call them resolution, intentions, or self improvements, now is the time of year many people set goals in the personal and professional lives. At DesignHammer, we are constantly striving to improve our process so we can help our clients overcome business obstacles with a better return on investment.