jump to navigation

Friday Philosophy – Publishing rather than Presenting December 18, 2015

Posted by mwidlake in Oracle Scene, publications, writing.
Tags: , ,
6 comments

Have you ever considered writing articles on Oracle subjects? Unlike presenting, there is no need to stand up in front of a scary crowd, remember what it was you wanted to say and risk someone calling you out from the crowd & accusing you of being an idiot {NB people worry a lot about that last one, but I have only seen it happen once – and no one much liked the person doing the calling}. Presenting is not for everyone. But it is not the only way to engage with people or share your knowledge. When you write an article you get to take your time, ensure you are saying what you want to say and you can correct it over time. You can also ask friends to check it over for glaring mistakes or badly written prose before you submit it. I do.

Oracle Scene, Autumn/Winter 2015

Oracle Scene, Autumn/Winter 2015

I can’t say I am an expert, I’ve only written a few articles for publication myself, but I have also been helping out with Oracle Scene in my role as deputy editor. I’ve reviewed a lot of material and helped one or two people update their articles. But there are some ways in which I think publishing is a superior way of communicating when compared to presenting. As I mentioned before, you get more time to “deliver” the material. When you present you will have prepared your slides or demonstrations and, I’d hope, you have practiced it. But the actual delivery is “Bang!” you’re up. What you say, you say, what you don’t is not going to be said – unless it is on the slides (which people may or may not read). With an article, what you actually put out there is something you can check and hone until you are happy. Or you get too close to the submission time to mess about any more…

A published article is there and it will stay there. Presenting is gone as soon as you finish it (unless it has been recorded – and my experience is that recorded presentations do not get watched that often). Many more people are likely to see an article than see you present, especially if you get it into something like Oracle Magazine… Or “Hello”, but that is pretty unlikely for an article about HR apps in the Cloud. That persistence is also a bit of a drawback I find, as I am even more concerned about getting it right. I don’t want to have something that people can constantly point at and say “Hey, that Widlake guy! He actually still USES the Buffer Cache Hit Ratio!”. But it drives me to produce something of a slightly better quality, I feel, than when I present or blog.

I obviously blog quite a bit but I hesitate to say that a blog is quite the same as having something published. When I blog it is me having my say to an audience that chooses to come by and look. If I mess up, you all know who messed up. If I publish, I have to produce something good enough for someone else to say “yeah, that is good enough to be in my publication”. And if I have messed up, I’ve messed up a bit of their publication. I can actually modify or remove anything I blog, it is under my control. However, when I do an article in a magazine, it is fixed once it has passed the copy edit check. So blogs are different, they are “softer”. I would say, though, that web sites that give information in a more formal way, like the wonderful Oracle Base by Tim Hall or fantastic oracle-developer by Adrian Billington are more like published material. A kind of half-way-house.

Where a published article wins out over a blog is in audience reach. I know that lots of people who would never visit my blog will see it, maybe people who will remember the great article I did and even recognise my name. You never know, one day it might help me land a piece of work. A published article will also be read by people outside of my sphere, some people who are reading it for the Apps content might look over my article, especially one that is an introduction to a subject.

Another of the great things about a published article is it can be referenced back to or, if it is a printed publication, there on your desk to look at as you try things out on the computer. We all tend to have larger computer screens now and even multiple ones {I would struggle to go back to a single screen} and use online material, but nothing beats having a physical copy to read and move about the desk. It leaves the computer screens free for everything else and you can take the magazine or printout around with you when you don’t want to have a laptop or tablet with you.

I guess I am more proud of my publications in Oracle Scene than my blogs. My mum even paid a tiny bit of interest in me having an article in a “real” publication.

os57cover

And this leads me on to the real purpose of this piece. I’d encourage you to submit articles to Oracle Scene. The call for articles for edition 59, to be published in Spring 2016, closes on 11th January. You can find the editorial calendar here which tells you about the dates for the next and future publications. If you want an excuse to get away from the relatives this Christmas, why not write and submit an article? We are always looking for good articles and series of articles. Check out the current edition online {the current edition is free to anyone to view online} to see what sort of things we cover, which is all aspects of the Oracle tech and Oracle apps. We are particularly keen to get more Apps articles as they are currently under-represented, but we of course are also interested in technical pieces.

We are moving to publishing Oracle Scene four times a year and with more content each copy. With “Oracle Magazine” going digital-only, I think Oracle Scene is now the only physically published magazine on Oracle technology. Oracle’s “Profit” magazine is still available in print but it is mainly focused on the business side of using Oracle solutions. When I was in the US for OOW15 I mentioned Oracle Scene to a few people and that it was still a physical publication, as well as available digitally, and that seemed to be of interest to most of them. Physical copies are available at all UKOUG events and are placed in Oracle Offices. If you have ever sat in reception waiting to see someone in Oracle, there were probably a few copies near you! You may well have read some of it, whilst waiting for Larry to see you.

