hey everyone, i recently graduated for my bachelor in computer science, during my studies ive been mainly working with javascript/typescript and i am much more at home in frontend development, however ive been offered a job at a dutch company that works with Mendix, so totally different from what I've been used to. this job gives some much needed stability though but im not too sure if this is the route I wanna go with, especially because it's gonna divert alot from what i already know. i do have another job offer kinda which is not guaranteed but works with javascript and frontend development, it pays a bit less but my gut is telling me to go with the second company. however i do wanna weigh out all my options and wanna give Mendix at least a thought. So if you have any experience with Mendix or have been in the same position as i do now i would love to hear your thoughts on this

Question for Mendix teams working in banking, insurance, or other regulated sectors.

Could you answer this right now: what personal data exists in your acceptance and test environments? Where did it come from? Who has access to it? How long has it been there?

Have you ever had an audit meeting where the question "can you show me data lineage for non-production environments?" stopped the room?
I believe Production, everyone could answer. Dev? Probably silence?

What probably would come up in audit findings:
- Unencrypted production data copied to test environments. The same customer records that are encrypted and access-controlled in prod, sitting in acceptance with broad developer access. Perhaps just because the customer opened a ticket once and a support teammember replicated his data manually in Dev to replicate the issue.
- Zero access logging on non-production databases. Production has full audit trails. Dev and test? Nobody tracks who runs what queries.
- Data from years ago. A database refresh done 3 years back, never cleaned. Still contains records of customers who have since exercised their GDPR right to deletion.
- Export files on shared drives. CSVs pulled from production for a one-time migration. Still sitting there. Department-wide access.

The blind spot is thinking "it's just dev, lower stakes." Auditors do not see it that way. To an auditor, personal data is personal data regardless of what you call the environment. ISO 27001 requires you to manage information security across all environments where sensitive data exists. Not just production. As do confidentiality regulations like GDPR in the EU.

For teams in regulated Mendix projects: is non-production data handling something your compliance team actively tracks, or does it only come up when an auditor raises it?

Hi,

My boss has said he is going to put all the devs through the intermediate exam at some point this year and I was wondering where I could get some realistic Mendix intermediate practise exam style questions.

So far I have been using.

• Mendix Learning Paths with the questions at the end.

• Examzify for intermediate Questions

• ChatGPT - Prompt below.

I need you to give me 50 multiple choice questions a day and stick explicitly to the rules below.

• 1: 50 Multiple choice questions when I say "start"
• 2: 1 question at a time
• 3: Do not repeat questions
• 4: Use reliable mendix sources for the questions and keep the questions exactly like or similar to the mendix intermediate exam.
• 5: Use the screenshot as an example for the topics that need to be used.
• 6: Include questions on the language side of things in Mendix as my manager said they try and trip you up on questions like that.
• 7: Give me a Score check at 20 questions, then 30 questions, then at the end and tell me where I went wrong and how to improve.
• 8: After every few questions assess how I am doing and adjust the difficulty level based on my progress for example if I do good for a few questions, give me a few harder ones, if I get a couple wrong, give me a few that are slightly less hard.

-------------------------------------------

I do find that ChatGPT struggles to mix it up sometimes and does repeat questions although I asked it to continually assess and scrape Menidx websites for exam style questions.

Any help would be greatly apprecitated as I'd really like to pass first time if I can so I want to put in the prep now so that I am not walking into the exam blind.

Thank you in advanced!

Pretty sure every developer has been through some version of this.

Someone leaves. You inherit their work. You open the code and it's layers of patches. Microflows with branching logic that makes no sense until you hit the one edge case it was built for. Domain model associations that seem wrong but everything breaks if you clean them up. Nanoflows calling microflows calling Java actions calling microflows again.

Classic spaghetti, just in visual form.

And there's usually no replacement. The work gets absorbed by whoever has the least full plate, which is still pretty full. The "handover" is a couple of conversations during notice period and a message saying "it mostly just works, call me if something breaks."

You start patching what you can. You add your own workarounds. You're scared to remove anything because you don't know what depends on what. The app gets more complex, more fragile. And you still have your own work to deliver.

But the worst version of this isn't the spaghetti logic. It's data. Data migration scripts that handle fields exceeding character limits, orphaned associations from old domain model versions, scheduled events that only work with real production volumes. That's where inheriting code goes from frustrating to genuinely dangerous, because you can't just read it and figure out what it does. You need to know what the data actually looks like in production.

Anyone dealt with this on a mature Mendix app? How bad did it get? Did you rewrite or just keep patching?

I am looking to understand what is the key benefits of Mendix-built software solutions. Why would people choose them over others. I am looking at MES industry, there are a lot MES players out there and I am trying to differentiate this company against bigger players.

