When I reach out and ask the community what they would like me to share, I primarily get asked for Best Practices. For a time I have rejected the idea of sharing those in too much detail as I consider Best Practices to be part of the value proposition of a consultant practice. It's taken years to forge and sharpen those practices and they therefore have value. We continue to challenge those and update as new scenarios, tools, and skills evolve over time. But I continued to think about this and have had a change of opinion.
When used correctly, Calculated Attributes enhance the apps by handling basic calculations at run time; Used poorly and they will damage your app performance. In this use case I walk through a sample app based on a real-world problem to explore the performance issues and a couple of strategies to improve performance to the correct standard. I appreciate any feedback and hope this helps some Mendix devs!
How easily could a Mendix Developer transfer the skills of Rapid App Development to another tool in Gartner’s Magic Quadrant for hpaPaaS? I look at OutSystems to help answer that question.
I tried something new this time: Video! Rather than write this all out, I decided to record a video to talk about a best practice. I’m very interested in your feedback on whether you prefer written to video format and if you found my shared best practices to be useful or thought provoking. I’ll do more or less of the video style based on your inputs here or on the video itself. Thanks!
I've received a lot of questions about my thoughts on the recent acquisition. I've spoken to a number of individuals at Mendix to get their thoughts, read CEO Derek Roos and CTO Johan den Haan blog posts, and discussed internally with some of my colleagues at EPI-USE and other Mendix MVP's. My perspective seems to be a bit different than the majority. Now that the dust has settled a bit I thought I would share.