In the late 1990s there was a temp who had left university not long before, with an MA in Ancient Greek Literature and a PhD to write up. He was applying for academic positions but uncertain where his long-term future applied. He started at a company which used Lotus Notes for a CRM planning events and working as office support for remote staff who worked on local replicas. Of course replication conflicts occurred and once he understood from IT what they meant, liking a clean database, he took the time to work with others where appropriate to help consolidate the conflicts and manage the data. When the person left who did weekly exports and manipulations of data to send to a third party, he embraced the opportunity to take over. When IT decided to modernise the application, the developer asked if he would be interested in shadow developing it. So he read the book, learned about Domino development and helped out partly in his spare time. He helped write the documentation and joined in the training for staff on the new version.

Opportunities came and went and he eventually joined IT as a developer too. When the developer was absent long term, he temporarily helped lead the development team and took on support and development of other applications. The investment in his learning enabled the company to cope with increased workload. His first application, using drag and drop, formula language only and some garish colours, nonetheless persisted and long outlived his time with the company. He was not technical, he was not a developer by education, he was not employed as a manager, but he was willing to learn and willing to grow.

Years later he became a speaker, blogger, author, considered by many an expert, IBM Champion and eventually a lifetime Champion. Yes, I am that person.

And that’s why low code is important. That’s why the citizen developer is important. The citizen developer who is eager and shows an aptitude can become a mid-code developer. And this is another route for growing the platform, for growing the developer base and for augmenting small development teams – even of one – in small organisations. And for rapid development the citizen developer brings something more – end user focus and business knowledge. The citizen developer is a user who codes, someone whose work may not even be 100% computer-based and certainly not someone who is a software expert. There is a reason there are Domino developers and not programmers. We don’t just code and with rapid development we shouldn’t. Our business knowledge helps build what a user really needs for what the business really wants. Pro code skills can be learned, particularly in the era of YouTube, just as business knowledge can be learned.

This is why for low code I’m looking through the eyes of both that young person eager to help out his fellow workers as well as the IT expert I am now. I’m not thinking primarily about IT control, I’m not thinking primarily about massive organisations, I’m not thinking primarily about what Domino development means today. I’m thinking about the business users who squeeze this alongside their day job, for whom this needs to be easy and fun. Some of them will only be interested in that current career, but some of them – many of them if we do this right – may augment and increase their development teams and with the right investment fly higher than they ever thought possible and bring talent from backgrounds we’re not expecting.

7 thoughts on “Why Low Code Resonates”

  1. Ah, Mr. Paul. That’s where you come from; the citizen developer. I really like the perspective you bring in. I got into Lotus Notes in the early 90’s around release 3 when there was no Lotusscript, just @Formulas.

    During that period, I meet many “citizen developers” (doctors, engineers and other professionals) that knew nothing about C++, Java and VBscript. BUT they knew about the business they were in. They solved many problems by creating and sharing Lotus Notes databases with colleagues.

    When release 4 arrived, “real developers” jump into Lotusscript and took control of the Domino platform. And it just took months for many “citizen” to leave the platform.

    The “citizen developer” play a big part in solving real business problems. With tools made for him, he (she) can achieve a lot. If that is the path that HCL takes with Domino, it will be interesting …

    1. Thanks for your comment. I wonder what the community can do to enable to path for those developers. The great thing is that this community, if we embrace these people, can do that in a way few other communities can.

  2. “Low Code” is definitely on all the buzzword bingo cards right now. But the “low code” products I’ve seen from other companies leave a lot to be desired.

    Either the capabilities are too limited (especially in the areas of who can edit what) or a product pretends to be a “drag and drop, no code/low code” offering, the amount of expertise required to drag and drop the right parts isn’t for the average power user.

    My hope is that future Domino development hits the right mixture of “expertise needed” vs. “useful result” that Notes client development had back in 3.x days.

    1. I think the challenge is that trying to be too much at once will mean not doing anything soon enough. The skill will be supporting all relevant people in a way that doesn’t overwhelm each. The advantage is that many at HCL and in the community have been through that journey, but it still takes a huge amount of skill to manage it effectively. Domino Designer has been through some of that with the different “perspectives”.The real skill is enabling the functionality for the person’s current skill level, while progressively displaying skills to take them to the next level. Or maybe some kind of training / documentation will best enable that. To be honest, I’m not sure yet. But this community definitely has the skills.

      1. “The real skill is enabling the functionality for the person’s current skill level, while progressively displaying skills to take them to the next level.”

        I think that HCL have a good idea about this. I’m sure you have seen their demo of DQL Explorer (

        Just under the “Run Query” button, there was a little switch named “Developer Options”. For me, that’s the way to go.

  3. Stefano Pogliani

    This post remembers me a wonderful yet small book i read 13 yrs ago. « Igniting the Phoenix » was the title !
    It is a pleasure reading this clear and so well written post.
    I fully agree with what you wrote Paul

    1. I’ve not come across that before, but the message “Problems cannot be solved at the same level of awareness that created them” sounds very apt. It reminds me of a comment from a Lotusphere a few years ago, “sending the elevator back down”. To help those who were at a level we once were, we need to remember the challenges we had at that time and think of what would have helped us overcome them quicker than we did. That again is something which this community is better equipped to achieve than many.

Leave a Comment

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Scroll to Top