Hello Readers … that is, if I still have any readers out left out there. I have few topics that have been on my mind lately and they will become posts in the near future. After all, this blog does have a purpose other than re-broadcasting my favorite xkcd's.
First order of business is to let you know what I've been up to lately. As you may have already learned from other blogs and adverts, there is a new book coming soon: Oracle Pro SQL. Karen Morton is the lead author and Kerry Osbourne, RS, Jared Still and I all contributed a couple of chapters to the effort. I have to say this is going to be an excellent book and the primary reason for that is Karen Morton. I don't intend to detract from the other authors at all. I've previewed many of the chapters and there is great content across the board but Karen is one of the top 5 Oracle educators out there. (and I'm thinking Jonathan Lewis, Cary Millsap, Tom Kyte level, plus I'm leaving one 'get out of jail free' card just in case I forgot someone important.) Karen has a talent for taking a complex concept and explaining it in a way that makes is immediately understandable and accessible to her audience. What is even more impressive is that she can do this in her writing as well, and it's actually enjoyable to read her work. And while enjoyable reading may be common on the best seller list, but let's face the facts, it's exceptionally rare in technical book section.
Next on the list is that I gave two presentations at UKOUG this year:
The topics are:
'On the Importance of a Good Data Model'
As you might have guessed, this topic resulted from my blog previous posts lamenting the lack of data modeling in Agile environments, and the very insightful comments from several readers. In the presentation, I'll talk about why the data model (data-at-rest version) is overlooked many development projects and why skipping it is a fatal flaw in any project. I'll also talk a bit about what I really like about Agile methods because - believe it or not - I do think Agile is a very good thing.
'Using Instrumentation to Ensure Performance'
One of the chapters I contributed to Karen's book was on Testing and Quality. As part of that chapter, I cover instrumenting your code and this second session will focus on how to instrument your code and why it's a good thing to do. I'll include some of the specific code changes I've made, the data points I choose to store and how that data can be used in conjunction with Oracle's performance tool to troubleshoot problems. I'll also show how you can use that instrumentation to measure performance and capacity testing before the code is released so you can fix any issues before the customer bumps into them.
If you missed the presentations at UKOUG, I will be giving these same presentations at RMOUG in February. With me, catching a later showing tends to pay off as I modify the presentation after each I give it to fix anything that wasn't clear, or to address questions from attendees. Unfortunately, about the time I get it right, I get bored with the slides and file them away. Character flaw, I know but I am working on it :)
I'm still in Birmingham, enjoying the snow and hoping that my train to Manchester and the subsequent flight home will be uneventful. The conference was excellent as always and it was great to see so many friends again. I took my annual walk through the Christmas Market today through a steady snowfall and it was absolutely lovely. I really love the UK and would be perfectly happy to just stay here :)
cheers everyone