Posts tagged with: Jython

With the coming of automation scripts, there was a possibility for a non-technical person to write code in Maximo and see the results immediately. Everybody could change something that was not possible with configuration and make it work. The thing that people sometimes forget is that when you start to write code, you need to take care of it as code. You can’t say, I’m writing code but I’m not doing software engineering stuff. It doesn’t work like that. There are hidden performance traps in automation scripts. You write code and you don’t understand why, but the performance is really slow. In the next few series I want to share my experience as a software engineer and tell you about small technical choices that can have a direct impact on performance and user experience.

Every hour of Maximo consultancy counts. Let’s be honest — nobody wants to waste time and money on preventable issues. So let me share a powerful tip I learned while working in one of the top software engineering teams at Philips — a simple practice that can save your Maximo team hours of frustration and significantly speed up issue resolution.