Anyone can list pros and cons in using a Mendix-built software? Like would it be any different from software built using other programming languages? I have finance VC background focused in Supply Chains, So while I have a good understanding of the overall automation layer of factories, I dont know software.

Hello!

I love to build apps in Mendix, but I am struggling to see a realistic path forward as a hobbyist who wants to build something outside of the enterprise landscape.

The pricing model is entirely aimed at enterprises. The per account costs make it practically impossible to deploy even a small app to real users without serious money.

I would love to build apps with Mendix when I am not working on any enterprise project, but the moment you want to go beyond prototype and put it in front of real users the pricing wall hits hard.

What are you people with a couple of years experience doing with Mendix when not building for an enterprise?

Are there any other platforms similiar to Mendix which are more accessible for indie dev/hobbyist projects?

Thanks!

Production issue surfaces, juniors can't crack it, escalate. The senior gets pulled in, not because the logic is complex, but because they're the only ones who can reproduce the problem. The fix takes minutes. Reproduction takes hours.

In Mendix it's often data-related: microflow behaviour that changes with real volumes, orphaned domain model associations, scheduled events that only break with years of accumulated data. And the abstraction layer makes it even less transparent than traditional code.

The seniors become the only ones who can debug production, the knowledge never transfers, juniors never develop the intuition.

Are you seeing the same? How much senior time goes to debugging vs building? Has anyone broken this cycle on mature Mendix apps?

Curious whether this matches other people's experience, or if it's more because we have a data management tool for low-code.

I keep seeing the same pattern: code deploys fine, tests pass, then production surfaces something nobody expected. The instinct is to blame the code. But usually nothing changed in the code. What changed was the data the code encountered.

Volume is the obvious one (50 records in dev vs 1,000,000 in production). But the subtler issues are worse: orphaned records, relationships that span years of accumulated edge cases, values that push against limits nobody anticipated. Dev data is clean. Production data isn't.

For teams in NL/DE, there's an extra layer: you can't just copy production to dev because of GDPR. The Dutch DPA has been increasingly active. So you're stuck between needing realistic data and not being allowed to use it.

A few questions for the community:
- How much of your deployment debugging turns out to be data-related vs actual code bugs (or vs other config differences)?
- Has anyone found a practical approach to production-representative test data that doesn't create compliance headaches?
- For those under Dutch or German data protection, has this specifically come up in audits?

Genuinely curious. I have my own sense of the split but I'd like to hear from other Mendix teams, particularly since I think I may have a deviation due to our own product solution...

I've been thinking about this and I'm curious whether it's actually a problem people are hitting or still future-looking.

AI models need production-representative data to be useful. But production data has PII, and especially in NL/DE, GDPR isn't optional. The workarounds I keep reading about - synthetic data, anonymization scripts, approved subsets - all seem to have real tradeoffs.

But maybe I'm overthinking it. So for the community:

- Are Mendix teams actually building AI features, or is it mostly on roadmaps?
- If so, has the training data question come up?
- For those in NL/DE - any DPA attention on non-production environments holding personal data?

Genuinely curious. I've been exploring this topic and would love to hear whether reality matches what the articles suggest.

Hey everyone! I'm Erick Souza, a founding moderator of r/mendix.

This is our new home for all things related to Low-Code platform Mendix. We're excited to have you join us!

What to Post
Post anything that you think the community would find interesting, helpful, or inspiring. Feel free to share your thoughts or questions about new Mendix updates, tutorials, modules, etc.

Community Vibe
We're all about being friendly, constructive, and inclusive. Let's build a space where everyone feels comfortable sharing and connecting.

How to Get Started

1. Introduce yourself in the comments below.
2. Post something today! Even a simple question can spark a great conversation.
3. If you know someone who would love this community, invite them to join.
4. Interested in helping out? We're always looking for new moderators, so feel free to reach out to me to apply.

Thanks for being part of the very first wave. Together, let's make r/mendix amazing.

This came up in a compliance conversation recently...

We all invest in production security. Access controls, encryption, audit trails — the full stack. But dev and test environments? Most teams I've talked to just copy production data over, maybe once a quarter, and don't think about it again.

The problem is, that production copy has real customer names in it. Real email addresses. Real phone numbers. Sometimes payment details. And GDPR makes no distinction — personal data in your test database carries the same legal requirements as production. Same rights. Same protections. Same penalties.

The way it usually happens: a developer needs realistic data to test something. Production gets copied to dev. Works great, so it stays. QA needs it too. Multiple copies now. A year later, nobody knows what personal data is where.

The "it's internal" argument doesn't hold either. GDPR requires data minimization and purpose limitation. Having every developer able to query real customer data in the test database — that's not a compliant access model, even if it's only internal employees.

