Software creation is my profession and at the same time a hobby of mine. I strive to create good (software) solutions for the case at hand. Because of my inherent interest in technology I keep up-to-date with the latest developments and am able to choose the right tool for the right job, which can either be something state of the art or proven over time.
When not busy with software I like to watch series and movies, play (board) games, read a bit, do sports, and enjoy time with family and friends.
Some facts about me:
Product owner and team lead of the Router team. Focus points are:
I'm also improving the aforementioned testing suite. Improvement points are mainly concerned with increasing the stability and extensibility of the code and the investigation and implementation of infrastructure enhancements.
Product owner of the Bot & Router team, facilitating collaboration between teams within the CM.com SAAS portfolio.
Aside from my primary responsibility I worked on an end-to-end testing suite based on Playwright and Appium. It involved testing various parts of the CM.com ecosystem and their respective integrations. The tests were based on automations of frontend interactions, API calls and mobile app usage. Metrics were logged to a database to enable the inspection of (historical) latency.
Product owner of the Bot & Router team, which delivered products part of the CM.com SAAS portfolio.
Pre and post sales technical consultancy and implementation of CM.com offerings, specialized in the Conversational AI Cloud. Cases ranged from standard implementations to projects with significant custom work. As a B2B company clients came from diverse sectors. Examples of those clients were Webhelp, Partou and the KNVB.
Backend developer and helping hand for the frontend and automated test developers.
Manager in name, developer in practice. Worked on a single project, starting from scratch and up until the point it was an internationally used platform.
Development started with me being a one man team. Therefore I did everything that had to be done, including but not exclusive to determining a fitting architecture, building the backend and frontend, setting up a test suite, creating a CI/CD pipeline and adding integrations with other systems. Once more people joined the project two teams were created. One was responsible for the core platform and the other for implementing the business logic ran on top of the platform.
I developed as part of and guided the multidisciplinary team responsible for creating and maintaining the core platform. This was done in a DevOps fashion. We also provided guidance and support to the business logic team. At the same time I worked on mapping out the technical future of the platform.
Full-stack developer with a bit more focus on the frontend than the backend. Spent a lot of time with GoJS. Work ranged from creating a testing framework and setting up a frontend to creating and consuming APIs and doing maintenance and support on existing codebases.
As part of a movement where test engineers were teached to write code I functioned as one of the persons who supervised them in their ambitions to become Oracle Certified Associate, Java SE 8 Programmer.
Got my first experiences with frontend development.
Backend developer. Worked a lot with Aquima (renamed to Blueriq).