I’m on Notes in 9 again, with a “grab bag” of a couple of tools I’ve put together recently that may be of a varying degree of useful for other Domino + XPages developers. You don’t need these to do development, but for the right person, they may help with their development workflow.

If you read my blog for any of the Saga of Servlets series, then I hope that you’re excited I’m returning to the application I put together for it. This time, it’s as a conversation piece in regards to some of the build process modernization I engaged in recently, in order to unify the code base in its git repository.

This one might be slight departure from my usual, but those that have followed my blogging this past year will have noticed a bit more of a leaning towards DevOps in some of my posts. This echoes a lot of what I’ve been concluding as increasingly a necessary part of development.

Here’s a quick tip from an example case I ran into at the day job relatively recently. I had a situation in which, due to one reason or another, a section of code had disappeared from an application. I happened to know exactly which design element (file) it disappeared from and, while I could have done so, I didn’t feel like only restoring the code (from an old, known working version), I also wanted to know what commit in my git repository showed its removal.

Amongst several things lately, such as basement remodeling, configuring my new home NAS, and yard work, I’ve had a few interesting thoughts on my mind lately. In fact, I’ve started up a couple of interesting side projects. Before I’m ready to share those, I have to shout about something from the roof tops. Ready?