No Local Oracle User Group? Oh Well, Go to a Bar… April 28, 2015
Posted by mwidlake in Presenting, User Groups.Tags: Meeting, user group
3 comments
Is there no local Oracle user group in your area? Do you wish you could share experiences with like-minded people? Is there no opportunity to talk about the technology you work with? Do you feel you would benefit from expanding your network of friends and contacts? But without a local user group it’s really hard to do any of that! – At least face-to-face. And, let’s face it, meeting for real really does beat meeting on-line. I know, you are sad about it.
Well, go to a bar. Have a drink, it might make you feel better. Especially if you go with Dave in your team. Ask your friend across town along who also works with Oracle Tech. And maybe she could bring her friend who is an Oracle DBA too.
Well done! You now have an Oracle User Group!
It really is that simple to start a user group. You do not need an organisation, you do not need membership and you do not need presenters. You just need three of you and a place to meet. I might be saying a bar above (or, in England, it would be a local Pub, my good chap) but it can be a coffee house, a cafe, a wine bar, the local library maybe or anywhere you can meet easily and relax. Obviously increasing from 3 to 4 to 5 etc makes it all more interesting with more stories, tips and experiences to share.
I’m in a user group just like that, it’s called the LOB – London Oracle Beers. We started in around 2009, 2010. Initially it was myself, Neil Chandler and Doug Burns occasionally meeting for a pint or three (and later arguing about who started LOB). Soon Pete Scott was joining us, then Dawn, then Graham {what happened to Graham?} then Martin Bach… It got serious when I put together a mail list. We’ve been going ever since and although the regularity of the meetings fluctuates, as does the size of the group, it seems to keep going at between once a month to once every 3 months. Thinking about it, we are due a get-together.
How to Start a Small, Social User Group
There is one thing that IS needed for a user group like the above, and in fact for the others I am going to mention.
You need someone to regularly say “let’s meet”.
It does not need to be one person, it can be shared between several people. In the current LOB it is mostly myself that sends out a call but Neil does too. Anyone in the group can make the call and occasionally others do (Dawn, Pete) and some ask me to make the call on their behalf, which I do even if I can’t attend. But that’s really all you need, someone to make the call.
The other thing you need to do is, as a group, invite some others along. Not everyone you can think of, for a social user group let it grow at a steady, organic rate. People drop in and out of user groups so you need to constantly keep an eye on things and if the numbers drop, ask a few others. People’s lives and circumstances alter so they can’t come or they just decide they’ve had enough and that’s fine. For this sort of social-centric user group I would suggest you stick to inviting friends and friendly contacts and try not to let it get too large (A nice problem for a user group to have!)
So Just Do it! If you do not have a local user group and you want one, be the person to ask a couple of friends and if there are 3 or more of you, make that call. And a month or two later, make the call again. The worst that will happen is that it won’t take off and, if it does not, you know you tried (and not many people will know you failed 🙂 ). I’d honestly be surprised if it does not at least take off for a while.
The Presenting User Group
Another sort of user group is where you start off by wanting it to be a bit more structured, to have presentations involved. This does take more organisation: a location where you can present (it does not have to be the same place each time), someone to present and it helps if you have a sponsor. As having somewhere to speak may well involve renting a room and it’s nice if you can offer some drinks and snacks. You don’t need a lot of sponsorship (if any). Ask some local Oracle-centric firms, the worst they will say is “no” and the best they will say is “sure, here is enough money for some pizza and Rohan in the Dev team is happy to talk about Blargh at the first meeting”. But work out what you need (say rental on the room and enough for a couple of Samosas for everyone) and only ask for what you need. Your sponsor may well want to put up a banner or have someone say something but that is part of the deal.
I’m involved in two such user groups in the UK at the moment:
Oracle Midlands run by Mike Mckay-Dirden. They are about to have their 8th meeting (Follow the link <- over there), on the 19th May in their usual location in Aston, Birmingham. I managed to get to most of their first meetings, spoke at one and sadly missed the last couple due to timing clashes. Might be true for this next one too :-(. Mike does brilliantly on this, he got a local firm (or part of the firm) Red Stack Technology to sponsor him and he has the gall to ask Oracle Ace Directors and other known people to speak 🙂
Club Oracle London was started by Jonathan Lewis (I think prompted by the LOB and also what Mike was doing – but don’t blame Jonathan if I have my facts wrong) and is sponsored and run by e-DBA but with a very light touch. This will be their 4th or 5th meeting. I’m speaking at this one and I’ve been to all of them. Again, follow the link for more details and to register for the event on Thursday.
If you visit my blog often or follow me on Twitter you will have seen me promote these events. I’m very keen to support smaller, local user groups.
Again, it needs someone to Make The Call and also get at least the first speaker(s), but you can share the load for that. The other difference is that you probably want to spread the call a little wider. Tweet about it, use Facebook and all those other social media things. Tell all the people you know who might be interested and ask them to spread the word as you want a reasonable crowd for the speaker.
There is more to organising these more formal user groups but nothing that one determined person or a small group of fairly determined people cannot make happen.
Larger User Groups
The next step up are the large user groups where you have membership and paid-for events, like national, regional (or state in the US) user groups. You need a run up to create one of those! However, they are still user groups, they are all part of the “environment” of the total user community.
These user groups can still be created by a small number of people but doing so is a bigger task and I suggest you contact other people who are involved in such things and really plan what you want to achieve – it’s a topic beyond a single blog post like this. But it can be done and it can grow out of the two sorts of user group above.
I would like to highlight that starting your own local, small user group should be no barrier to being part of the large user groups. I attend, promote and present at the small user groups. Heck, you could say I run one with the LOB (along with other people). However, I am an active member of the UKOUG, deputy-chairing a Special Interest Group that meets 3 times a year and I’m involved in organising the content of UKOUG Tech15 (See the banner -> over there -> – at the time of writing the Call for Papers is open ). We can all live together.
Getting Speakers
If you want a speaker at your event (which you can have at the social sort of user group but you need to make sure the speaker is not expecting a projector and can’t user powerpoint!) then you can ask someone in your group to do it, you can do it yourself (we all have knowledge and experience to contribute) or you could try to get a speaker outside your group.
If you are trying to start up the more formal Presenting User Group then a known name will help draw people to your event. But there is the danger that not enough people will turn up for the speaker! You will worry about that. Well, don’t. Just be honest with the speaker about the numbers you expect and be realistic. In many ways I personally like smaller crowds and I know other speakers who do. I’d rather have 5 enthusiastic people than 50 indifferent ones.
Obviously, the more geographically local the speaker is the more likely they will say yes and asking the stellar stars is likely to get a “no” as they are simply too busy – but if they are Local-local, they may say yes! Remember, potential speakers have to earn a living so are not available at the drop of a hat and some only do conferences. Again, the worst you will get is a “no”.
I’ll make an offer – If you decide to start such a group in the UK and you need a presenter, let me know. I can’t promise but I’ll try to oblige. If you are further afield I’m afraid it is less likely I can help as I have to pay my own travel and expenses. But you never know, the odd jaunt over to Europe does happen.
Also, try looking up local Oracle ACEs and OakTable members. Again,they might say no, they might say yes but Oracle ACEs and OakTable members are generally inclined to help, it’s a large part of why we have those labels.
As the annoying advert says “Just Do It”
So in summary: If you want a user group and there is not one, maybe you can start one. If you want it to be a little more formal with presentations, look for a sponsor and ask some local Oracle Names if they would present.
Good Luck!
My First Published Article April 21, 2015
Posted by mwidlake in Presenting, publications, UKOUG.Tags: Blogging, Presenting, publishing, UKOUG
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.
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!
Tips on Submitting an Abstract to Conference April 17, 2015
Posted by mwidlake in conference, Tech15, UKOUG.Tags: Presenting, UKOUG, user group
3 comments
<.. The tech15 committee and my role
<…. Who plans the Tech15 content
The call for Papers for UKOUG Tech15 has gone out. This is how most of the content for a large conference is sourced, by asking the community to submit abstracts for consideration. With smaller conferences and user group meetings the organisers can often get enough talks by hassling asking people they know.
Firstly, I would encourage anyone who has considered talking at conference but never has, to submit an abstract. We could easily fill the whole event with known speakers but we don’t. We have a policy of having some New Blood at every conference. {If you are in the UK and want to try out presenting then a great way to do so is by presenting at a smaller user group meeting, like for example the next RAC/Database UKOUG SIG meeting on July 1st 🙂 – It’s a friendly, relaxed way to get into presenting. Get in touch with me if it appeals to you}.
You can click on this link to go to the submission page, but before you do…
When you submit an abstract for a conference, you are not actually at that point communicating with your potential audience. You are communicating with the handful of people who are tasked with going through all the submissions and selecting the papers. With the UKOUG conference you are also communicating with the volunteers who will judge abstracts. And we, the agenda planning committee, take those judging scores very seriously. It is a large part of how we attempt to ensure we select the talks on topics that people want to hear about, as well as the people who you want to hear talk.
So when you get to the field where you describe your proposed presentation (the abstract) I would suggest you don’t want to be “teasing the audience” at this point. The people who are judging and selecting the papers are seasoned conference attenders. A catchy title might get you noticed but if the abstract does not clearly state what your talk is about, what you intend to cover and who you expect your audience to be, it makes it less likely that your abstract will get selected.
Also, if you have looked at the call-for-papers page and associated notes and have seen that we are particularly interested in some area (eg “what you need to know about ….” for the database stream) and your paper is addressing it, it is worth making that a little bit obvious. The agenda planning day is hectic, we get tired and tetchy and our brains start to leak out of our ears. If your abstract is clear about what you are talking about, you are increasing your chances of selection.
In years gone by we have given the people the option to give two versions of your abstract – the one for judging and the one for promoting your talk (that is the one that gets put in the conference notes and your potential audience will read and decided if your talk is worth their attention). However, many people felt this was asking for the same information twice so we have reverted back to a single abstract this your. However, you can change your abstract text after your talk has been accepted {but note, we are wise to people trying to change the actual content of the talk later on – we LOOK at the changes!}. So sell your talk to the committee and judges now and worry about the catchy reference to your favorite movie afterwards.
I used to make my submission abstract humorous (well, in my eyes) but I don’t anymore, or at least I tone it down. If anything, I make the abstract factual and simple. As an example:
How Oracle Works in 50 Minutes
—————————————–
This is a high level but technical talk about the key processes that underlie the Oracle database. I describe what an instance is and how the server process is the gateway to the instance. I cover how the redo mechanism works and why it is critical, how data is moved into and out of memory, delayed block cleanout, what a commit IS, the importance of the undo tablespace and how a read consistent image is maintained for the user. The intended audience is new DBAs or developers who have never been taught how the database works and at the end of the talk they will understand how these key processes work.
OK, the description is a bit boring but you know exactly what my talk is going to be about and if it will fit in your conference.
So what happens when you click on the above link to submit an abstract? You will see the below front screen:
I would suggest you not only read this screen but also check out the menu on the left of the screen. Look at the “Hints & Tips” and also the stream you are intending to submit to (eg “Systems” if you want to present on Exadata). If you are unsure which area your talk fits in, check them all out.
the big red Submit an Abstract will actually take you to the same place that the left menu “Speaker Application” takes you too. The first step of submitting an abstract is actually saying who you are and registering on the system. If you are willing to judge abstracts (ie you ticked that box) you will then get to indicate what topics in what streams you are willing to judge. THEN you will be put into the “Speaker Lounge” and you can enter your abstract by clicking the “Submit” button.
When you come back to the system, you can go straight to the Speaker Lounge, the system will show you your details again so you can correct anything. You will see what abstract(s) you have submitted and click on them to check or change anything, or click on “Submit” to add another abstract.
Think carefully before you submit 15 abstracts. As a general rule, more than 3 and you start to reduce your chances of having a paper selected. People judge your papers will score you down if you submit too many, it’s like you dilute your judging scores over all the abstracts.
Enjoy.