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'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.
“With SAP tools like Fiori and UI5, why would I need Mendix?”
As a practitioner who directs our architecture and development of Mendix applications alongside SAP developers, I get asked this question a lot. Rapid Application Development (RAD) tools like Mendix are on the rise because as businesses begin their journey into digital transformation, they realize that the agility necessary to respond to rapidly changing competition and value perceptions require focused teams that combine business leadership and IT to design and deploy solutions just as rapidly. Waiting for a waterfall, stack-developed project to get scoped and developed will typically miss the mark, come out behind the curve of the transformation, and be dead in the water by the time it hits the market or the business.
Most of us who have delivered more than one app know that the majority of these turn into applications. That transition from ‘app’ to ‘application’ brings new challenges from the initial prototype and deliver process. Adding all of those extra features requires us to slow down our velocity a bit to test all of the new inter-connectivity. In this post I want to share with you my perspectives on what it means to transition an ‘app’ into an ‘application’.
One thing that is inevitable in software development is that you will create bugs in your software. The question becomes how and when you deploy fixes for them. Each client has differing levels of change control processes that need to be considered when dealing with these fixes. You want to eradicate the bugs as quickly as possible, particularly if they are preventing the end users from completing their work, but you don't want to affect current main line development. I'll give you a process I use that seems to be working best after much trial and error.