Arthur’s story with Rollbar

Arthur Guy Head of Engineering
Arthur has now been using Rollbar for 109 months!

1. What company do you work for (describe the product/service) and what projects are you working on there?

I am the head of engineering at Vestd (www.vestd.com) and lead our engineering teams. We specialise in building share scheme and equity management solutions for companies allowing businesses to easily and safely issue shares and equity to their team and investors. Our products are complex with a lot of business rules and restrictions that come into play at various stages. We are currently working on some exciting new tools for our larger users to help them manage more things in one place.

2. What are you most passionate about in your current and/or past roles?

It's probably a cliché but I enjoy the challenge of building systems that solve problems. I really try and get to the underlying domain representation when designing a system, the better I can manage this, the more flexible and long-lasting the solutions tend to be.
Over the years this has morphed from tackling small problems on my own to guiding engineering teams to solve problems for big businesses and thousands of users, however, the approach has always been the same.
At Vestd we are solving some really big problems and doing so in a way that hasn't been done before so we are having to forge our own path. This can be frustrating as others in this space approach things a bit differently but we have a desire for something better and it's not always an easy journey.

3. Is there anything in particular about Rollbar that has kept you a loyal user all this time?

I can't remember what first led me to rollbar but I started using it to keep track of issues with various personal projects but quickly adopted it at Vestd. It's always been a straightforward service to implement thanks to its integration with the Laravel framework. It is also one of my pinned tabs that I always have open and refer to multiple times a day. On the odd occasion, we have a customer-facing bug I usually find that me or the team is rolling out a fix before the customer has even gotten in contact.
It's also a nice product to use, the integration with GitHub usually means the problem is displayed alongside the error message.