Daniël Koek

TBD

The main tasks I had at Uniphar were:

• TBD

I was asked back at Kiwa, not for the project that I was originally hired for, but for help with some of their internal systems, since they needed a bit of TLC. During my time I mainly did maintenance and small features to existing projects. But since the applications were mostly written in .net framework I also decided to help out with a migration to .net core, with some minimal effort I was not only able to remove any dependencies that would stop us from switching, but I also successfully migrated the application. Since I can very quickly learn a new system inside out I was also asked to help and support some older applications and to write up some documentation that was not available

The main tasks I had at Kiwa were:

• Help maintain the applications
• Fix bugs, create new features and find new bugs
• Clean up legacy code, upgrade projects and invent upgrade paths
• Help with invoice proposal
• Understand code that nobody in the company had any knowledge of and come up with solutions to get this code more maintainable

When I joined Vicrea, the application was a Proof of Concept. It was built locally on portainer instances. Little consideration was given to reliability, security and isolation of business logic. My main task was to get a production-ready application launched. By leveraging my years of experience in various software stacks, I was able to create a version of the application that could be run natively on the cloud while maintaining high observability that would be expected of any modern application. Lastly I removed all manual steps such as the provision of new customer environments and ensuring the application could handle large amounts of data, without incurring a large cost to the company.

The main tasks I had at Vicrea were:

• Creating CI/CD pipelines to automatically deploy new versions of microservices (leveraging helm)
• Isolating the FE from the BE and deploying this using Cloudflare workers in order to have a serverless global low latency way to serve HTML/CSS/JS
• Building logic so that part of the FE was only available for authenticated users
• Automatically using infrastructure as code to provision new environments, including databases, docker registries and k8s clusters
• Refactoring major parts of the existing code to be compliant with Domain Driven Design concepts
• Creating background processes that would pull large datasets from various government agencies. This was then redistributed to various internal APIs, which in turn would provide insights for users
• Removing FE-microservices and creating a mono FE, refactored from single-spa to Remix, introducing Tailwind and moving from Leaflet to OpenLayers
• Mentoring/teaching other developers in kubernetes and how to develop decoupled software

We have been tasked by Kiwa to produce a proxy type application to collect and process data for the manure industry, since this system had to be asynchronous, reliable, secure and highly flexible, we chose to build this in containers and with kubernetes, since I had previous experience in this, I was tasked with setting up the basic system and design it. Because of my previous experience we chose to use Kafka as the Pub-Sub system, since this is highly reliable and ES for logging, since this is almost a de facto standard by now. We decided for an API based FrontEnd using a utility based CSS and Web components to keep this part also very flexible and scalable. This was the first time I had to do everything from scratch and learned a lot from this, also new for me was the extended way we used EF, this is something I dealt with in the past, but I did not make myself an expert in. We also created our own OAuth server due to the restraints presented to us, all in all a project where we not only proved 'new' technologies are worth it, but they are also highly flexible and maintainable when done right.

A few selections of the main tasks Daniël did were:

• Build, design and implement the infrastructure
• Introduce new technologies to Kiwa who still runs some of their servers on bare metal and has no prior history with technologies like Docker
• Build, develop and CI/CD backend services to process: SOAP, XML, SFTP and have restful APIs to have a very flexible set of data to insert and collect
• Create a dynamic FrontEnd mostly driven by data entries (tables) that need to be very readable, responsive and flexible for future changes
• Create a full OAuth flow, which has multiple login systems, with roles that can be maintained from the FE, it also has a "Permission Module" uniquely developed for the Agriculture market, but highly customizable for future portals
• Improve security throughout the whole process, create Tunnels using Cloudflare, have E2E HTTPS traffic, create a Zero trust security plan where security standards are higher than any company I ever encountered

When I started at Univé there were a lot of older techniques that were being deployed, for example jQuery. This in combination with the hard to read code, made developing slower for all the developers. That is why at Univé I introduced a few technologies, mainly Web-components (using LitElement) in combination with a Utility based CSS called Tailwind. This made developing quicker and more productive, without changing too much of the current workflow, but it dramatically decreased the size of both the JavaScript libraries and the size of CSS, on new components. To make it even better to manage and develop in I also introduced Karma for unit testing and Storybook as a component library, this so UX could view the components in an earlier stage and for us to have a better view of what is where and how. This allowed us to create a more powerful User Experience, while maintaining a consistent look and feel.