I’ll finish with a few words on what we look for in articles {I may well do a longer piece on this at a later date, especially if any of you tell me you would like to see it}. We avoid sales pieces. If you work for “United Mega Corp” and every sentence has “United Mega Corp” in it or you are just trying to sell United Mega Corp’s sales portal system, then you are unlikely to get your article accepted – you can pay for advertising space for that. However if you work for “Incredible IT Systems” and write a piece on using pluggable database and mention “Incredible IT Systems” once or twice, or that you have experience in the field you can offer to customers, all is good. Other than that, we simply want well-written articles that will help people use a feature of Oracle, better understand some aspect of their Apps offerings or allow a compare & contrast across possible solutions. Basically, we want to publish things that UKOUG members and the wider Oracle community want to read.

Go on, think about it. Give it a go. And if you actually want to spend time with the relatives over Christmas, write a piece for one of the editions later in the year.

My First Published Article April 21, 2015

Posted by mwidlake in Presenting, publications, UKOUG.
Tags: , , ,
8 comments

I’ve been blogging now for almost 6 years and presenting at conferences for… 12 years (really? Good grief!). I’ve even written and delivered several courses, ranging from 1 day to 3 days in length. However, up until now I’ve never been what I would term published – ie managed to persuade another organisation or person to publish something I have written.

That changed a few days ago when the latest UKOUG “Oracle Scene” magazine came out, which included the first of a small series of articles I am doing on how the Oracle RDMBS works – the processes and activities that underlie the core RDBMS engine. It’s based on my “how Oracle works in under an hour” presentation where I give the audience an overview of things like the redo mechanism, what a commit *is*, how data is moved into and out of memory and which parts of memory it resides in, how a point-in-time view is maintained… things like that. Many people don’t really know any of this stuff, even skilled and experienced developers and DBAs, as you can get by without knowing it. But understanding the core architecture makes a lot of how oracle works make more sense.

The below is a screen shot of the title and first paragraph, but you can use the link above to see the whole article.

Title and first paragraph of the article

Title and first paragraph of the article

I’m not sure why it has taken me so long to publish something other than via my blog and presentations. I know part of it is the fear of putting something out there that is wrong or misleading. If it is on my blog, heck it’s only a blog and I stick to things I give test cases for or my thoughts and opinions (which are intrinsically open to interpretation). My presentations are certainly put “out there” but again I of course try to ensure what I say I can back up. I think the key thing is that in both cases it is very obvious who you can blame if it turns out I have made a mistake. Me.

But when something is going to be published I feel that (a) it might be taken more seriously so I need to make extra sure it is correct and (b) if I get something wrong or, more concerning, mislead anyone then the people publishing the article could also be put in a poor light. I think that is what has made me wary.

The irony is that the first thing I get published, I know that there are some inaccuracies in there! The article (and also the presentation it is derived from) is an introduction to a lot of technology and I have to simplify things and ignore many exceptions to keep it small and easy to digest. It’s how it works 90% of the time and you need to know that so you will better understand the exceptions and finer detail I don’t have time to tell you about. For the physical presentation I spend a minute at the top of the talk saying I have simplified, occasionally lied, but the overall principles and feel is correct. I had to drop that bit out of the article as, well, it took a lot of words to explain that and the article was long enough already!

Another reason NOT to publish is it takes a lot of time and effort to prepare the material in a way that is polished enough to be printed and I know from friends that the actual financial payback for eg writing a book is very, very, very poor. No one I know makes enough from royalties on technical books to make the effort worth while {though there are other less tangible benefits}. But I have time at present so I can afford to do these things.  If you want to make money out of publishing, write about a load of elves, an often-wimpy trainee wizard or something with sex in. Or all three together.

I did nearly put a technical book together about 10, 12 years ago, called “The Little Book of Very Large Databases” as it was something I knew a lot about but the issues were rarely discussed publicly – most VLDBS were (and are) run by financial organisation or “defence” {why can’t they be honest and refer to themselves as “Killing & Spying”} and they don’t talk. O’Reilly was doing several small, A6 booklet-type-books at the time that it would have suited. I can’t do it now, I know nothing about Cloud and some of the 12C features that would help with VLDBS, so I missed the boat. I regret not giving it a go. However, there is a possibility I might be involved in a book sometime in the future.

I have to thank Brendan Tierney for hassling me into doing this series of articles. I’m not being derogatory when I say he hassled me, he did, but Brendan did so in a very nice way and also gave me the odd toe in the backside when I needed it.

I also have to thank Jonathan Lewis. If this article had been a book he would have got a huge mention for being my technical reviewer. He was good enough to look over the article and let me know a couple of things he felt I had over simplified, some things with the flow and also something I had simply got wrong. You know that bit in books about “thanks to Dave for assisting but all mistakes are mine”. Well, I always thought it was a bit overly… defensive? Well now I don’t.

All mistakes are mine. I want no blame falling on the people who helped me!

I still can't take my Bio too seriously

I still can’t take my Bio too seriously