Blog

We are pleased to share that our colleague has recently been awarded the Mendix MVP Trainer certificate — a recognition given to experts who actively contribute to the low-code community through knowledge sharing, training, and platform expertise.
As a Senior Developer, he combines hands-on project experience with a strong passion for teaching and enabling others. Through his training sessions, he helps developers not only learn how to build applications in Mendix, but also understand the software engineering principles behind scalable and maintainable solutions.

In this interview, he shares what motivated him to become an MVP Trainer, the challenges of teaching low-code development, common mistakes developers make when starting out, and how he sees the Mendix ecosystem evolving in the coming years.

What motivated you to become a Mendix MVP Trainer? 
As a Mendix trainer I enjoy working with people and helping them grow. A key aspect for me is making software development more accessible to a wider range of people and enabling them to contribute. 
My main motivation for becoming a Mendix MVP was to stay closely involved with the evolution of the platform, remain in the loop as new features are developed, and have the opportunity to share my ideas and feedback. The MVP program is a great way to contribute to both the community and the platform while staying connected to the product team. 
 
What does being a Mendix MVP Trainer mean to you personally? 
Being a Trainer MVP comes with a sense of responsibility and pride, knowing that the guidance I provide to trainees can influence project quality, contribute to successful outcomes, and accelerate digital transformation. 

What’s the biggest challenge when teaching Mendix to others? 
Usually, my trainees are technology-affine and pick up how to build apps really quickly. What’s often missing at the start is the mindset behind low-code development: it’s not just about dragging and dropping elements, but about designing clean logic, considering performance, security, and maintainability. 

What’s one mistake developers often make when starting with Mendix? 
A common mistake beginners make is overcomplicating their logic flows, spending excessive time building complex microflows when simpler solutions exist.  
Performance considerations and best practices for designing modular, efficient, and maintainable microflows are often overlooked as well. This not only slows down the app but also makes future maintenance and scaling much more difficult. 
 
What advice would you give to someone who wants to grow in the Mendix ecosystem? 
Although low-code significantly simplifies and accelerates development, anyone who wants to become an expert in Mendix should still learn fundamental software engineering principles. This includes topics such as clean data structures, branching strategies, security and performance best practices. In addition, gaining experience in UX/UI is important as well. The fast development pace allows developers to be involved in many different aspects of software development, which makes being a generalist a key advantage. 

How do you balance low-code speed with clean architecture? 
While Mendix helps to increase the development speed significantly, it is important to keep classical software architecture principles in mind. A clean data structure and clear separation of front-end and back-end logic (especially for security and performance reasons) are key. Coding conventions, like the ones we use at BlueBerk, provide guidance to less experienced developers, giving them guardrails to maintain quality without slowing down development. 
 
What separates a good Mendix developer from a great one? 
In Mendix development, technical skills alone don’t make a developer great. A good developer can build a solid and stable app. A great developer goes further: they actively collaborate with users during development, helping them clarify their real needs and identify low-hanging fruits.  
In short: technical mastery builds a good app, but a great developer guides the customer to the most effective solution. 
 
Why is internal enablement important in low-code projects? 
Internal enablement in Mendix projects is important for two main reasons. 
It improves understanding of the Mendix platform, which often sparks new ideas for further simplifying and optimizing business processes. 
And it reduces dependence on external partners for development and app support, giving the organization more independence and control. 
 
How do you see the Mendix ecosystem evolving in the next years? 
I see the Mendix ecosystem evolving significantly especially as a backbone for AI applications in enterprises. AI can’t operate in a vacuum, it needs a platform that maps and manages business processes and data to fully leverage its potential. 
Additionally, AI will transform Mendix development itself. Just as we’ve seen in high-code environments, we can expect prompting and AI-assisted development to become part of Mendix, making it even easier for users to build applications and lowering the barrier to entry. 
 

About the Author

Fulya Gürcan is a Senior Mendix Developer at BlueBerk, she specializes in the design and implementation of scalable low-code applications. She is certified as an Advanced Developer by Mendix and contributes to projects by turning complex business requirements into reliable digital applications.

In addition to her technical responsibilities, she contributes to marketing and communication initiatives, helping to communicate technological developments and practical insights from digital transformation projects within BlueBerk.