Pieter Jordaan
Lead Developer
Utrecht, The Netherlands
Actions
Pieter Jordaan is a lead developer at PAQT and has been working with PHP for 15 years. He started his career in development back when Internet Explorer 6 was still a browser he had to support, giving him a long-standing perspective on how web development has evolved.
Although his background is strongly rooted in backend development, Pieter enjoys working across the full stack. He is particularly interested in the boundary between frontend and backend: API design, application architecture, data flow, and building maintainable applications from end to end.
In 2026, Pieter spoke at the Dutch PHP Conference (DPC) with his talk File Uploads and REST, exploring the challenges and considerations around handling file uploads in REST APIs.
Over the years, he has worked with a wide range of frameworks and technologies, and enjoys sharing practical lessons from real-world projects. He is also the creator of Apie, an open-source PHP library focused on better tooling for Domain Objects.
Area of Expertise
Topics
File Uploads and REST
So you have built your fancy JSON REST API, maybe even add a fancy OpenAPI spec of your API. And then you have to add file upload functionality to your REST API. You will notice that your API is not made for file uploads. What is the proper strategy to handle file uploads in a REST API?
What makes a framework enterprise?
I've read a lot of articles about framework X versus Y, even wrote a blog article about the silliness of comparing Laravel with Symfony for example. The argument I hear most is that Symfony is a better match for enterprise applications. But you also have similar examples like comparing Vue.js with Angular. Now my question is what makes something an enterprise application and why does this effect the choice of framework? It should be more than 'enterprise requires more abstract, complicated code', as any application of any size benefits from 'clean code'.
The Messy History of the JavaScript Bundler
JavaScript bundlers didn’t appear out of nowhere. From early script concatenation and AMD to Browserify, Webpack, Vite and the modern JavaScript toolchain, we’ve accumulated a surprising amount of history — and baggage. This talk takes a look at how we got here, why bundlers became so complicated, and what we can learn from the problems they were built to solve.
Help! My lead developer does not understand DDD!
Ask a developer if they ever did DDD and it's very likely they say yes. But if you ask if they executed DDD correctly in the project you will get a very different response. So what IS the correct way to do DDD and why is it not being executed properly?
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top