Code Screen Problems Don't Have to be Unspeakably Terrible

Many software developers are familiar with a “fizzbuzz”-type problem in coding interviews. The idea is to ask a fairly trivial coding question of candidates to make sure they are competent coders. This can be done on-site, or in a phone interview format. Although well-intentioned, these kinds of questions are annoying and insulting for qualified candidates, can give false negatives as a result of trivial errors (especially if asked on a whiteboard) and are tedious for interviewers to ask.


Inheriting Code: Why You Should Keep Code Teardowns to Yourself

We all dream of a perfect, unencumbered world, working with a pristine code base or starting a project from scratch. In reality, I’ve started enough projects to know that I can build myself into a corner just as well as anyone else can, and that things always get messy unless you spend an incredible amount of time refactoring. I’d like to offer some advice about taking over someone else's code based on my experience: Keep your code teardowns to yourself. I learned this the hard way.


Lessons Learned from Last Week's S3 Outage

Like many companies, we were affected by last week's S3 outage. We were surprised, however, by the extent of the impact to our systems. It was a bit of a wake-up call, and we realized how much of a failure point S3 had become for us and how little we were doing to protected ourselves against S3 downtime. 


Update: How We're Building iOS Apps Today

Back in 2014, we wrote a post about how we were using CocoaPods to Modularize our iOS app. With our latest iOS app we released a few months ago, we went in a different direction - here's why.


Tech Talk at Night React Meetup (Video)

On Wednesday, October 12th we hosted a React Meetup here at HubSpot. We had a wonderful time with over 150 attendees, 200 delicious Mexican tortas, and lots of great content.

How to Set the Analytical Foundations for the Future of Your App

Do you know if people are using your product the way they say they do? Especially at scale, customer interviews and usability tests aren't enough to answer this question. You need to see  what happens in reality, which should be well reflected in your usage numbers. 

Subscribe for updates

New Call-to-action