A few selections of the main tasks Daniël did were:

• Maintaining unive.nl and the logged in environment of unive.nl
• Introducing new technologies tailored to the product and bringing this to production (Tailwind, LitElement)
• Maintaining build and release pipelines and improving these for quicker builds and better stability
• Create new features, that with the limited availability of other systems, still gave a rich user experience, by finding creative solutions, rather than limiting yourself to the systems you don't have control over
• Being a helping hand for other team members, when they can't figure out how to build new or improve existing code

Within RTL there are loads of systems that need to communicate with each other, the main idea of this project is to combine this, going from a few source systems to multiple target systems, thus reducing load. This also makes it possible to integrate legacy systems with the newer systems RTL acquired, this data in the end will serve as metadata for platforms like RTL XL and Videoland

A few selections of the main tasks Daniël did were:

• Adapt/Receive data from 1-2 source systems
• Create Distributors that Distribute these to 4 target systems, each tailored for their target system needs
• Finding and resolving both technical and non-technical queries
• Build a CD/CI pipeline in Azure DevOps
• Create and setup Azure resources
• Guide the team as a team lead, introducing Kanban and getting business requirements from POs

MyDataFactory is a company that specialises in building matching engines for customers that have invoices coming in from different sources and that want to match this to their own in-house catalogue of products. Through the process of manual and automated tagging of potential products, the user can decide what products with what items on the bill, after which the system will improve itself to remove further human intervention.

A few selections of the main tasks Daniël did were:

• Building a Front-End where the matches can be suggested and approved, and after this processing, can be downloaded for other systems
• Building and deploying a proof of concept to move all the current infrastructure to Kubernetes with code as infrastructure, in which I used helm to automate this better
• Moving the existing tag structure to a single system, with some minor improvements and building full deep dive tests to guarantee tag behavior currently and in the future
• Move existing Azure functions to pods in Kubernetes, which are now using Kafka to get queue messages, this to improve performance significantly, after which the data will be saved in ElasticSearch

PFM creates reporting/data repair and data collection software to measure footfall (visitors). Currently the old stack needs to be phased out since the code is never maintained and is not correctly built. So Daniël and the rest of the development team is working on this new stack in .net Core(v2.1) + angular (v6) to create the same functionality as the old stack, but with many improvements and optimisations. Partly by improving on data flow and partly by cutting cost, utilizing more Serverless approaches like lambda

A few selections of the main tasks Daniël did were:

• Build new front end functionality, improve and refactor existing code in angular and VMware's clarity which interacts with a backend
• Create lambda's that get kinesis events for parsing data from sensors that are in the field, which then get processed and finally stored if all data is correct

The fraud prevention system main task was:

• Fact/Score based system to indicate if a transaction that our customer sent us is a legit person
• Get the good guys in, make it very hard/impossible for the bad guys to come in
• Aggregation over big sets of data to determine if the end user is a valid user (identify the user based on their history)

A few selections of the main tasks Daniël did were:

• Integrate with 3rd party data sources for better fact results, for example: xml, soap, custom xml, json etc.
• Extend existing API and service these new and existing API in a VueJS application for demo purposes
• Creating Test systems/Mock systems for better QA automation
• Improve existing delivery pipelines to speed up releases and remove manual interaction
• Building custom nifi processors for handling data streams
• Being on an on call rota for outages (remote logging into systems to determine why the system went down or is using so many resources)

Combined back-end and front-end developer. I develop a medical record system for nearly all cruise ships, which are strictly monitored by coast guards, no record can ever be deleted and records require to be implemented using comprehensive guidelines.

Daniël worked directly with clients on issues that require development as well as creating completely new enhancements set by the company.

Testing of Apple software products, logging and raising bug tickets and language proofing of translations in my mother tongue (Dutch).

As a consultant working in the rapid prototyping department Daniël was responsible for the development and creation of several technical prototypes for automation systems for third party clients. Projects include:

• Model taxi parking system for KLM: Creating an experimental parking system for taxis near the Netherlands biggest airport on a small scale. Removing much needed space while removing waiting time for taxi's, so they can be more efficient.
• Smart health app for Interpolis: Health app for iOS using Apple Watch biometrics designed with heavy gamification to reduce and prevent stress that leads to burnout and its high exposure to health insurers.
• Evacuation application for ProRail: Created a custom evacuation application, that even works when the internet is temporarily not available for Dutch railroad infrastructure.