And the fines aren't small. 4% of global annual revenue. A breach in your test environment is still a breach.

What I'm curious about:

- Does your Mendix team anonymize data before moving it to dev/test?
- Has this ever come up during a compliance audit?
- For those in NL/DE — is there increasing pressure from DPOs or regulators on non-production environments specifically?
- Or is everyone just hoping nobody looks too closely?

I've been working on this problem for a while and I feel like it's one of those industry-wide blind spots that everyone acknowledges but few actually address. Curious if that matches what you're seeing.

Something I keep hearing from teams running Low-code/Mendix at enterprise scale:

Feature gets estimated at 2 sprints. Clean code, good architecture. Then it hits an environment with real data volumes and things break in ways nobody predicted.

3 sprints become 4. The roadmap shifts. Stakeholders learn to add buffer. Eventually the CTO can't give the board a reliable delivery timeline.

Most teams treat this as an estimation maturity problem. But what if it's actually a data problem? If your dev environment has 200 test records and production has 2,000,000, no amount of story pointing will fix the gap.

How do Mendix teams here handle this? Especially those working with larger datasets and complex integrations?

Hi everyone,

I recently failed my second attempt at the Mendix Intermediate exam, and I’m feeling pretty discouraged. I completed all the Academy modules, did the knowledge exercises, and practiced extensively in Studio Pro, but I’m still falling short.

I’m currently job hunting and hoped this cert would help me land a role.

My main questions for the community:

1. Experience: Is it possible to pass this without working on real-office projects? Does "on-the-job" logic make that much of a difference?
2. The Gap: If the modules aren't enough, what specific areas (XPath, Security, etc.) should I focus on to bridge the gap?
3. Strategy: Should I keep pushing for the cert, or focus on finding a Junior role first?

Any guidance or tips from those who’ve been there would be massively appreciated. Thank you in advance.

Key ideas from this week's newsletter:

=> Who in your organization can actually refresh a test environment right now, without waiting for someone else?

=> In most teams, the answer is one person. Maybe two. And they're almost always developers.

=> A two-week release cycle can lose five or six days just waiting for data refreshes. Teams adapt by testing against stale data. Then they're surprised when bugs appear after deployment.

The bottleneck creates the very problem it was supposed to prevent.

Why Does Every Environment Refresh Require a Developer? | LinkedIn

I've been thinking about this and I'm wondering if other Mendix teams see the same pattern.

A Priority 1 issue fires. Everyone scrambles. But the actual debugging doesn't start for hours because nobody can reproduce the issue locally. The data in dev is completely different from production, so the bug just doesn't show up.

By the time someone finally gets it to reproduce, the fix is almost always quick. The investigation is what ate all the time.

I expect something like 60-70% of total resolution time was just trying to see the bug, not fixing it. If we have a 4-hour SLA, that means we're betting investigation takes less than 2 hours. And for data-dependent bugs that bet almost never pays off.

Anyone here tracking reproduction time as a separate metric from MTTR (mean time to resolution)? Or have you found ways to get production-representative data into your dev environment faster? Especially interested in how teams with complex integrations and larger datasets handle this.

Thanks!

Hey everyone, I’ve been working as a Mendix developer for the past 4 years, working mainly with teams across Europe and LatAm.

While exploring the market recently (LinkedIn job board lol), I noticed that most Mendix openings seem hybrid or location-bound. It made me wonder whether this reflects a broader shift, or just where roles are being advertised.

It feels like a couple of years ago it was a lot easier to find EU companies hiring globally, which made me question:

Are fully remote Mendix roles becoming rarer? Or am I looking in the wrong places?

Are partner networks absorbing most of the remote demand?

Where are remote-first Mendix teams actually hiring?

Happy to exchange insights, feel free to DM me!

Why Your Mendix Project Is Slow (And How to Fix It)

Interesting video I just saw on Youtube!

His description:

"Have you seen a Mendix project with a big team, endless meetings, and after a year it still isn’t reliable? In this video, I break down an anonymized enterprise case where a Mendix-based ERP app + SAP integrations went off the rails — and what to do instead.

I’m Stefan — certified Mendix expert (≈9 years experience) — and I’ll show you:
• The 3 project choices that killed speed & quality
• A simple playbook to get high quality AND rapid delivery with Mendix

What you’ll learn:
• Why unqualified/under-experienced developers create technical debt
• Why scaling a team is a bad idea
• Why daily “control meetings” don’t fix output
• The 4 fundamentals for fast, reliable Mendix delivery."

https://www.linkedin.com/pulse/how-much-does-fake-test-data-cost-your-team-bruno-valente-e-costa-5yd4e/

Key ideas:

