In other but related news, I've been (somewhat unwillingly) appointed our next Confluence administrator. This means I'll be given full control over the wiki (muhuhaha) , meaning in effect I'll be able to try out new plug-ins, manage spaces, bully people around, etc.
It also means I'll have to do upgrades, booring user adminstration, figure out funky stacktraces that are appearing in Confluence for some odd reason, fix the database, etc, etc.
The main reason I have volunteered to do this job is that no-one else wanted to do it, and I believe our Wiki is far too critical to leave in the hands of our IT service provider like our CTO would've had it. When are you people gonna understand that Windows is not meant for hosting?
Additionally, I'll hopefully learn alot about Linux, DNS stuff, routing, network, hosting java applications, databases and user management (with LDAP).
These things aren't always relevant in my daytime job, but sooner or later the software we produce will end up in the hands of IT techies who want the software to work, log and do error reporting in a certain way.
And when all boils down to it, Confluence is still a java web application that runs on Tomcat, which is very similar to the products I develop. Having been responsible for hosting Confluence will therefore make me a better software developer.
I've got lots of other things to blog about, but no time to do them right now. Subjects include:
- Finalizing the CMS requirements with its most important element: Extendability
- How I became a certified Scrum Master (and what I learned)
- The programming designer, the new breed of web developers