After 14 and a half years at Intec, I'm moving on to pastures new. I've learned a lot and developed in ways that were never envisaged by anyone when I started at Intec. I'm very fortunate to have had a company that backed me, and I think we've both benefited greatly. But I've always sought to embrace opportunities and accept responsibilities throughout my career. And now is no different.
Over the years I've spent a lot of time supporting applications. I would like to think I'm pretty effective at it. So I thought it was the right time to share my approaches. The key is a systematic, logical approach to identify the cause - or causes.
Over the years I've done a lot of development on a variety of platforms. Error management is something developers either bake in from the start, add in later, or never get round to! It seems a good time to review my experiences and my philosophy.
tl;dr - it varies.
People discussing Domino application development have been using a new term since early this year - "mid code". This has become necessary because of the evolution of Domino development since Domino V10.
Recently I've been diving back into running Java outside of the Domino HTTP stack, picking up some work I did quite a few years ago playing with Vert.x and Domino based on Stephan Wissel's blog series on Vert.x and Domino. Quite a few things have happened since I was last working on the project, not least the laptop I had at the time got rebuilt, I have got a new laptop, several version of Eclipse have been released and XPages SDK has been deployed to the Eclipse Marketplace (thanks Jesse Gallagher).