Joris Saenen
Dev Engineer - ING Belgium
Hasselt, Belgium
Actions
Joris is a seasoned technology enthusiast whose journey began with early explorations on Microsoft DOS. From navigating command lines to launching games, his curiosity has evolved into a passion for making a significant impact in the tech world.
As the Lead Developer of an international team at ING, he plays a pivotal role in ensuring seamless and secure transactions through Bancontact, Payconiq, and Wero payments. With a commitment to excellence, Joris drives innovation and efficiency, enhancing the customer experience globally.
A dedicated mentor and motivator, Joris thrives on sharing knowledge and inspiring colleagues to reach their full potential. Continuous improvement is at the heart of his professional ethos, with a daily focus on personal and team growth.
Outside of work, he enjoys quality time with friends and family, engaging in sports, and running. A tech-savvy individual, Joris also indulges in home automation projects and self-hosted IT solutions, blending a love for technology with everyday life.
Links
Area of Expertise
Topics
Rubber-Stamp Coding: The Silent Threat in AI-Assisted Development
AI is no longer a concept of tomorrow. It is already writing our code, reviewing pull requests, and quietly becoming part of every developer’s workflow. This promises more productivity and freedom to focus on higher-level thinking. But it also introduces a silent threat: as AI generates code faster than we can read, we begin to approve generated code faster than we understand.
I call this rubber-stamp coding, a term inspired by the old bureaucratic habit of approving stacks of documents with a stamp, without actually reading them. We skim. We trust. We ship.
A second, less obvious risk is emerging too: the return of complexity. In the past, we deployed a few large releases per year. Agile helped us break that into small, manageable deliveries. But AI can generate massive, high-velocity code changes, turning weekly releases into mini waterfall launches. Without a mindset shift, teams risk blindly shipping flawed logic wrapped in syntactically correct code.
This keynote exposes the hidden pitfalls of AI-assisted development and challenges how we think about code, ownership, and accountability in an AI-augmented workflow. It is about staying sharp, critical, and responsible when the machine does the typing. Because if you're no longer writing the code, are you still the developer?
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