All of us at GroupWave have years of experience with HCL Domino, so we know the platform inside out. But what happens when you introduce this technology to a new generation of developers?
To get a fresh perspective, we asked our interns Pieter-Jan Geelen and Timo Sleeckx for their unfiltered thoughts on the platform. Let’s see what surprised them, what stood out positively, and where there is room for improvement.
“Domino builds security deeply into every part of the system. Many modern tools could learn from the way Domino manages such a complex aspect.”
First impressions: expectations vs. reality
Before their first day, Pieter-Jan and Timo searched online for LotusScript. “We mainly wanted to know what it is and whether we would be able to read and understand it,” they recall.
They also looked up general information about Domino to get a basic idea of what they were dealing with. This led to some misconceptions. “We expected Domino to be more of an environment than a platform,” Pieter-Jan notes. “We thought it was a place where applications are deployed, rather than primarily developed.”
When they heard it described as an enterprise platform from the nineties, they admit they felt some hesitation. “We felt a bit of stress and anxiety about having to adapt to a completely new environment,” Timo explains. “We thought it might be outdated and not aligned with modern application development standards.”
First week: unfamiliar, but not difficult
During their first week with us, Pieter-Jan and Timo needed time to adjust. Modern tools usually rely on open text environments, but Domino’s Administrator and Designer tools take another approach. There are plenty of buttons, nested tabs, and structured menus, and this took some getting used to along with the differences in syntax.
But that feeling didn’t last long: things clicked when they began programming with LotusScript. And according to the interns, the platform is not inherently difficult. “Once we started using the tools ourselves, things gradually began to make sense,” Pieter-Jan says. They just had to learn the specific layout and figure out which buttons actually mattered.
Architecture and modern frameworks
When we asked Timo and Pieter-Jan about JavaScript, they pointed out that they never really used it in the Domino context. “It’s technically possible, but superseded by other options like the Formula language and LotusScript,” Timo points out. “However, we did use TypeScript for almost all of our frontend work.”
This contrast highlighted a clear difference in architecture. “We noticed that modern tools like React focus on developer freedom and modularity,” Pieter-Jan says. Domino operates differently. “It feels more structured and operates as an all-in-one environment.” They tried bringing in some other tools, but these kinds of direct integrations weren’t always as straightforward as they had hoped.
Security and stability
What about performance? The students experienced a few stability hiccups with their specific development server during the testing phase. But when it came to data protection, the platform completely blew them away.
“We were really impressed by the security model,” Pieter-Jan emphasises. “Domino builds security deeply into every part of the system, so users and roles control everything from data retrieval to deletion from a central interface. Many modern tools could learn from the way Domino manages such a complex aspect.”
The final verdict
So, what’s the final score? Pieter-Jan and Timo give Domino a solid 7.5 out of 10.
“Most points were lost due to personal preference, as we are used to very different tools and platforms,” they admit. But Domino earned bonus points because it becomes quite easy to use after you learn its quirks.
Would they use it again on a real project? Yes, but with a strategic approach to get the best of both worlds. “We would ideally combine it with modern tools,” they conclude. “We would use Domino for security and database management and keep most of the business logic in another backend, such as Java or C#.”
For any new developer starting with Domino, they offer one final piece of advice. “Start with the basics and focus on understanding the core tools and concepts first. From there, it becomes much easier to identify what is important.”
And there you have it: an honest assessment of Domino from people who are just starting out with it. We’re happy with the score, and we wish both of them the best of luck with the rest of their careers!
“We would use Domino for security and database management and keep most of the business logic in another backend, such as Java or C#.”
Ready to use Domino the way Pieter-Jan and Timo suggest?
Their conclusion hits exactly where Domino shines in 2026: a rock-solid, secure data layer underneath a modern stack. Java, C#, or React on the front end — Domino as the reliable backbone underneath. No vendor lock-in, full control over your data, and a security model that impresses even a new generation of developers.
At Groupwave, we’ve spent years helping Belgian organisations do exactly that: modernise their Domino platform, integrate it with the tools their teams already use, and get it ready for what’s next.
Curious what that could look like for your organisation? Contact us for a no-strings chat with our team.
