Why we spent a week on bug fixes
Like any product, there are bugs in Buffer. We believe that making these improvements while resolving bugs can have a huge impact on the user experience. But this week wasn’t just about bug fixes — this was about taking an opportunity to bring the whole engineering team together to improve how we work.
How Fixathon worked
Ahead of the Fixathon, we crafted a carefully selected list of tasks for our team to work on. Each day started with our engineers engaging in Bugsnag, a tool designed for monitoring and managing automated error reports. After triaging Bugsnag reports, our engineers shifted their focus to resolving product bugs. Throughout the Fixathon, we kept our Advocacy team in the loop with daily updates. On the last day, we focused on quality assurance (QA).
The results of our first Fixathon
Ultimately, we learned a ton by doing a Fixathon. We improved our collaboration, gained visibility into many issues, and resolved 44 bugs in total. While most of them were small, all of them contribute to our vision of a consumer-grade experience. Notable bugs we squashed included adding a billing page link, making “suggested media” scrollable, and styling changes for consistency.
As a part of the Fixathon, we’re also close to releasing the “first comment” functionality for LinkedIn. We consider Fixathon a successful initiative and hope it’s not the last one!
Did you miss our previous article…
https://onlinemarketingagencies.net/what-makes-good-b2b-content-experts-share-9-must-haves-for-success/
