GitHub is an amazing company and an amazing startup story.  We're not only customers of the product, we're huge fans.  

In part 1 about HubSpot’s approach to front-end development, we talked about common issues with sharing front-end code (JS, CSS, etc) across teams and how dependency management can help.

However, dependency management of front-end code is a relatively new thing. There have been a few projects that have started taking that path, but developers haven’t yet taken into account how front-end web code is subtly different from typical desktop or server-side code.

Console.log is one of the simplest, and most powerful, tools frontend developers have.  Turns out, it's not quite as simple as we thought.  Console messages can be formatted using CSS.  You could, for example, make your error messages larger:

The HubSpot usability team loves to get feedback on apps we’re developing to make our customer's marketing lives easier. But testing in the mobile environment presents a unique set of challenges. We recently devised a system that allows us to get much more insight from our testing sprints with real mobile users, using real apps in their natural environment -- in situ -- and discovered a whole new set of questions we were able to ask as a result.

Last week the product team went out for a night of dodgeball, falafel and cocktails. Apply to join our team at http://dev.hubspot.com/jobs and join us for our next event!

Last Wednesday I gave a Tech Talk, Pixels Matter, to the Dev team.

Over the years, our engineering teams at HubSpot have run into issues with deploying, updating, and sharing front-end assets (e.g. Javascript, CSS, images, etc). Sure, web development has come a long way, and the latest browsers, libraries, and tools enable us to build incredibly rich and complex applications. But in many ways, webapp development is still quite young.

Note: this is the first in a series of posts on how to do UX in a fast-paced company like HubSpot. Subscribe to our email updates for future posts.