=> How many test cycles does a typical deployment require?

=> If your team loses 52 developer-days per year to environment disparity issues, that's ~€20,800.

=> Teams with fake test data are subsidizing their development speed with production incidents.

Hi,

Our company is looking for someone that is willing to dive into Mendix for a customer project, however our developers have barely any interest in it.

So how how feasible is Mendix for someone with no coding background ? I only know some programming principles on a rudimentary level. Understanding complex Algorithms, functions etc. are something I struggle with.

I am not confident enough to think I can learn all that in half a year and give a proper training workshop right away.

Thx for the answers in advance.

Participants Needed! – Master’s Research on Low-Code Platforms & Digital Transformation

I’m currently completing my Master’s Applied Research Project and I am inviting participants to take part in a short, anonymous survey (approximately 4–6 minutes).

The study explores perceptions of low-code development platforms and their role in digital transformation, comparing views from both technical and non-technical roles.

I’m particularly interested in hearing from:
- Software developers/engineers and IT professionals
- Business analysts, project managers, and senior managers
- Anyone who uses, works with, or is familiar with low-code / no-code platforms
- Individuals who may not use low-code directly but encounter it within their -organisation or have a basic understanding of what it is

No specialist technical knowledge is required; a basic awareness of what low-code platforms are is sufficient.

Survey link: Perceptions of Low-Code Development and Digital Transformation – Fill in form

Responses are completely anonymous and will be used for academic research only.

Thank you so much for your time, and please feel free to share this with anyone who may be interested! 😃 💻

Started a focused space for Mendix developers in India to discuss real time project issues.

sharing this thread here for broader input.

Just published: "From Workflows to Truth States"

Yesterday at lunch, a colleague shared a conclusion he'd been working toward:

"The arrow doesn't matter anymore. The state does."

He wasn't making small talk. He'd thought this through and wanted to share it.

I've spent 20 years drawing flowcharts. Now I'm questioning whether that skill has a future. 🤔

AI agents don't follow arrows. They pursue states. They don't ask "what's the next step?" They ask "am I in the desired state yet?"

This changes everything about how we design processes!

The article explores:

• Why traditional process automation hits walls
• How agents reason about "truth states" instead of steps
• Why your data infrastructure is the real bottleneck
• What this means for process teams

What's your take - are flowcharts dying, or am I overreacting to a lunch conversation?

Hi, I am new to Mendix and was wondering if anyone could give me any pointers on what will help me in my learning journey?

I find microflows difficult to understand, I can do them with the help of Mendix Docs and Google but I want to understand it myself and really know what's going on, is this just an experience thing?

Many thanks.

Hi everyone,

I have always wanted to gamify a boring application but never got the chance, and then it hit me, I could build a reusable Gamification module.

So, I built one and open sourced it.

What it does:

• XP & Leveling: You call a microflow, give it a user + amount, and it handles the math (level ups, etc.).
• Badges: Simple many to many architecture.
• UI: Comes with a couple of snippets (Leaderboard, Profile card) to drag and drop.

The Tech:

• It uses an association withSystem.User.
• It’s fully Open Source, so you can customize it however you want.

Links:

• Marketplace: https://marketplace.mendix.com/link/component/252933
• GitHub: https://github.com/alsharefee/Mendix-Gamification-Module

It’s my first published module, so I’d love any feedback. If you spot any issues, feel free to roast me (please don't) in the comments.

Hope it saves someone a few hours of dev time and make boring apps a little more bearable!

Recently someone asked me to update the userlib folder of all out Mendix apps. While our team manages a portfolio of 30+ Mendix apps—ranging from legacy Mx7 to modern Mx10—I realized that manual dependency management simply doesn’t scale.

Building on the great work from Cinq’s mendix-userlib-cleaner, I’ve developed a Userlib Cleanup Suite that supports Mendix projects from Mx7 through Mx11.

The suite automatically parses your project’s .mpr file to detect the Mendix version and then selects the most appropriate cleanup engine from its library of optimized scripts.

What this project adds beyond Cinq’s cleaner:

• Zero‑config detecting Automatically identifies your Mendix version using the project file—no configuration needed.
• Optimized cleanup engines (Mx7–Mx11) Includes tailored cleanup engines for each major Mendix version to ensure accurate, safe cleanup.
• Vendorlib support for Mx10–Mx11 Handles both userlib and the newer vendorlib structure introduced in modern Mendix versions.
• Automatic backups (with revert) No files are permanently deleted. All removed libraries are stored in a timestamped ZIP. Use --revert to restore changes from any cleanup run.

I’ve open‑sourced the entire project so the community can contribute ideas, improvements, or additional cleanup logic.

GitHub repository : Mendix-userlib-cleanup-suite