We had ourselves a bug week
No new features. No detailed plan. Just bug fixes for a week.
Knut Melvær
Head of Developer Relations at Sanity.io
If you have ever built or used software you know this: There will be bugs. When Grace Hopper coined the phrase in software development it proved to be an actual moth that had crept into the hardware and made trouble (original bug report in the photo above). As far as we know though, there aren't any moths inside our React code.
At Sanity.io we're a team of developers who make a platform for structured content, used by many different people for many different things. Feature requests from the community, strategic product decisions, and the needs of our customers will mostly end up getting prioritized. As it well should be. But it also means that it's easy to let those bugs rest in their hiding places while we focus on the new shiny stuff.
But bugs aren't just annoying for people who may encounter them when using our software, they're also… well, bugging us who develop and design the product. Because we know they are there. Some bugs may never really affect users directly or just in some rare cases, while some bugs are more intrusive. Either way, there's nothing more we would like, than to squash them.
So we had ourselves a bug week!
No new features. No detailed sprint plan. Every developer got to pick the bugs that annoyed them the most and fix it. The result: 32 Pull Requests to the next-branch.
We have fixed bugs in the CLI, Structure Builder, error handling, the editor for Portable Text, the Form Builder, the mutator, visual components, block-tools, and validation. Pull Requests will now be reviewed one-by-one and shipped to you in the next releases.
It felt invigorating! Cathartic even! And we're definitely doing bug week again!