Moving Fast and Not Breaking All The Things Every day, Gusto engineers work on systems that move billions of dollars, secure sensitive customer information, and pay hundreds of thousands of employees. Our customers' livelihoods depend on our product,
In the previous posts, we covered why we moved away from Backbone [https://engineering.gusto.com/evolving-javascript-part-1-goodbye-backbone] and started building new features with React [https://engineering.gusto.com/evolving-javascript-part-2-hello-react]. To further reinforce why we invested in our migration
In the previous post [https://engineering.gusto.com/evolving-javascript-part-1-goodbye-backbone] , we detailed the reasoning that led to us moving away from Backbone. In this installment, we'll highlight how we framed the search that led us to React and subsequently
Note: This is the first post in a multi-part series about the evolution of our Javascript application over time. Here are parts 2 [https://engineering.gusto.com/evolving-javascript-part-2-hello-react/] and parts 3 [https://engineering.gusto.com/evolving-javascript-part-3-building-a-react-application]. The advancements
Here at ZenPayroll, writing software that pays tens of thousands of employees across the country inspires us as engineers to write bullet-proof code. As a team, we are committed to putting in the extra time to make our
Here at Gusto, we're all about abstracting away the complexities that come with compensation. Payroll has traditionally been a bureaucratic hornet's nest, and implementing a modern and delightful product in such an atmosphere is an engaging technical challenge--one
