Category Show-N-Tell Thursday XPages
Notes and Domino application can be the new sexy and run beautifully on all sorts of devices big and small. So a whole cottage industry
(no insult intended) of offerings around Domino Application Modernization
Modernization always also means: browser and mobile enablement.
Expectations ran high, that a magic button would transform (pun intended) a code base organically grown over two decades into beautiful working responsive web 2.0 applications. But GIGO
stands firm and not all applications are created equal. Domino's (and LotusScript's) greatest strength, turned into a curse: being an incredible forgiving environment. Any clobbered together code would somehow still run and lots of applications truly deserve the label "contains Frankencode
There is a lot of technical debt
than needs to be paid.
The first thing I taught every developer in LotusScript, is to keep front- and backend separate and keep the business logic in script libraries that only contain back-end classes. Developers who followed these guidelines have a comparable easy time to web enable application.
But how to explain this problem to a business user (who probably saw some advertisement about automatic conversion to web, be it on IBM technology or a competitor)?
Tell them a story (if they are not interested at listening at any of that, there's a solution too
Here we go
You are supply specialist for natural resources exploration company and your current assignment is to get your geo engineers set up in a remote jungle location. So you have to source vehicles, build roads and establish a supply chain. Probably you get a bunch of those
(a living legent since 1948
), stock spare parts and ensure that you have diesel stations along the way.
Everything is fine - the road might be a little patchy
here and there
, but that's not a problem, you get you guys delivered and working. You even look good
This are your Notes client applications, delivering business value, robust, efficient and can deal with a lot of road deficiency (that would be code quality).
Your remote location becomes successful and suddenly the requirements change. People want to get there in style
(Browsers). Your gas stations will do, no problem here, but already the roads need to be a little less patchy
and your stock of spare parts and the mechanics trained on them are useless. That would be your front-end classes and the "mix-them-all-up" coding style that worked in the past.
If the "arrive-in-style" meme escalates further
(mobile devices) you need to build flawless roads (unless your oil has been found in Dallas
where proper roads supposedly exist).
An experienced supply planner might anticipate what is coming and while sending in the Unimogs already prepare the gravel foundation, so paving of the road for the fragile cars
is just a small step. Or nothing has been done for a while and the
road check comes back with a huge bill of material.
You get the gist, now go and tell your own story.