 That is that better excellent. I'll go and thumbs up from the AV guys. Okay While Lana's talking if any of you've got Questions put your hand up and one of the ushers will bring a microphone to you that way We'll get your voice on the AV when the questions are asked. Okay, it's great. It's fine. Okay So to get started Because you all want to see me pop the balloon This is your program. This is your program this bit on the outside This is that this is the user interface that bit in there. That's your code When users are using your program, they want to get to this bit. They don't care about all this stuff on the outside This is the stuff on the outside that they're using to get into here The thing in here will allow them to do stuff will allow them to achieve goals The stuff on the outside is just the way that they achieve those goals the way they get in there to do that If you've got a good user interface, it helps obviously However, even a really brilliant user info. I'll keep on doing this even a really brilliant user interface is Not going to be perfect. It's not going to work for someone who's got English as a second language It's not going to work so well for someone who's never used the kind of program you've designed. I'll throw it away It's some It's not going to get not going to if you've got you might have something hidden in a menu somewhere And people can't logically find that and so what we do is we have documentation to help us to help us deal with the the user interface so between The user interface we add the documentation and we can get into your program I think that's called a technical hitch Basically what we're doing is we're using documentation to break through the user interface to get into the core of the program So that people can achieve what they want to achieve without having to worry too much about the clicky button And the writing the writing the commands in the command line So who wants to tell me what this is? It's black box very well head up cardboard Now is there anyone here who's never used a cardboard box before? Congratulations Michael. I don't think this talks for you The fact is we all use we always cardboard boxes with the exception of Michael We all use cardboard boxes every day very few people actually sit down and think about where they've come from and The reason this actually occurred to me at some point was because my partner started a new job He comes home on his first day, and he says you know what I'm working across the road from a cardboard box factory And I went I never thought about where cardboard boxes come before but someone's designed the dimensions Someone's worked out what material to make it out of someone has worked out how many people it's going to take To be able to make this thing. They've thought about whether to package them in lots of 10 or 20 or 500 Do I mean do they package cardboard boxes in other cardboard boxes that they put them in something else? You're gonna ship it on a plane are you gonna ship it on a truck where you're gonna send it to who's gonna buy it? How much are you gonna charge? There is a whole industry around things like cardboard boxes that we don't even think about and the reason I bring it up Is because technical writing is much the same We've probably if you're anything like me you've probably got a drawer somewhere. That's full of manuals that you've never read Absolutely You might have opened it you might have opened the Manual that you got for your fan that you bought last summer and had a bit of a laugh at the bad Chinese translation or something like that You don't read them nobody reads them it's um The thing is even though you've got them see them every day You don't think about who's actually written them. You don't think about where they've come from There we go So like the cardboard box you don't think about where your manuals have come from you don't think about who's written them Like I say you might have laughed at the translation You probably haven't thought it where they come from and I keep on finding myself in these situations Where I'm in a conversation with somebody at a party or whatever and they say oh Salana What do you do and I go well? I'm a technical writer and they go. What's that then? You say well, I write technical manuals for I write documentation for technical products. Oh There's someone has to write them, huh? It's it's the cardboard box problem. Nobody thinks about where they come from So what I would like to do here of the fact that it's black also is important Engineers quite often view technical writing as a black box. What happens is they give us source information and we pop books out and There is actually there is actually a process that happens except for the hecklers down the front There there is actually a process that happens in there What I would like to do for you today is quite literally unpack the black box so what I'm going to do is Discuss the process that we use at red hat. I'm a red hat technical writer by the way Well, I'm going to discuss the process. We use it red hat. We use a basic five phase waterfall model Quite simple. I'm going to try and spend about five minutes on each of the phases talking about what we do in each phase and What tools we use at each stage of it and then because I need to live up to my yeah to my abstract I I will go through and do some Do some writing tips for you at the end So phase one Phase one is what we call the information plan and that's where we work at our dates Essentially, so this is my diary When we when we get to a information plan We work out not so much title and that kind of thing but more what the book's going to cover Who the audience is going to be we do our audience analysis? That's really important and we work out who the dates going to be who we're going to get our information from at least in a rough Context and who our managers are going going to be in this particular situation. What project we're working on? The tools that we use are primarily a wiki at this point and that's because it's easy to edit It's easy to share. It's easy to organize stuff into a hierarchical Kind of system. We've got about 50 writers at red hat It's important that we can keep things organized that our managers can find our projects and our information plans and check out What we're doing that our engineers can can go to our wiki and and find the information plans relevant to their product And I'm going to try and knock this microphone off again as I fish something out of the pocket It's gone. No, I've lost it No, it's here. It's all right We also use a ticketing system. I'm sure you've all got one of these at the moment We also use ticketing system. We open a Just an overarching ticket to start with and this is essentially a management function It's a way of our managers being able to say, okay So what's Lana working on at the moment? When is she due to finish it? Will she be on time? How many other you know, is she struggling does she need more resources? that'd be nice and You know and who my engineering manager is so they can get in contact So that that's basically a management function at that point So we can get rid of those now Phase two phase two is where we decide what goes in the thing In this case, it's lollies, which is a lot more fun than most of my documentation We work out what it's going to look like work at what's going to be called We do our title our subtitle bit of an abstract whatever and we work out where we're going to get the information to create the thing we We usually identify a subject matter expert in phase one and then in phase two we get in contact with them and in In most cases you've got your subject matter expert It's an engineer on the project a senior engineer on the project you can go hey Bob give us an information he'll go Yeah, sure. I've been working on this wiki. I've got some bugs here. You can look at I've been blogging about it There's usually a fair few things that we can get in there and we can aggregate that all together in addition Believe it or not. We do Google for information. We I have been known to look at Wikipedia to check technical aspects There's code comments, of course and let this be a lesson to your engineers if you're writing code You must comment directly because one day a technical writer will be reading it and trying to work out what you're doing Code comments are very very important There's also things like knowledge base if we've had support staff writing knowledge base We've had customers giving us information bug histories that kind of thing Tools in this case we're back to the wiki believe it or not and It's just a really good way to be able to gather all the information because we're getting Information from such a disparate range of things. We gather all the information together on a wiki I just draw up a quick table with table and section and chapter headings and the link to the where the information is coming from for that chapter Which I like to pass them around take one pass around take one take a lolly quite specific enough I miss that comment The the other tool that's really important in addition to our wiki Is our bug system because he's big. He's our tracker bug So what we do is we have we set our tracker bug up at the top and this is where the management function happens So the management management can look engineering managers at this point Will you look at it and see all the other bugs we have the bugs they're sitting underneath it? I quite neatly like this and they can they can approve it they can say yep That's fine. They're the ones we want and then we were into obviously work on the individual and the individual bugs It is actually I see three fairly fairly standard in in many organizations, I think We use several wikis in red hat the one that we use specifically as track wiki There there are several in play there's there's constant Arguing over which one's the best which one we should all use which one should which one should go company-wide I don't know if they'll ever come to a conclusion, but track wiki is what we're using at the moment in our department Do I just take the microphone? Oh, sorry Sorry the question the question there was which wiki do you use and the answer was track wiki There's something Track is a bug tracking system. It is all so we do you know we only use the wiki component of it We don't we don't use the bug we use bugzilla feather for the bug tracking of course So moving right along phase three Phase three of course is the most important part and this is where I get to do my writing This takes up 50% of the project, which is why it's the most important part or It's the most important part. That's why it takes up 50% of the project put it that way So what I do at this point is I take the table that I created in the last phase If you remember I created the table with the section and chapter headings with the links to the information I write down my section and chapter headings in XML not on paper unfortunately We do a table and section headings and then we then we start dragging the information in we edit it and make sure we're happy with it We go over it over and over it and eventually we get to a point where we individually are happy and that's where the fun begins so after that We do reviews we make sure it's correct obviously we all have our own dictionaries But we also have use other people's dictionaries We do have a technical editor on site who likes to look at our stuff occasionally We have a legal department who we like to check out with trademark kind of issues And of course the most important part is the technical review if it's not technically accurate It will not get published at least in theory And if you do find a bug in any book, please raise you do find a problem in any book Please raise a bug we'll fix it The technical review is the most important We send it back to our subject matter experts and we do also like to send it to in the entire engineering team that we're working with and So we just basically say is this technically accurate. They will raise bugs. They will email us They will give us all sorts of feedback and we then obviously Coordinate all that and that's where our bug system comes in as well Oh my bugs So we they will raise bugs we go through each individual bug We fix it we get rid of it and after that's happened after we've fixed each bug We've gone. Yep. That's done. We send it over to quality engineering and quality engineering go, you know what that one over there She tried to fix it and they'll send it back And we'll have to fix again and then we can get rid of it So That ah the tools the tools start getting interesting in this phase as well When I started with red hat, which was nearly four years ago now. Thank you very much It's nearly four years ago when I started started with red hat and Back then we had a system that we used to call dock bot. It was pretty obvious dock bot it was a robot that created documentation for us and what at the time we were using CVS is our Repository it would grab the stuff out of CVS It had wrapped it all up and package it and we then had an internal website We could go and get our HTML PDF versions over time. We decided to formalize things We've got a fantastic engineer in our engineering content services department by the name of Jeff Fern who some of you may have heard of And he create he recreated dock bot and relabeled it as public in I've got a bit of an issue with the name publicings to me a public in a summer who owns a bar, but anyway Public in publication. That's where it came from and so public and now hooks into Not CVS anymore. It's SVN moving with the times Eventually, we'll get eventually we'll get to get It grabs our stuff out of SVN it wraps it up and we have now a proper official staging process So we've got an internal stage where we can put up our draft Versions and our engineers can look at it directly on the on the stage and public and can also do the publication for us But I'll get to that in the next bit. I'm not going to throw that because I'm going to have that later so phase 5 Phase 5 is a bit interesting because phase 5 is mostly about translation But it's also about publication which are two completely different things I have no idea why they've been lumped into the same phase and you should all go and speak to Joe at Hacos who wrote them and Find out because I'd like to know so translation first of first of all Red Hat translates into around about 26 languages. It does vary Anywhere in the 20s as a general rule it obviously not every product goes into every language I do believe rail red hat and preslinux goes into most of those languages If not all someone from red hat in the audience may be able to confirm or deny It really depends on where we're marketing each product as to where where which translations it gets And it also depends of course on what translators we have available. Most of our translators are in Brisbane I believe we've got around 30 of them at the moment possibly I'm looking at Marco because Marco might be able it's around that number, isn't it? They all work very very hard. They're all lovely people and what public and does so coming back to public in Just cuz I like holding beer and waving it around. I keep on thinking I'm gonna pop the lid on that soon if it was only if only it was cold I'd What public and does we've got a sort of magic button in public and that basically splits everything up into the individual language files each Translator then gets their individual language They do the translation for a switch to me as a black box Hold translation process a bit bizarre. They go through and they do their translation They then push it we push it all back into public and and public and wraps it up on our stage so that you can just select Which language you want you get your book in that language. It's really really neat Public and also I'm even to I'm even to publication. Let's move away from translation. Sorry French Um We publish we don't publish dead tree. What obviously this book was actually I purchased this in 1994 It's still got their seat in it. I clearly haven't read it Because I went and worked for an open source company We don't publish dead tree books We do have the ability to publish dead tree books. We can provide files to printers if we wanted to we generally don't And because I'm too cheap because I didn't read this book because I'm too cheap I I printed one out We we publish in HTML standard HTML or every chapters on a second page you click next to go to the next chapter We publish on single page HTML, which is fantastic if you're searching for something. It all goes on a single page You've got a scroll a lot. We publish in PDF, of course And we also publish in EPUB, which is a fairly new thing that we've only just started doing reasonably recently And it's actually really exciting. How am I going for time? Can I throw a story in I'm not doing too badly Excellent, I'll throw in a quick story and hopefully it won't cut into the question time at the end There's an interesting story that was taught I mentioned Joan Hacos before is the woman who wrote the wrote the model that we use Joan Hacos was is an American writer of documenter type person and she She told this this story once of there were there were guys who the guys who work up the the energy the electrical poles And someone had been a company had been hired to go in and rewrite their documentation for them They had they had a reference manual that they they needed to use to look up various codes whatever it is that these electricians do and And then they you know, they need to look it up while they were working. So they did a great job They redesigned everything they got it all written down and they produced this manual and they presented it to the company and The company presented it to their workers. These are the guys who work up poles. I'll remind you and They went How am I going to use this? I can't put it in my back pocket. I Can't hold on to it because I'm busy holding on to the pole and whatever tools I've got and all the rest How am I going to work it and so it got ignored? Basically, they hadn't done an audience analysis. They hadn't worked out who was it was going to be using these things And what conditions are going to be using it in and this is why we began they did eventually do an EPUB Version to solve that that issue. I believe another company came in and fixed it but This is exactly why we began using EPUB and there's an individual story and read how about it our global professional services people quite often work in In they work on site at various customer locations and they're quite often subject to fairly rigid security protocols that the the customers they go to especially if they're talking government or defense or whatever and Of course, they can't they can't take a printed version of the rail if anyone has seen the rail deployment guide It's like hundreds of pages long. It's really huge. It's this mammoth book that everyone at Red Hat talks in awe of The rail deployment guide So they can't go take a printed version because it's just impractical They can't use internet when they're on site. So they can't access the online versions What do they do? Well, they do they download the EPUB version take it in on a non-internet connected machine They've still got the information at their hands They don't have an internet connection and they don't have to carry a set of encyclopedias That is exactly why we started doing this. So there's my lucky. It's not a real Kindle, huh? Okay So that pretty much wraps up phase four, which means we've only got one phase left In theory, this should be the phase where you get the money. I've got doubloons You know what though? I bought this in the $2 shop. You know what they say on them Kids obviously don't understand what doubloons anymore. It says pirate money This should be where you get the money. It's not We work for open source Don't get money in open source. What are you talking about? So phase five is actually where we do our review So what we do because we're geographically disparate as a to give you an example Currently my engineering team is based in both Raleigh and North Carolina and Westford, which is right near Boston My project manager is in Bono in the Chakra public My documentation manager is in Brisbane. I live in Canberra Which is another hour out during summer I've got a developer in The UK. I think we've got another one in Canada Yes, I think we have another one in Canada. Oh, yes, and we've got a couple in South America as well So the fact is it's very very difficult for us to get in a room together and say so. How was it? It's not gonna happen. In fact, it's fine It's can be very very difficult for us to even find a time for a meeting Even if we can all get on the phone at the same time However, normally what happens is the person who's in Australia gets up at 2 a.m. And we jump on the phone Do you like my new iphone? I was very pleased that it makes sounds that they're very soft It wouldn't be very good in a train station or something. Anyway, so what we do is we get on that We get on the phone. We have a call. We say so it was a good for you. Yeah, it was great Let's do it the same way next time or you actually know that really sucked. Let's try something different I promised you some I did I did promise you some some tips on writing the fact is anyone can write I know you probably have grown up all your life going. Oh, I hate writing This is why tech writers exist because I don't want to do it Somebody else has to do the writing. Unfortunately, you do have to do writing even as an engineer I know I'm sorry You do have to do writing at the very least you have to comment your code because otherwise technical writers will come and stab you You you problem. Thank you You do you do have to have to document what you're doing at the very least We like you to do things like write blog posts and write wikis and or it'll keep some scrap paper on your desk and just note down What you're doing. It's it's very very helpful. So even as an engineer. Yes, you do have to write The good the good news is of course, I don't believe that anyone actually sucks at writing I do believe you can you can learn to write. It is a learned skill. It's not an inherent skill I wasn't born with a dictionary in my mouth. I'm not particularly special in this regard. I've just worked at it So Slides do suck. Yes. I think I've got six. So I'm sorry I sort of had trouble coming out with props for these ones so The first thing you have to do and I have already touched on this is get organized And this is where your phase one information planning comes in if you know When you've got your due date when you've got to be finished by and not just when you've got a your final due date your final Delivery, but when you've got to get the next bit and a bit after that and the bit after that you will be able to achieve it and To illustrate the point How long do you think it takes to write a novel a standard? Yeah fiction novel Mills have been three weeks. I can go along with that a year. Let's talk about literary fiction decent fiction a year two years five years a lifetime You knew where I was going with that It it you know, I'm sure there's plenty of people with unfinished novels in their bottom drawer. I Without boasting I've written three and I wrote each of them in 30 days in November as as Nareen pointed out And the way that we're it's a competition called national novel writing month And I'm not going to advertise it here, but if you want to know more come and speak to me It's competition called national novel writing month and the goal is to write a 50,000 word novel in 30 days No, none of my three novels will ever be published. They all suck So don't even bother asking me They but the fact is I have written three 50,000 one novels. Yes, they are complete novels. They're complete stories They were had a beginning and an ending and a middle in most cases and And they were all written within 30 days Some of them were written were finished at a quarter to midnight on the last day But they were all written in 30 days and that's because you have a goal If you have a goal, you've got something to achieve It's the way we work as humans and I'm sure we've all heard we've all been to goal-setting Courses and this kind of thing that that work makes us do all the time And it's always about breaking it down into achievable chunks. It's always about setting deadlines It's always about making them making them, you know realistic and timely and all the rest of it And that's exactly what you need to do in your writing documentation as well is Stick to your standard goal-setting principles Make sure you've got a date make sure you know what you're supposed to be delivering by that date and ideally have a manager making sure you're doing it so the next one is choosing your voice The way I'm speaking to you now is completely differently Completely different to the way I would be addressing these children. I mean other than the fact that I probably would have had a DeLorean to do it I love this picture. They all look so neat and proper. I'm sure my daughter doesn't look like that in school But the point is the voice is different use different words. We use different expressions We I was going to say if you're addressing school children, you might use more props, but maybe not We the point is we dressings differently, it's exactly the same in writing as in speaking you need to talk to your audience in different ways It might come as news to many of you, but engineers are not the same as Ciss Admin's Ciss Admin's and Joe made the point in her talk on Monday Ciss Admin's are different to engineers and they need to be they need to be spoken to in a different way Not that one's more intelligent than the other of course. They're just different So when you when you're addressing a Ciss Admin You need to discuss different aspects and different ways of achieving goals Then when you're when you're talking to engineers and it's it's different again when you're talking to users on you can talking to contributors There's all when you're talking to management or whatever. So choose make sure you know your audience and you choose your voice Say what you mean If you want to warn people that there are flying toasters and I'm going to have to read this out because I always forget it say Wanting flying toasters for starters. Don't say Take heed of the fact that in some cases they may be airborne heated bread-cooking apparatus Because what's going to happen is by the time they finish reading the sentence They're going to be hit in the head don't ever say more than you need to Analyze every word analyze every sentence analyze every paragraph make sure it's serving a role Some of my favorites in technical running of things that there may be a risk that there is a possibility that in some cases this may happen Don't just say sometimes There's There were ways of rephrasing things phrase it the way you would when you're speaking Not the way you would when you're Trying to write technically This brings me very neatly To use short sentences There are rules of thumb about writing short sentences They have a long sentences should be the general and technical writing you want to be around about 15 to 20 words That's fine. If you're reading the dead tree books If you're not reading dead tree books if you read it on a screen Attention spans are different We're much more distracted when we're on a screen because you know, there's like Google and stuff there And it's much more exciting than reading this technical manual You need to try and keep it sort of 10 to 15. That's on average Of course, don't be afraid if you get a 16 word sentence. It's not the end of the world You want some shorter ones and you want some long ones what you don't want is 17 sentences. They're all four words long Followed by 17 sentences. They're all 34 words long Because the start is it's going to look really weird. It's going to sound really bad and your users not going to understand what the hell you're talking about One of my favorites who he went to Guinea Most of us if not all Okay, when we're at uni, we're taught to write up to a word limit So you might have a fantastic idea It's the great ideas is best idea you've ever come up with and you can probably express it very neatly and about 300 words At university you're expected to express that 300 word idea in a 5000 word essay and so we do We do we sit down we start when we write a very flowery introduction and then we write the next bit And we choose the longest words we possibly can because you know what we want to do We want to teach our lecturers how clever we are You I've just described every essay I ever wrote Except for my last one because I've started an actual technical communicators course and it's really hard not to write like a uni student You actually got to write like a technical writer and a technical writing course and there's all this cognitive dissonance with that Unfortunately take writers don't get paid by the word. It would be nice if we did because I can be very low-quacious I Was I saying I was going to I was going to talk about academic writing in terms of not just how long and Flowery the language is but also the words we choose we choose these big words because it makes us look smart and as humans We want people to think we're smart. We want people to read the book and go Haven't they got a fantastic grasp of the English language? I'd really like to read a literary novel written by this person and I didn't bring it with me I do have a I do have a 91 word sentence that I have on cards that I like to give out But and then ask people what it actually means, but I didn't bring it with me. Unfortunately I Illustrate this a little bit more. I did some editing for a gentleman who shall remain nameless So that he remains shameless, I guess He it was absolutely abysmal and it was a typical case of university writing typical case of the real pretentious language and I've got some examples from this particular essay I was going to say that the problem too is when you're using big fancy words that you might not speak You might not use in conversation You quite often misspelled them and you quite often mean something you don't maybe didn't realize that they mean One of the one of the ones he used a lot he used the word enumerated but what he really meant was discovered or found The word enumerated means you counted something Doesn't mean you found it and so what it do is he'd say we logged on to the server and we enumerated the packages And I bet he didn't sit there and go. That's one package. That's two packages and that's three packages He looked at the package He might have looked at what sort of packages they were which ones what categories they fell into whatever I can bet your bedroom doll Bet your bottom dollar. He did not count them. So he did not enumerate them. He found them Utilizing Utilizing gets used again and again and again and again again. It's not incorrect. I will say that it is not incorrect It's just long It doesn't need to be using is fine. We're all we're all modern, you know, we don't need to see need to use this okay, like which anyone The other one he did a lot was provide when what he really meant was prove And I can tell you right now that nothing will ever provide to be true And the other which I've actually forgotten to write down here, but I can't forget it is the word assess The word assess has four s's in it It's a double s e double s if you don't put the last s on It's not assess anymore It did make for interesting and very hilarious reading in some cases do have a prop for this one This is my favorite prop. It goes with my doubloon. Sorry my pirate money goes with my pirate money. Oh It's in the box because I didn't get it Okay, I don't with a knife. I'm gonna have to figure this stuff up, aren't I? And it with a knife every editing pass you do on your document should make your document about 20% shorter I'm not kidding. That's true. If you do five passes, well, okay It should get about 20% shorter. It's because you're cutting out the extra words I go shopping at that $2 shop I'll have my doubloons instead You should be getting 20% shorter. You're cutting out extra words. You're cutting out anything that is not absolutely essential Um, a lot of a lot of people would like to do this thing where they use the word namely Something and then they tell you that they're going to explain it. Just say it. What's it? What's the example? I like to use I did in a Hawaiian dance namely the hula Don't need to Don't need to just so I did I did a Hawaiian dance called the hula or I did the hula, which is a Hawaiian dance You don't need to tell me that you're going to tell me something Exactly Every time you had it bring it down take out all these extra things if you've got a sentence that says more than one thing Put it into two sentences cut out. There's extra filler words You need to read what you're right It's not easy to do it's not as easy as it sounds because the problem is we read what we think we've written It's hard It's it's hard to read what you've actually written and not what you think you've written The best way to do there are three tactics that I use the first one is walk away Walk away for as long as you possibly can and then tell your boss that the reason it's delivered latest because you had to walk away from it because Lana said so I Tried that it didn't work Walk away from it even if it's only to go out and get a coffee And you know, obviously the longer you can leave it the better leave it overnight is always a good idea But even if you just get up and have a walk around and then come back to it at least you're looking with slightly fresh eyes Secondly, do the first here, sorry Do the first pass forwards, but do it out loud. I Work from home, which is a good thing for my co-workers And I have a big picture of the Beatles on my on my wall So John George Paul and Ringo get most of my books read out to them. They're very very boring lives these days You stand out and you read it out loud and the reason you read it out loud is because we naturally use language and we naturally use grammatical constructs and That was a big word When you you do that slight little pause you put a comarine You do the bigger pause you take a breath put a full stop in if you find your reading sentences out And you're getting short of breath. You probably need to put another full stop in there right now Before you have to go And pass out Because John Lennon always looks me really badly want to do that Then once you've gone through forwards and you've read out loud and you've had a good drink of water Because you generally need one Then read it backwards Which sounds silly Depending on the length of your document if you've got a short document and you're doing something like pre-reading your business cards Read each word backwards because then you see the word and not its placement in the sentence or its placement the paragraph You've got a longer document read each sentence read the last sentence first and then the second last sentence and the third last sentence and walk the entire way through your book and that way hopefully you'll break the You'll get that memory you break that memory pattern that you had if you know when you wrote it that this is how it Was supposed to sound if you read it backwards. It's not going to sound like that anymore It's going to actually trigger those those typos. You're going to find the double ups of the these When they break over the line and that kind of stuff so read it backwards Oh I have another story. Do I have time? Eight minutes. Excellent. I'm sure I've told the story before so please stop me if you've heard it In Canberra about ten years ago in the Yellow Pages There was an ad for a bus company that advertised quite proudly that they did school executions If they had have read the ad backwards, I can guarantee they would have worked out that what they really meant was excursions. I Love that story. Anyway Sorry to do this to you. I have also been asked to mention that red hat are hiring. I've got flyers down here They are looking for engineering types. They're looking for support service types. They're looking for security types They're also looking for technical writers and Translators, so please come down to get a flyer. It gives you information on who to contact to get more You can also grab business card off me and I can help you do that, which is really good because we have a hiring bonus Okay