Rapid App Development
Nolan Ramsey
Outdated Technology: When to Build New vs ...

All IT leaders face challenges of outdated technology. Sometimes it’s time to build or buy a new application. But nowadays, it might make more sense to refresh the new old one. I explore those challenges and provide real client examples where I’ve used low code to help in both cases.

Outdated Technology: When to Build New vs Refresh the Old
Rapid App Development
Nolan Ramsey
Does SAP's acquisition of No-Code Developer ...

I share my thoughts on the recent acquisition of AppGyver by SAP and how that does or doesn’t relate to their SOLEX partner, Mendix.

Does SAP's acquisition of No-Code Developer AppGyver hurt their SOLEX partner Siemens Mendix?
Rapid App Development
Nolan Ramsey
Is Rapid App Development essential in the ...

The world is battling a war on two fronts: our health is threatened by COVID-19 and our economies have slowed and even stopped in certain sectors. As an App Developer, does my work really matter in such times?

Is Rapid App Development essential in the current climate?
Rapid App Development
Nolan Ramsey
What makes a Great Rapid App Developer?

After years of delivering, leading, and coaching leaders in Rapid App Development, I give you my perspective on what skills and profile it takes to be a ‘Great’ RAD Maker.

What makes a Great Rapid App Developer?
Mendix
Nolan Ramsey
Extending SAP: Fiori or Mendix Revisited

It’s been 1 year since I first wrote the post, “Extending SAP: Fiori or Mendix?” and a lot has changed. Because of the changes, this older post has gotten a lot of renewed interest so I thought I would take a look at my opinions from a year ago and see if they differ. If you haven’t already, please refer to the original article to have context for this one.

IT should be an expert “SWAT” team with precise skills to tackle the toughest app challenges, not a bottleneck to solving business problems.

Extending SAP: Fiori or Mendix Revisited

WSDL

Handling CDATA in a WSDL response with Mendix

Handling CDATA in a WSDL response with Mendix

This past week while working on a module in Mendix that required the consumption of a web service, I ran into the situation where the response was CDATA. I hadn’t encountered that before so I did a bit of research. Apparently this is used to extend and change API’s without changing the structure of the WSDL. This makes a lot of sense since once an API is created there can be 1 to n number of other systems using it and any change will require all of the end users to change their work. If you’ve ever encountered this or want to understand how to deal with parsing CDATA in Mendix, read on!