APEX – Scratching the itch #JoelKallmanDay

My biggest regret upon retirement in 2015 was not having had the time to study APEX and promote it in my organisation.

Fortunately, I had a daughter in medical school in Paris. She was in the Commission that managed the process of assigning internships to students every trimester. I used the “Hungarian Algorithm” to optimise the students’ preferences and achieve the greatest average satisfaction. With the help of Richard Martens, I then developed an APEX application to accept the preferences and to enable an administrator to run the process directly without my intervention.

Students on average got their fifth choice out of about 150 possibilities!

Since then I have developed a new version of this application after the merger of two medical schools, a similar application for the medical school in Nancy, and two COVID-related applications.

By this time, I should have enough experience to temper my enthusiasm for APEX: I should be starting the downward slope in the Hype Cycle from “inflated expectations” to the “trough of disillusionment”. No way! APEX was always there for me, either meeting my need out of the box or allowing me to tinker with a bit of javascript. Not only that, but slightly more difficult tasks kept getting easier with each version as new functions kept piling up.

Sometimes the feature I needed was hidden away where I could not find it, but online searches generally led me to some member of the APEX community who had already solved my problem. Often enough, that feature was simply there in the first spot I looked.

I know I have barely scratched the surface of all that APEX has to offer, but I was able to scratch my itch,
and boy did it feel good!

With my thanks to the entire team and especially Mr. Kallman,

Stew Ashton