During my first few months at Yoast, I focussed on developing content checks to help our users to write more readable content. When I was asked if I wanted to assist in writing the code for those checks as well, I immediately said yes!
My temporary move to the development team turned out to be quite permanent. After implementing the readability checks, I started to work on our internal linking tool that suggests to which related post users might want to link. Over the years, I’ve been part of many development teams: I joined the inaugural MyYoast team, switched back to the plugin team, became team lead of the Gutenberg integration team, and later of all plugin development teams.
Currently, I’m the development manager of the plugin team, and the plugin release lead. I’m responsible for the productivity, quality of work and professional development of the plugin development teams. I also make sure that everything on the dev side goes as smoothly as possible for every release. I enjoy improving processes, responding to quickly changing circumstances, and getting things done together.
As plugin developers, we are continuously working on implementing features and fixing bugs. We’re not flawless, but fortunately we, at Yoast, have a QA team that tests our plugin daily, both manually and automatically. Sometimes when they find a bug, a specific commit or pull request comes to mind that is the likely cause. Sometimes […]
Read: "Using git bisect to find the commit that broke your code"
At Yoast, we like to release often. We’re a fan of continuous delivery and currently release every two weeks. As we sometimes get questions about our release cycle, we’d like to tell the entire story on why and how we release and test our plugins before they are ready to be installed on millions of […]
Read: "Continuous delivery at Yoast"
