For the Donna Service Organisation (DSO) I was team lead of one of the DevOps teams.
The team is in charge of a subset of functionality within the existing monolithic
application. This means that we were responsible of maintaining the code within the
monolithic application as well as migrating the functionality from this monolithic
application to microservices.
For Kadaster I was team lead of a DevOps team in charge of migrating the existing
landscape to support loading and reading data from their newly developed datastore
solution (Datahub). The team is part of the DSO project. Besides the migration we built
and maintained the application stack required for the project.
For the Gidso project I was team lead of a small DevOps team, implementing new
functionality to connect new customers to the Gidso platform, a large Saas platform for
the social domain. An important part of the assignment was implementing new
functionality for the city of Amsterdam. Besides the regular development work, I had to
coordinate the new functionality with all stakeholders.
At the Kadaster Data Platform (KDP) project I was part of a DevOps team that built and
maintained a stack to make large datasets accessible throughout and outside of the
organisation. My work consisted partly of contributing to DotWebStack, an open source
framework that enables API creation by configuration. And it consisted of maintaining the
orchestration layer for extracting, transforming and loading the Linked Data from (mostly
html and xml) ?bestemmingsplannen? for the IHR (Informatie Huis Ruimte) project, part of
the DSO (digitaal stelsel omgevingswet)
The Equestic Saddle clip is an electronic sensor that you can easily attach to the saddle
of your horse. It measures the training and analyses the results. You can use these results
to customise your training routine. The ambition is to help one million horses and riders
worldwide to grow up to Happy Athletes. For this innovative sensor I was part of a small
DevOps team that developed a mobile application that could connect with the Equestic
Saddle clip, read out the measurements and show the analysed results. For the more
sophisticated analyses the measurement was sent to a java backend, that we also
developed.
The Equestic development team was very small, so as a developer I was involved in
all parts of the development process for both the mobile application as well as the
backend application. From writing technical designs, to developing new functionality and
maintaining existing functionality. One of the important topics that we touched during my
time at the project was setting up App store and Play store subscriptions. During a large
part of my time on the Equestic project I was the scrum master and I was greatly involved
at improving the continuous integration process.
For the Donna Service Organisation (DSO) I was team lead of one of the DevOps teams.
The team is in charge of a subset of functionality within the existing monolithic
application. This means that we were responsible of maintaining the code within the
monolithic application as well as migrating the functionality from this monolithic
application to microservices.
For Kadaster I was team lead of a DevOps team in charge of migrating the existing
landscape to support loading and reading data from their newly developed datastore
solution (Datahub). The team is part of the DSO project. Besides the migration we built
and maintained the application stack required for the project.
For the Gidso project I was team lead of a small DevOps team, implementing new
functionality to connect new customers to the Gidso platform, a large Saas platform for
the social domain. An important part of the assignment was implementing new
functionality for the city of Amsterdam. Besides the regular development work, I had to
coordinate the new functionality with all stakeholders.
At the Kadaster Data Platform (KDP) project I was part of a DevOps team that built and
maintained a stack to make large datasets accessible throughout and outside of the
organisation. My work consisted partly of contributing to DotWebStack, an open source
framework that enables API creation by configuration. And it consisted of maintaining the
orchestration layer for extracting, transforming and loading the Linked Data from (mostly
html and xml) ?bestemmingsplannen? for the IHR (Informatie Huis Ruimte) project, part of
the DSO (digitaal stelsel omgevingswet)
The Equestic Saddle clip is an electronic sensor that you can easily attach to the saddle
of your horse. It measures the training and analyses the results. You can use these results
to customise your training routine. The ambition is to help one million horses and riders
worldwide to grow up to Happy Athletes. For this innovative sensor I was part of a small
DevOps team that developed a mobile application that could connect with the Equestic
Saddle clip, read out the measurements and show the analysed results. For the more
sophisticated analyses the measurement was sent to a java backend, that we also
developed.
The Equestic development team was very small, so as a developer I was involved in
all parts of the development process for both the mobile application as well as the
backend application. From writing technical designs, to developing new functionality and
maintaining existing functionality. One of the important topics that we touched during my
time at the project was setting up App store and Play store subscriptions. During a large
part of my time on the Equestic project I was the scrum master and I was greatly involved
at improving the continuous integration process.