Everybody for us here ripping 2022 tops diamond icons baseball hobby one box number 20 random hit style We got 10 spots of the break 10 hits in the box We'll type them in as we go to the random at the end to see who's getting what? Thanks you everybody for joining. Let's see what we got now Yeah, about 10 minutes behind. I always fall behind on icons blank cards on top. Is that a sign? No three blanks. Whoa. You're Sam. Wow That relic Eddie Matthews 10 of 10 cut signature it's who a four is Al Barlick Hal Barlick Former umpire. Oh, it's got it on like a portrait of him right there Al Barlick patch auto Kyle Tucker 11 to 25 nice Tucker. He's the first Tucker I've seen out of this. Yeah, good young outfielder, too. I would just make the code out. Oh, yeah All of them are we just mad? That's what I've been doing every thin Nice Tucker there. Wow. That's nasty patch auto Ronald Acuna junior two of five Heck yeah, good luck on that one Beautiful Acuna, but he's Scott Rowland auto two of 25 Scott Rowland Cardinals Rowland Silver ink David Wright auto five out of five Jersey number Will Clark auto nine out of ten will Clark Chipper Jones auto 20 of 25 on the chipper a Vladdy Jr. Silver ink auto eight of ten Sig Vlad that one magazine. We'll get this one mag two Aaron judge icons of the diamond auto Number 25 at 25 on the book and nice Vlad and judge back-to-back on the back there Back-to-back on the back. Oh Had to say that like it sounds weird Nice stuff there. All right guys. There's our ten hits Okay, random time or randomize the names and the hits the same amount of times and put them side-by-side. Good luck everybody six times on each five and one one two three four five six Bo G down to a shams and Six times on the hits one two three four five six Al Barley cut auto down to the Aaron judge auto I've got Bo G with the Barley cut auto John a the David Wright auto five of five Robert C. Kyle Tucker patch auto Adrian K Scott Rowland silver ink auto Thank you. Excuse me See Adrian. Hey the Scott Rowland John a the Eddie Matthews bat relic 10 out of 10 Braden a with the Will Clark auto Brandon O Ronald the Cunea junior patch auto 205 Danny see with the Vlad junior silver ink auto 8 at 10 Brandon. Oh the Chipper Jones auto 25 and a shams the Aaron judge auto 25 25 we'll get those results posted to the site. We got the triple case up next


Good evening, everyone. I'm assuming that all of you have either appeared in the past in the personality test, or you're planning to appear in a personality test. My focus today will be totally on how do you prepare for personality test. So some initial questions. We must understand when you sell a product or an idea you must understand who is the consumer of those ideas and products. And you must clearly also understand what is the word looking for. This is very important because sometimes you make a preparation without understanding who are you going to talk to and what is the purpose of the discussion. The second part of my brief presentation would relate to how should you prepare for the test or personality test and what should you do at the time of this. So first is the understanding of the context that is the board. The second is the as you go along to prepare for the test. And the third is at the time of interview what should you do. Now, the first point has to be understood very, very clearly by all of you. I must clearly appreciate and understand that it is not repeat, not an interview. It's a personality test attitude part. Very, very important. It will not only help you in your interview, but when you get into the service which you would most of you hopefully, you will require that attitude to succeed in the career. This is not merely as as if now I can understand that all of you are focused totally on getting into the service somehow anyhow, but I've seen a large number of civil servants spending miserable time in civil service because of wrong attitude. So there's no harm in developing a positive attitude right now, whether you make it or don't make it to the civil service attitude is extremely extremely important. Now, evolving out of your understanding that it is not an interview and a personality test. You must also appreciate the fact that the focus of this personality test is not knowledge. Your knowledge has already been tested through in your written exams. So don't waste your time in trying to read your mathematics and chemistry and physics, or history or whatever. Do it. You've done that in the means exam. Your focus when you prepare has to be totally different.  That's very, very important. And I'll briefly tell you how you can actually improve your articulation. And there is a there is hopefully a slide, then you have to improve on your logic. How do you logically present your arguments. One is your capability to speak. The other is your ability to speak logically, one point flowing into the other point. This is also equally important for your written exam, but in interviews absolutely imperative. Then, whether you are reasonable, it's not merely logic, if you are very reasonable, and you have to be coherent, meaning you should not blabber. If not, and then comes the very, very important point which was mentioned earlier, the positive attitude. So they may give you problems. But your approach to these problems will help those of you can find time and read my recently released book, ethical dilemmas of civil servant, they're about 70 odd case studies in that where you'll find that the difference that it makes from one officer to the other officer is basically in the context of your attitude. It makes a world of a difference. Two officers are actually equal, very competent, very sharp, very bright, very articulate, one is positive other is not. I'll give you some examples of how do you approach a problem so for example, when I was called secretary. I was posted as school secretary in 2014, when all scams had happened. And at that point in time, when I walked into the office room, I felt as I was walking into a graveyard, because the CBI was after files, it was after officers. Now, if I didn't have a positive attitude to finding solutions to the problems, I would have found it I would have become a part of the problem. It is the positive attitude, or the attitude of attempting to find solutions, or the belief that there are solutions to problems that you start finding solutions, and it all depends on the attitude. So much so that after 12 months when we had sorted out most of the core issues used to jokingly say that give us the Kashmir problem, we just might be able to find a solution. So the point is problems are what they are. You can't do much about the problem. They're there. Your, your efficiency will be determined by your approach to the problem. How do you see whether initially when a problem is presented to you, you start about it positively or negatively and hence positive attitude becomes very, very important. The other point that you should do is you should be aware of the recent happenings, something which has happened to them. You know, they will not test your knowledge, but they will test your awareness, awareness about what is happening around you. So for example, I'm certain that many of you will be asked about the farms laws that are going on. They will be asked about the farmers education, you have to be aware. That's how it is. So whatever is happening, some of you who may have written cricket as your hobby may ask you about what has happened in Australia, you can ask you about cricket. The next is when I talk about awareness about the place where you stay, where you are staying. So if you are, if you've come say from Allahabad, or you've studied say in Chinnai, you must know the recent issues about Chinnai, the history of Chinnai, the college where you studied its history. Some great people who've come out of that college, you should know about them. So the fundamental point here is they are checking about your awareness levels of recent happenings as well as the places to stay. And then finally, your hobbies. I don't know whether you already mentioned your hobbies, be careful about mentioning your hobbies. Hobbies, having hobbies does not necessarily mean that you are very good at it, but you are aware of it. So for example, I'm very fond of music. If I write music as my hobby, I might as well be prepared for answering questions related to music. So if they ask me, well, Mr. Suru, can you sing? No, I have to be clear in my mind whether I should say yes or no. I can tell you about my example. I had given music my hobby in one of the interviews, they asked me whether you can sing. So my job, my response at that point in time, which I think was fairly good. I said I'm a Khan saying not a Khan saying, meaning thereby, I'm a good listener, but I can't sing myself. I'm not saying you answer it in that manner. But if you say if you give tennis as your hobby, then you should know what is happening in Australia and open or what is likely to happen in Australia and open. Who are the good players and tennis men, women, what are the problems with tennis. So if there is a tennis player sitting in the board, they will ask you about tennis. So be careful about what you write and when you write, you have them to be fully conversant with those aspects. Now, this is also very important. You are not supposed to have solutions to all the problems that beset the country. Don't worry about it. They might ask you about the Kashmir problem. They asked me in my interview. They asked me about the Kashmir problem. And I told them whatever I thought was correct. You're not supposed to know if you knew the solution to the problems, you would not be sitting on the other side of the board, you would be asking questions and those that are asking questions are also not available are also not have all the solutions.  So what they are going to assess you is in terms of approaching a problem, the nature of the problem, rather than actual solutions, because whatever they're going to ask you the solutions are not already there. So again, let me take the example of farmers agitation. If someone asked you whether the bills should be abrogated as is the demand of the farmers, then I can answer either way. Yes or no, but whatever answer you give, you must have a reason behind it. You just can't say, sir, it is too bad. It should be abrogated. Then you should be able to tell why should be abrogated. What are the possible consequences of abrogation of those laws, you should be able to give a reason behind whatever reply that you get. Then let us now come to two aspects of it. How do you prepare for the test. And the second one is what do you do at the time of the test. The first is, you must improve your articulation and awareness that is prepared for preparation. So you have two months, three months, six months, whatever time you have. And the suggestion that I have here is which I give to everyone is pick up the editorial articles. I'm not talking about the editorial. On the editorial page, there are articles that come, you should first read them aloud in in front of a mirror and record what you're saying. Initially, you'll feel terrible because not used to it and I can again give you my example. I was very poor at articulation to begin with. I did my class 12 and I had physics, chemistry and maths. And thereafter I switched over to arts. So my language was bad, my articulation was poor, and I couldn't express myself very fluently, but I tried this trick and it worked. You need the article on the editorial page allowed regularly for next one month, two months, whatever time you have one, you will see an improvement in your articulation that will help you do that. Number two, you will also get a lot of knowledge or awareness about that particular issue. And more often than not, the articles on the editorial page of a newspaper are about issues that are current. So your awareness level will go. The third advantage that you will have is that once you start doing that, you will understand how to logically build an argument. You can, because these articles are based on logic. You may agree, disagree. That's a different matter. They could be a particular bent in that article, but whatever opinion of the author is or the writer is, you will see that they build their arguments logically. So you will have logic there. So your articulation will improve, your awareness level will improve and you will be able to say it logically. That's the first stage of reading of articles. After one month, two months, when you become slightly more fluent in leading, the next step would be to put down that paper after you've read it out, put it down, and then in your own words, try and speak out what is there. That's the second stage. The third stage would be that if you have a difference of opinion with the writer, then after having said what the writer has said, you present your point of view. Now all this exercise will help you improve your articulation, your understanding and presenting it logically. The other preparatory work that you can do while you prepare for the interview is to constitute small groups of aspirants. And number one, hold discussions amongst yourself. So what you do is you pick up a topic and these days you have a WhatsApp group. You need not meet physically, you can do it in a group also on a Zoom chat also. So initially you assign each individual, suppose there are five persons in that group, assign each one on a particular topic, ask him to prepare and speak for about five minutes on that topic. It helps the person who's preparing and speaking. It helps others in terms of knowledge. And then after he's spoken for five minutes, each person gives his own view on that particular issue in a minute or two minutes. Again, if it will improve your articulation, it will improve your awareness, you will be able to respond to a particular situation in that. And finally, for preparation purposes, you can have mock interviews. So amongst your five, four can become a board and one chap can. And they can ask questions. All this will help you enormously in preparing yourself for the interview. Now, as I mentioned earlier, while preparing for the test study at length the details of copies that you've indicated place of state where you've been educated. If you have worked somewhere, then you should know very well about the organization's problems and your contribution, as well as your reason for quitting that. Why do you want to quit that and join the civil service, you should have good answer that then brush up the details of the subject that you have, you have offered, not in the context of the subject, but if there are some recent developments. So suppose you've opted for political science or public administration, if they are current issues relating to political science and public administration, you should be conversant with that. And finally, this is very important, you have to have an in-depth understanding of current affairs through newspapers and articles, read newspapers. Of course, these days on the net you get details of everything you can read very easily. But what you have to do is to prepare yourself in terms of whatever information that you can gather around that time. And on the day of test, you should dress normally in which you feel comfortable, don't wear anything new.   But don't look sleepy, you beard, like I have a grown beard, I would not like to go and interview with a beard if I have to. You should look decent and presentable, you should not look outstanding, outlandish. The second point is very important. You must listen very intensively and you should practice this in group discussions and mock interviews that don't interrupt anybody, never. Let the other person complete his point, and then you should start your argument. And finally, most importantly, you are not there to win an argument. Again, very, very important. You may disagree with the panelists or the board member and politely do that. I remember in the first year that I appeared and I qualified for the police that year. I got about 55% marks in the interview or in the personality test. In the second year I got 80% which was the highest in the country. The difference was this, I was not trying to win an argument in the second interview, I patiently listen to them, and then respond it in the manner that I could, makes a lot of difference. This again is very, very important. You must clearly understand the difference between facts and opinion. So you should not be guessing facts until less a board member ask you to guess. If they ask you then you should guess, but if they're not asking you, don't guess. If you don't know a fact, then you should say no, sir. I'm, as I said in the beginning if you recall, you're not supposed to know everything. So if you don't know facts, admit it, be, be very humble, be very forthright, be very honest, because if you try and fit and tell you, one of the board members is going to catch you, and then there's no redemption. So your focus should be on, on, if you know the fact tell them, if you don't know the fact admitted, but opinion will be based on what he's saying. So you may have an opinion. I mean, it would be wrong of you to say, sir, I don't have an opinion that would be wrong, because as youngsters, you're supposed to have opinions on issues that are besetting the society. So you should be able to say something about it. Opinion can be yours, but facts cannot be yours. Facts are facts. Then when you are saying, and this you'll have to practice practice quite a lot. While in your group discussions mock interviews that at your age, you do not have finality to issues, because what they so again I could go back to the farms legislation. There is no finality as which is right and which is wrong.  So don't say sir, in my view, this is happening. So you will have to keep as I use the term, you have to have some exit or open, sir, in my opinion. So, which means that there could be a difference of opinion, you have a different opinion a board member may have a different opinion. You can use words, probably in all likelihood, perhaps by using these phrases, you are leaving some door open for you to get out in case you get caught. But if you say, no, sir, I'm sure this is this is this is what it is. You are in trouble if you do that. Because as I said in the final, in the last point, that there are no final solutions available to most of these social problems. We are all grappling with it. Those sitting the board would also be grappling with it. Okay, all the best. God bless you. Work the way I've suggested many of you will qualify and probably we'll have a cup of tea after you qualify. God bless you. Take care.


My text editor of choice these days is DOOM Emacs and DOOM Emacs is great because it's not just a text editor, it is a full suite of applications, it's this environment that has all of these cool tools, not just a text editor, but many things, including a really great file manager. The file manager within Emacs is called DeerEd and today I wanted to highlight some of what you can do with DeerEd inside DOOM Emacs. So let me switch over to my desktop and let me go ahead and launch DOOM Emacs here and I'm going to go ahead and open my DOOM Emacs config file. So this is a config.org. So it's written in org, which is great because I love to leave a lot of comments. You see, I have these tables specifying various keybindings. This is the DeerEd section of my config file. If I go to the top of my config.org, you can see my config files rather lengthy. But the great thing about having a org document as a config file is you can organize it very neatly. So let's go to the DeerEd section. I'm going to show you some of the settings I use for DeerEd, some of the keybindings. And let me also go ahead and open a DeerEd window. So this is my home directory in DeerEd. And essentially you can think of this as the LS command with a few flags and options like in a terminal. It's basically the same thing. DeerEd is essentially that LS listing in a long format. Now the very first thing you need to know about DeerEd, if you're brand new to DoomyMax, you need to know that DoomyMax uses the evil keybindings. So navigation is done with the standard HJKL VIM navigation keys. The other thing you need to know of course is how to get into DeerEd. There's a couple of different ways you could launch DeerEd. First is do metaX and then type the word DeerEd. If I hit enter, it's going to ask what directory do we want to launch DeerEd in and by default it's going to default to the home directory, which is where we're already at here. Another way you can get into DeerEd is if you're working in a file, you could do space period for the find file command and you could navigate to a directory. For example, maybe I want to go into my app images directory here. If I hit enter, we'll go into that directory inside a DeerEd buffer. Now that's not really what I wanted to go to. So let's go back to the home directory. So space BP for buffer previous gets us to that previous buffer, which was the home directory here. Now for the most part, I'm using DeerEd as it comes out of the box in Doomy Max. I haven't made that many major modifications. The one major modification that you'll notice in my config up front, when I say HJKL is the navigation, by default, J and K work in DeerEd inside Doomy Max. So J would be down, K would be up. But typically to go into a sub directory, for example, maybe I want to go into this dot DWM directory instead of L, which is what you would expect. L actually was not set to that binding, but I thought you would have to hit enter to go into that directory. And then H wouldn't actually go back. I believe it was the carrot symbol that goes up a directory. Now those are kind of weird. I didn't want to fool with return and carrot. I just wanted to have my four fingers on HJKL, where if I wanted to go in a directory, for example, that dot DWM directory, I just hit L. If I want to go back, I just hit HJK, right? If I go into config here, put the cursor point on dot config, I could do L to go into that directory, and then I could go around into this directory, hit L to get into that directory. Or if I want to go back up a couple of directories to get back into home, all I have to do is hit H to go up, H to go up, and I'm back in home. Of course, standard Vimkey bindings will typically work here. So GG would go to the first line in the document, right? In this case, it takes me to the top of this buffer. Capital G would take me to the end of the buffer. If I do five capital G, it would take me to the fifth line of the buffer, which in that case was dot bin, because it does count the first two lines here that are not really directory information. The first line is just the path, and then the second line is total used in the directory, the size of the directory. So to get this HJKL working as you would expect, the way it works in a lot of especially terminal based file managers that use the VIM bindings. What I did is I have this section here of evil key bindings. Remember that it was the carrot symbol to go up a directory, but now I've changed that to where H on the keyboard is up a directory. And L is dear ed open file, meaning wherever the cursor point is, go into that file or that directory. So that is now why HJKL works as expected. I mentioned that dear ed by default has this basically long format of the LS command as the output. You can change that a little bit for me. I actually quite like this. My typical LS command is basically LS-LAH for long format, all the files including the hidden files, and H for human readable numbers. That's what it's defaulting to here. So that's typically what I use, but you could edit that a little bit if you wanted to. The other thing is you can quickly go from this long format listing to a short format listing using this key binding here, the opening parentheses.  If I wanted the long format back, I would just hit that opening parentheses again, and it toggles the long listing back on. Now there is a closing parentheses binding as well, and that is for a get information, I believe. If I do the closing parentheses, if there's anything that is like a get repository here, or it doesn't look like there was in this, but that was deer-ed get info mode, what that toggles a specific get mode inside deer-ed on and off. I've never found that particularly useful, and honestly, I never really toggle on the long format either, but I know some people may find that useful. Now I mentioned you could edit the output of this. There is a variable. There is deer-ed listing switches that actually list the flags and options for the LS command that deer-ed shows by default. So if I do space HV inside Doomy Max, space HV is a help command. All the help commands typically start with space H and then another character. Space HV is described variable, and the variable I want to describe is deer-ed listing switches, and it's the second one here in the list, and I'm not going to hit enter on it because it already tells me exactly what I wanted, which is what is that variable set to? It's set to dash A-H-L. I remember I typically use the LS command in my terminals with dash L-A-H-L. It doesn't matter the order of the switches. They're using A-H-L. They're going in alphabetical order. They are also using dash V and dash dash group dash directories dash first as a flag as well. And what this does, it makes sure that the directories are actually listed first in the output because by default, if you didn't have that set up that way, it would actually list everything alphabetically and all the files and directories would be jumbled up. They wouldn't be in a specific order. I think most people are going to find that confusing, so most people would actually set it with the group directories first flag on, and that's what Doomy Max does out of the box.  So let's talk about file previewing. Let me make this full screen, this deer-ed buffer here, and let me go down toward the bottom. And let's say I want a preview of one of these files. Now, what I could do is I could do meta return, so that's the alt key return, so alt return, and what it will do, it will give me a preview in this vertical split. And I say it's a preview. I could actually edit the file, but by default what that alt return does is it opens that in the split, but it keeps the focus in the deer-ed buffer, so I could go down to a different file and do alt return and get a new preview, or I could keep going. Let me go up and maybe alt return on this. So you can see that's very cool because you just keep previewing, essentially, these files in this vertical split, and that's kind of a nice feature. Now, if I want to get into that vertical split to actually edit the file, I could do control ww, which is a standard VM command, right, to switch from one frame to the next, and now I'm over here and I could do whatever control ww to get back into the deer-ed buffer, right? And for DOOM EMAC specific bindings, instead of control w followed by w, you could do space ww, so space ww works the exact same way space ww gets me back. If I wanted to close that split over there, I could do space ww and then space wc to close, and now that split, that preview window goes away. And of course, sometimes you don't want to actually get a preview. Sometimes you're on the file you want to work with and you just want to start editing it. And for that, instead of doing the meta return, just do a simple return and it'll open that file in the current frame you're working in. Now remember, in EMACs, buffers don't just magically get killed and go away, even though we're not actually viewing it, the deer-ed buffer is still open. We can go back to it exactly where we left it. If I do space bp for buffer previous, I just go back to the deer-ed buffer that I was in before. Now say you're working on a config file. For example, I'm in my config.org here. Maybe I want to open up deer-ed in the directory that I'm currently working in as far as this file. Well, there is a deer-ed command called deer-ed-jump, which will just jump to our working directory here. I have this key binding to space dj for directory jump and it goes immediately into my .config slash doom directory because that's where that file I was working in actually lives the config.org. And you don't necessarily have to use the deer-ed-jump command to do that. You could also simply do a space period for the find file command because by default, it defaults to your current directory's location. And if you just hit enter, it works the exact same way. Let me hit enter and get back into my config file. Actually, let me go ahead and switch back over to that deer-ed buffer. So let's talk about how deer-ed works as far as marking things for renaming and moving and copying and deletion and things like that. So actually what I'm going to do, I'm going to search for a specific directory on my system because just like in Vim, you do a slash to search. I'm going to search for a directory I have called .screenshots. I'm going to hit enter and go in this directory. Let me zoom in a little bit here. And the reason I picked this directory to work on is because there's nothing really important in this directory. If I accidentally move something someplace or delete something, it's not a big deal. I don't want to work on any important config files like my do-me-max config or X-mode-add configs or anything like that. This is just a directory of a lot of peeing images. So let's start by marking files. Typically what you want to do before doing any action, you're going to do M on the keyboard to mark a file for whatever action you want to perform on it. So let me highlight a file here. I'm going to go down to this file here, .files04.ping. I'm going to hit M on the keyboard. And now I have marked it. Marked it for what? Well, we'll get to that later, but right now it is a marked file. You can see an asterisk at the beginning of that line. It's letting me know that that file is a marked file. I can go down here to .files06.ping, hit M on the keyboard, and I've marked that as well. And maybe go down one more to .files09.ping and M on the keyboard for mark. And now that they're marked, I can run any command as far as moving, deletion, compressing the files, uncompressing the files. You know, whatever it is I'm trying to do to these particular groups of files that I've marked. I could now do that. Now I've marked them, but sometimes you mark a file and then you decide, you know what, I didn't mean to mark that file, or I've changed my mind on what I was wanting to do. How do you unmark a file? Well, you to unmark. So just highlight the file that you made a mistake on and you unmarks it. Or let me do M to mark that again. What I could do is simply do a shift U, capital U, right? And that unmarks all the files. Now I would have to start over again, marking the specific files I wanted to work with. Another really cool thing you could do is you could mark all the files you don't actually want to select. So maybe I wanted every file marked at CIP369. Well, the easiest way to do this would be to actually mark .files369. And then after that hit T on the keyboard for toggle the mark, which means basically do the inverse. So everything I didn't have marked is now marked. Everything I had marked is now unmarked. So that is a really cool little keybinding. T again would invert that back to the way I had it before. Shift U unmarks everything. Now when you're working with a lot of files, sometimes you just want to mark files based on a particular search pattern or a regular expression, things like that. One neat little keybinding that you'll use all the time for marking files is the asterisk symbol followed by the period. And what this does is it marks files based on an extension. So you can think of asterisk and then the dot as being the dot as part of the extension. So think of .png, for example, is what I'm searching for. And if I do that, it marks all files that had the extension .png. Now let me do shift U, capital U again, to unmark all files. Again, asterisk and then the period for the extension. And if I was searching for HTML as an extension for file names, I'd hit enter. And of course, in this case, there's nothing in this directory that has .html as an extension. It's all .png files. Now let me go back up a directory. So I'm just going to hit H to go back into the home directory. And I'm going to go into .stump.d. This directory here, it doesn't have very many files in it. Let me also zoom in in this buffer as well. Another cool key binding you can use is the percent sign M. Percent sign M means mark files based on a regular expression. For example, I can do a regular expression for, I could just do anything. I could search for the pattern log, for example, because maybe the file I'm really searching for is anything that ends in .log.log. But if I search for that pattern, of course, I get two files because I get this that matched the pattern and then stump wm.log.1 that also matched the pattern. So this is where regular expressions would come in handy because now I could do percent sign M for mark using regular expressions. Except this time, let me actually do a backslash period because I want to escape a period because I want that as part of the expression. And I'm also going to add a dollar sign here, meaning the end of the line. So search for .log at the end of the line. So that should eliminate the file that has .log.1. If I search for that, it says zero files marked because I already had the files marked from the previous time I ran that. So let me actually do a capital U to undo and then percent M for mark files with regular expression. Let's try that again. So backslash.log, dollar sign, and now you see it actually marked the one file this time because of the way I used it with that regular expression and it no longer marks the second file, the .log.1 file. Now what exactly are we going to do with the file or the multiple files that we might have marked? In this case, I've got one file marked. Well, I could do capital C for copy. So shift C. And where's it going to copy this to? You could specify a location by default. It's going to default to the current directory, which is fine. And then I could just give it a name, stumpwm.log.2 and again, it just copied that to this new location, which essentially is a new file with a new name is how that worked. Now let me shift U, capital U to undo everything. Now this file here that I just copied, this was just for test purposes. So I could M to mark and then I could capital D for delete. And it's going to ask me, do I really want to delete this file? You can see, do I want to trash stumpwm.log.2? Yes or no? Why for yes? And it asked me to trash it is because I've got my config set up to where it actually sends my deleted files to my trash bin rather than just permanently deleting them. So this is a safety mechanism. You want your file managers typically to send deleted files to a trash bin because sometimes you do make mistakes. And how I accomplish that trash bin, by the way, is in my DRID section of my config, somewhere in here. Let me scroll down. Have this section here. Making deleted files go to the trash bin. So I run set Q and this variable here, delete by moving to trash and T for true. By default, unless you have that set to true, it's probably going to be set to nil. Meaning anything you delete in DRID is permanently deleted. So just make sure that variable is set to true. And then you need to specify a trash dash directory, which on your Linux systems typically is going to be home directory slash local slash share slash trash with a capital T. And in my case, I'm sending it to slash files within slash trash. Now that's kind of a lengthy path to navigate to if you've trashed something and then later want to undelete it, right, to get it out of the trash. Sometimes you don't want to have to travel four subdirectories into your home directory. So for convenience, you see I made a note here, you may want to create a sim link to that trash directory in your home directory just for convenience.  It's actually really dot local slash share slash trash. So if I hit enter, it'll actually go into dot local slash share slash trash. And then if I go into slash files, these are all the files that are currently sitting in my trash bin that I could, if I made a mistake, I could go in here and get them out if I needed to, but everything in there is actually deserving of being in the trash at the moment. So let me do a search and back into the dot stump wd directory. Let me go up here and let's actually mark that file one more time for something. And let me do a copy. So I'm going to do capital C again. I'm going to do stumpwm.log.2 to get that copy and then capital U to unmark it. And then I'm just going to do a m to mark that new copied file. And this time I'm going to do capital R, so shift R. And this is for renaming. And what I could do is I could do stumpwm.log.3 and hit enter and you can see it renamed stumpwm.log.2 to .log.3. So very similar copy and rename except copy. You can make a copy and still keep the original rename actually takes the original and renames it. And of course what I've done with copy, rename, delete. You could do this on multiple files if I had multiple files marked. Same thing with rename. I could move multiple files to a directory. As a matter of fact, why don't we actually try this? So I've got this .log.3 file marked right now. Let's go ahead and capital R for rename and this time I'm going to rename it to a new subdirectory. I'll call the subdirectory test slash and then stumpwm.log.37. And it's going to ask do you really want to create this new subdirectory that was part of that path just in case you made a mistake, you know, for safety reasons. In this case, I actually do want that directory. And now we have this new directory test. If I go into test, we have that renamed file, right? Stumpwm.log.37. If I go back up the stumpwm.log.3 that was here is gone because a rename is essentially a move, right? So that can be kind of confusing for those of you used to using file management typically in the terminal, which is where I spend most of my time. A rename is actually move, right? MV, but in Emacs and Deer-Ed, they call it actually rename. So just know rename, move, they're synonymous for what they do. One last thing I want to show you is I'm going to mark the test directory and, of course, that directory has that one file in it. And now I'm going to do capital Z. Think of capital Z for compression. Capital Z is going to ask me, do I really want to compress this test directory? I'm going to hit Y for yes. So you can see I've got the original test directory. Now I have test.targz. Now, I actually don't want any of these directories. So let's go ahead and mark both the test and the test targz file and do capital D for delete. It's going to ask for confirmation Y for yes. And it's going to ask, do you want to recursively delete the test directory because there's stuff in it? Also, yes, so. And now this directory is back to looking the way it was before I started the video. Now let me go back into the home directory and I'm going to go into my Xmonad directory. So let me go into home slash dot config. So that is an invalid search. Let me just do space period to do find file because it's got tab complete inside find file and it's just an easier way. It still gets me to that dear ed buffer, right? So here is my Xmonad directory. Now, imagine this directory, I've got a bunch of files here, but maybe I don't want to actually see all the files and that could be the case if you're working in a large directory that has a bunch of stuff, but maybe you only need a small subset of files that you're working with today.   You don't actually delete anything. It's not going to delete files or directories or anything like that. It just hides those lines. It kills those lines. So for example, maybe I only want to work with my Xmonad config file, which is really the readme.org and maybe the Xmonad.hs and everything else I want to get rid of. Well, I could mark all of these. So m, right? Go ahead and mark all of these. And then if I do meta X, there is a command called dear ed do kill lines. If I hit enter, those lines go away. All those files, all those directories that I didn't want to see, they're no longer here. Now they're not deleted or anything. Again, it's just hiding those lines. If I want to get those lines back, I could just revert this buffer, refresh this buffer. And how you do this, and this is not a dear ed specific command. This is a general evil mode command. Anytime you want to refresh a buffer inside Doomy Max using the evil bindings, gr for revert buffer. So gr goes back to the buffer, refreshes it essentially. And now I get all of the files and directories displayed again. As a matter of fact, I think that dear ed do kill lines command is so useful. Instead of having to do meta X and executing the command from the prompt here, I should actually bind that to a key binding because it is actually not set to a key binding by default inside Doomy Max. So let me go to my config. And looking at my config, there are some standard bindings that were already here. These were not things I added. These are default Doomy Max bindings. But I don't necessarily use this one. For example, the key binding, the dash, the minus symbol for dear ed up directory, going up a directory. Well, I already use H for that, right? H, J, K, L. I'm never going to use the minus sign for going up a directory. I've never used that. So why don't I change that? Because I think that makes sense for killing lines, right? Minus making lines go away. It kind of makes sense for a key binding.  And then I'm going to write that. And then inside Doomy Max, space H R R to restart or reload your Doomy Max config that you've made changes to. And it says config successfully reloaded. So let me go back into this dear ed buffer here.  So let's see if that works. So I'm going to mark these first three directories. And now let's see if the minus symbol actually kills the lines. So minus and they go away. And again, if I wanted those lines back, G R to revert buffer. Very cool. And let me hit H to go up into the home directory again. And this time I'm going to go into my wallpapers directory here. So let me hit Enter on that. And if I wanted to get a preview of images because a lot of people want image previews I could do just like I did on the files earlier with meta return. So alt return, right? Alt return. I'm going to get that split with that preview, right? And I could go down to some other image and do alt return and get the preview for that. But sometimes you want the actual preview to actually happen just as you change through the images because a lot of people just want instant image previews. And I actually do have a binding for this. First of all, let me do space ww to get into the split over there then space wc to close that split. And let me show you in my config. This section right here, I have a program installed called peep-deer-ed. Essentially peep. You can think of it as a file preview. And I have these binded to leader key space, right? Space dp to launch peep-deer-ed and space dv for leader-ed view file. And then once this is actually opened, just navigating with j and k through the directory structure will actually just give you the image previews. Let me show you this. So if I do space dp, you can see it opens that preview, that split. But now just navigating with j and k up and down the directory structure here. So if I go down to the next image with j, right? I'm always going to get that preview immediately. I don't have to worry about alt return. And if I wanted to turn that off, space dp would kill that because you wouldn't want that on all the time, especially if you're constantly navigating through a lot of images because it's going to open up a million buffers in emacs. And it's going to be very cluttered when you go and look at your buffer list. As a matter of fact, let me show you space bi for iBuffer inside doom emacs. And I'm going to have a lot of stuff that we have previewed earlier. I've got several of those scripts that early in the video I previewed are here. I've got one image preview it looks like here as well. And of course from iBuffer, you know, I could delete some of these buffers, kill some of these buffers. But for now, I'm just going to let them go. iBuffer was really not the focal point of today's video. Today was all about Dear Ed, the file manager inside emacs. And I hope this video, the short little walkthrough of Dear Ed inside doom emacs, helps some of you guys. I know some of you guys just now trying out doom emacs for the first time. You're kind of wondering how this thing works, right? It's a different kind of experience where you have pretty much all of your applications that you work with. Your text editor and your file manager and your terminal emulator or your email client and your Git client and all of this all in one program. And sometimes it's kind of hard to conceptualize how all of that stuff fits together. So I hope today's video helps some of you guys out. Before I go, I need to thank a few special people. I need to thank the producers of this episode. Dustin Gabe James, Matt Maxim, Mimit, Michael Mitchell, Paul West. Why you bald homie? Alex Allen, Armoredragon, Chuck Commander, Ringer, Yida Yokai, Dylan Greg, Greg Marsh, Drummer, Erjan Alexander, Paul Peace, Archon Fodor, Polytech Realities for the less-read profit Steven Thules, Devler, and Willie. These guys, they're my highest-tiered patrons over on Patreon without these guys. This quick look at the Dear Ed file manager inside emacs would not have been possible. The show is also brought to you by each and every one of these fine ladies and gentlemen. All these names you're seeing on the screen right now, these are all my supporters over on Patreon. I don't have any corporate sponsors. I depend on you guys. If you like my work and want to support me, subscribe to DistroTube over on Patreon. All right, guys. Peace.


two frogs fell into a well but when they realized just how deep the well was and that they wouldn't be able to climb out on their own they started to shout for help very soon all the frogs in the forest had gathered around the top of the well but when they too realized just how steep the sites were and how deep the well was they realized they weren't going to be able to help their friends down there and so they started to shout down to them saying we can't help you there's no way that you're going to be able to climb out of there you may as well just die now you may as well just give up your life because there's no way that we're going to be able to save you now one of the frogs heard what they were saying and he got so disheartened that he actually died right there and then but the other frog was slightly hard of hearing and he thought that they were trying to encourage him and so he managed to clamber out of the well you know I was just thinking how much responsibility we have towards ourselves what we decide to hear is our choice what we decide to do is our choice how we react is our choice and yet we are at all times surrounded by so much noise that we cannot even hear what we ourselves are thinking in order to make those choices and so for me the moral of the story is we all need some deaf time we need to switch off our phones we have to shut the door to every single person out there and we have to turn off every form of noise so that you can just learn to listen to your own voice


Tena koutou katoa. Tadai am gana bai, as Fee said, am gana bai discussing my experiences during my PhD, building large corpus based on the official online version of the New Zealand Parliamentary Debates or Hansard, as well as an insight into the narrow institutional politics of Parliament and political elites. As a researcher, I'm interested in the parliamentary record as a lens of society, culture, history and ideas. Why is this talk maybe relevant to folk in Glam? For those involved in research on their collections or working closely with researchers, you might be interested in the corpus itself, but maybe more so in the methods that I've used. For people involved in putting collections online and content online, you might be interested in some of the hoops that researchers have to jump through and repurposing digital resources and take this as encouragement to continue engaging with the research community in this work. I'll explain why there's a radio in a bit. So first I'd like to say thanks to NDF for having me and a big thanks to the University of Canterbury for funding my PhD research with a scholarship, my supervisor is Bronwyn Hayward in political science and Kevin Watson in linguistics and my lovely colleagues at the Arts Digital Lab. Representatives from the lab talked yesterday about the project's understanding place and the lab works closely across the humanities, social sciences and fine arts at UC and the strong links to the Glam sector. A bit about myself. I have a professional background dating back to 2000 as a software developer, working with web-based applications and web technologies around a development shop in Christchurch. My work on Hansard was part of my PhD research and in the post-op position I'm going to be continuing to develop this and apply to build other stuff and apply digital methods for new research. That's a bit about myself, but the idea of speech with data I'm going to get a green MP to introduce this idea, so hopefully the audio works. Basically this is a speech with Kevin Hague and the House representatives and he quantifies the use of the word economy, the word growth in businesses and speeches by the National Party over time. He makes this point that John Key isn't using the words climate change, isn't using the words poverty and I want to use this as a way to introduce the idea of using speech as data, getting it kind of quantifying and counting it. Oddly enough in my research I was studying the use of the word economy and I was applying methods developed by Corpus Linguis. Corpus Linguis is according to the classic definition of it the study of language based on examples of real-life language use. A Corpus is a collection of a lot of texts, examples of language use collected together in a standardised format but there's no stipulations about that really. But in a way that can be processed by a computer for analysis and maybe enriched with further annotation. A basic claim of Corpus Linguistics untie my tongue. A basic claim of Corpus Linguistics and a lot of digital methods is it's a way to surpass your intuitions about the data you're dealing with so there's no meaningful patterns within it. So I was interested in pervasive patterns of use of a word-like economy and to place it in perspective by drawing comparisons. So a bit about the PhD research that this was part of. This combined political psychology and Corpus Linguistics to examine the use of the economy in the wild. And by wild I mean parliamentary debates and I built a large Corpus of 1788 hours of talk-back radio. I didn't listen to all that but I had some software listen to it. There's a body of academic research that's concerned with lay economic thinking and past research has been often conducted by economists and economic psychologists and they focus on demonstrating the ways in which lay people deviate from the judgements and knowledge of economists and they typically see that as a problem. Or, you know, on the other hand, this tends to be the psychologists. They use interviews and surveys to attempt to uncover hidden structures within our cognitions about the economic sphere. Instead I was focusing on observable language in these contexts, connecting public thinking about the economy to the context of political arguments and ideas and studying common features of argumentation to provide new insights on lay thinking as a kind of public thinking. So I'll talk briefly about the Corpus. Here's a photo of my son reading a volume but next to him there's a wall in the political science department at Canterbury of almost a complete set of the print volumes. Racing forward to kind of the present, obviously we have an online version of this and the current parliamentary website contains debates from 2003. At the time I started looking at the online Hansard in 2013, it was quite slow to search and really wasn't conducive to cutting up in the kind of way I wanted to for my analysis. So my first instinct was to look at how it could be repurposed. So here I've got a representation of the source of the HTML and within it you can see a bunch of markup, marking particular kinds of speeches, there's indications of timing, even like the page that this would relate to in a print volume. The speakers are represented in a common way so I thought this would be conducive to cutting up in some way. I'm not going to go into a lot of detail about that but essentially the way a lot of people would approach this is to use an XML parser and use that as the groundwork but there was a lot of inconsistency in the way that it was represented well formed in places. I hope no-one from Parliament's here. But obviously over a 10-year period which in 2013 I was working with there's things changed over time, the way that things were being marked up over time. There was a period of a week where it looked like their system went down and they were cutting and pasting from Word documents or something like this. You find all this stuff out when you scrape. So at the end of the software-driven process to cut this thing up there was a database containing all the separate utterances and procedural text coded with the debate that were from the type of debate, the date of the debate and who was speaking and their party and there was an additional stage of processing to make searches and comparisons very fast. So I updated it in 2016 and this is what I used for my analysis. So there was a 13-year period covered 57 million words, almost 400,000 utterances and 261 speakers represented. So I built a tool that went along with this. This is what I was hoping. Okay, and similar to what Tim was saying this is a rower working thing, I developed it enough to do my analysis but something I want to do through the postdoc is release a public version of this for the public and researchers. So I'll demo some of the basic browsing. I thought I'd pick on librarians. So this is the classic call for linguistics tool. When you search the keyword is in context down the middle and you get to see some text either side of it and this is the basic interpretive tool that even if you're using high level quantifications you're still coming back to this to check the robustness of your interpretations. So I'll pick out one that I quite liked. So you see when you click one of these lines it races to the point in the debate. May the rage of a thousand librarians rain down on the heads of the National Party members. I'm sure there's probably some people in this room that would agree with that. Sorry. So part of the tool is it allows you to expand out the context to see things in the context of debate. So in question time interactions you can see the sequence of turns what people are responding to and so this was a basic move by the kind of corpus work I was doing is to look at levels of analysis, look at these big quantifications down to the actual utterance level. One other thing that's quite... So I've made it so that you can highlight specific text in there in the document and it'll create the concordance for that. So I guess kind of similar to what Tim's doing, he's annotating the text with linked open data this is kind of a way to think of it as annotating the text with itself and kind of seeing context across the corpus, across lots of examples of usage. At this point it's good to acknowledge that Tim's actually done some work on this. He's built a tool for 80 years of the Australian Parliament and there's other people in the UK, the Hansard at Huddersfield project trying to make this more useful for researchers and more accessible for the public. What can researchers learn? What can we do with this? So I'm going to take the case of economy and talk about some of the a small part of my research. Firstly, in terms of use of economy we can quantify its use over time and compare it and here I've got this graph shows the average patterns of use by three different parties and aggregated over different parliamentary terms and it's an average over every thousand words so that you can directly compare them and we can reflect back on what Kevin Haig was saying and the thing I couldn't play was he was talking about the use of economy by the National Party and obviously in the period from 2008 there's a financial crisis and a change of government. It is a very noticeable feature in comparison to the other parties it increases dramatically but interesting also before this 2008 period National comes behind Labour and the Greens in their use. In addition to this example for my research we can look at co-locations or words that predictably occur in a limited span with economy and here I'm showing words that co-locate across sentences across the whole corpus so you might expect words to do with growth it gets more interesting when you compare parties on this so you'll notice the two major parties have highlighted the common words between them and particularly top five words. I talked about a shared vocabulary or shared language related to the economy and also this I dominate an idea of growth and to be able to quantify this assumption that's kind of prevalent in this kind of speech the National Party members when said growth or one of the other grow words once in every four sentences Labour parties use grow words once in every six sentences where they mention economy the Greens in contrast mentioned it once every 20 sentences and this was often in a critical sense in addition I was quite interested in this word our because this is our economy the academic literature is focused on the emergence of this idea of that economy as a kind of a separate abstract independent entity that we do things for in our politics but along with this kind of abstract thing that politicians were appealing to they're also appealing to our embeddedness the embeddedness of the economy it's for people in the end so I've mainly talked about language but and moving away from the economy there's other things you can kind of take from this data grass of this kind can't be, there's no data to do this kind of stuff at the moment so this is looking at Green Party votes across years and the percentage of yes, nos and abstentions and you'll see under Labour they're tending to less more under national vote no more but there's still this kind of strong no voting under Labour which is quite interesting given they're in coalition now also, I mean we often talk about representation in parliament and equate that with who gets to speak and who has a voice so using this data we can look at who actually gets to talk across parties, across genders and so on here I've picked out a party that I've written a bit about the Greens comparing 2006 where there's quite an equal share of speaker allocation to 2012 where there seems to be more of a hierarchy and these are patterns that aren't easily insurable from just listening to parliament okay, so what are the opportunities the key the key opportunity I think is to extend the span of the corpus so I've stopped in 2016 when my analysis ended but obviously there's this interesting period recently with a change of government but there's other sources of Hansard now going back to the earliest volumes there's been scans made available by the Hathi Trust there's a prior mirror of previous online records prior to 2003 and I've recently noticed that there's some Google Docs link from the wiki that look kind of official as well though I'm not sure of where they come from in addition to this there's videos that could enrich the way that people interact with this kind of tool so joining these sources up and putting them into a comparable format across the entire Hansard record would have lots of research applications and it's a challenge I've been looking at for a while prior to the Hathi scans being available I piloted scanning and OCRing the debates myself and thankfully this isn't something I have to worry about anymore but I'll talk about the challenges there's a basic problem of changing reporting practices this is a problem that anyone working with Hansard needs to be aware of that there's transcription editing practices that change over time and that something researchers don't really know a lot about especially once we get further back in time second with different data sources there's different representation practices even just down to the way columns how many columns there are in the print version whether macrons were being used or in one case removed from one record one record source and how we might identify speakers and procedural texts within the OCR record itself so I've trialled using Bayesian classifiers to do this with some success thirdly there's just some basic errors both in bad scans then record and bugs in the online record which as I mentioned you probably only notice if you scrape it why should you care to put this another way what can librarians, archivists and others in cultural heritage learn from this part of my hope with doing this talk is to provide some interest in this form of analysis I'm aware that there's university librarians at NDF and I would love to hear from researchers and others interested in the form of analysis with Hansard or other sources I'm also keen to provoke dialogue with people interested in the possibilities of collaborating towards joining up the parliamentary record I have this rough idea of a wiki interface to crowd source improvements to the scans to find specific pages that are problematic and to correct the texts of significant speeches perhaps we could discuss this more in question time also I think it would be useful for folk in Glam to understand some of the problems that researchers have in repurposing data in the way I have especially as some of you will be involved with decisions about making stuff available many of you will be thinking well the answer is an API and if we build an API the researchers will come and this is something I've kind of been dealing with a digital NZ API recently which is great but it's interesting comparing institutions the quality of differs I was comparing for example dissertation records across university repositories six out of eight of these institutions said what degree the dissertation was related to two don't so that kind of leads me as someone who can code to start scraping that from the repositories himself beyond the whole builder and they will come idea of APIs researchers need documentation on how the records were created and the decisions involved in this this is things you'll know but this is something that probably by continuing the dialogues with the research community and this is perhaps an encouragement to continue these engagements so I'll leave it there, I had something else to play but that'll do we've got time for one or two questions any questions out there Tim's got one that's great Jeff I mean my question is sort of obvious and that's the possibilities of international comparisons because we have the Australian Hansard even though there's some licensing issues around it I think Canadian Hansard is available now so I'm wondering what you think what it might emerge if we can start to actually explore these different bodies of political speech across countries yeah I think that would be I mean the economy is interesting from my own research but I think this would be interesting to see this across in comparative kind of context and one other thing I've looked at the Australian records and I kind of played around with that and there are some problems of kind of comparing formats but yeah I think this is some people are already doing this kind of stuff I know I'm aware of some Canadian researchers that did stuff with European parliaments but yeah there's kind of a wide open kind of field really in terms of these comparisons yeah Kia ora Jeffrey you mentioned problems with documentation and the source and the markup did you think of contacting the officers of the Clark and asking them about the inconsistencies I did think of that but I'd kind of done it already and this is kind of the hacker thing is just kind of do it you know kind of solve the problems as much as you can yourself and I'd really like to talk to the Hansard team about some of the things I'd found with this I've found one little bug that I'm sure they'd love to know about you know it's yeah it's I mean it's just it's a big reflection on their work as well when you work with this for a number of years you see the amount of work that's going on to put this thing together so yeah Thanks Jeff Rowan Payne Digital NZ just to follow on from that previous question I just put it out there that also you know issues with with what you found through the Digital NZ API you know we can also work with that I appreciate that that's you know That wasn't a criticism at all I sent an email about something else and got a nice prompt reply so cool it's the nature of the thing my point is really that the API is kind of it's about what data you're exposing and how and research is shouldn't really I don't want to be constrained necessarily by the particular ways of classifying those records so I've kind of got the privilege of being able to code around it but I guess it speaks to how the APIs are what's being exposed Hi, I was just wondering how far can you filter it so you can do it by parties could you do by like individual MPs and analyse their specific language in use of words? Yes, yeah so I've done a little bit of work with this with John Key and direct comparisons with Helen Clark so there's kind of a particular speech that kind of belongs to prime ministerial roles and then it's working out what's different and yeah, this is something that I think you can do it with the Hansard search now is bring up individual speeches by parliamentarians but at the time I kind of kicked this off you couldn't and just being able to see all the speeches you know and decontextualise across time one speaker speech after another is quite useful is anyone from Hansard or the parliament here? Oh sweet, I'll talk to you afterwards Oh yeah OK OK I was going to ask exactly the same question because I had an inkling there was probably someone from Parliamentary Library or from Parliamentary Services in the room or at least NDF and I think by the number of questions you can tell that you've got a pretty engaged audience and I can think of several people some of whom are in the room who you need to talk to so hit me up afterwards and yeah, really exciting work and yeah, there's some people for you to meet OK everyone it's lunchtime, can we ho mo te pake pake for Jess?


Live from Boston, Massachusetts, it's theCUBE, covering OpenStack Summit 2017, brought to you by the OpenStack Foundation, Red Hat, and additional ecosystem support. And we're back. I'm Stu Miniman with my co-host, John Troyer. Happy to welcome the program, first time guest, a non-Christian who's the EVP and general manager of Cloud Insight Canonical. Thanks so much for joining us. Thank you. All right, so we had Mark Shuddleworth on this morning talking about how it used to be kind of three groups. And now there's kind of two main groups of the focus. You know, I think he said Ubuntu, winning everywhere. Of course we expect the man who's stepping into the CEO role to give that positioning. Most people I talk to know Ubuntu.  It was like, you know, VMware desktop all over the place. Every, you know, person that uses Linux absolutely uses Ubuntu. Let's talk about cloud in your space. Where do you guys position yourselves? Where are customers using you? Let's start there. So a bit of background, as Mark says, three things that have sort of shrunk down to two. Canonical's origins were on the desktop. As a Linux for the desktop, as a Linux for developers. And that part of our DNA is as strong as it ever was. And so developers still, I think overwhelmingly, developed for Ubuntu on Ubuntu. And one of the target environments they would typically develop for is Ubuntu on the cloud, or increasingly Ubuntu on the edge. And those are the two sides of the company now. You have two divisions. I run the cloud division and Mike Bell, a counterpart to me, runs the IoT side of it. Now, if you think of cloud, for any, it's probably best to see this from a customer standpoint. For any of our customers, their data center has two sides to it. There's all the stuff they know how to do, which they figured out how to do 10 years ago or five years ago. This stuff has a lot of windows, my old world, a lot of Red Hat, a lot of VMware, and that stuff is just fine. And they have no desire to change it, other than keep it alive and keep it running. The new stuff, the stuff that fills their inboxes, is words like containers, cloud, infrastructure as a service, public cloud, hybrid, yada yada, all of that new stuff. That's the world which is evolving. It is a different class of software for them, and that's where they will find us more often than not. So, if you look in the public cloud, we were early to the public cloud. We didn't just treat it as yet another server, just virtual. We treated it as its own environment. And today Ubuntu will make up 70 to 80% of all the guest OSs on a public cloud, no matter which one you pick. We have relationships, we know all of them, we know we have relationships with about 35 partners in the public cloud space. And you'll find a similar mirroring as well of Ubuntu presence when you look at that class of workload on-premise. So, take Cloud Foundry, 90 plus percent of the time, that'll be deployed on Ubuntu, and a 70% of Docker out there runs on Ubuntu, as we see from the OpenStack survey every six months, something of the order of 55% of all the OpenStack out there, especially the large ones will be running on Ubuntu. We tend to be the default environment customers will go for as an operating system when they're looking at that new class of workload, containers, big data, et cetera. So, that's what the cloud division is really about, is helping people build first class, net new infrastructure which can be on-premise, it can be hybrid, it can be completely public cloud, we are indifferent to it. Our biggest customers, I mean just about anybody that you can think of that is a logo that you recognize the name of, the Netflix, the Uber, the Spotify, the Dropboxes of the world are all running on Ubuntu. Anybody you can think of with a Fortune 500 that is doing infrastructure scale is almost guaranteed to have significant estate now running on Ubuntu. So, that's the spread of the business and our journey if you will over the last five years. Great, that's quite a spread that you've got there. What's different in the cloud versus kind of where Ubuntu came from? I love your comment kind of about cloud, you know there's stickers, it's just somebody else's computer when you do there. Why is it, what's more to that? Why, what do you have to do special? Why do you have such strong affinity there? Our understanding of it has evolved because initially you're right and I've been in the cloud space for 10 years. It did start out as it's just somebody else's server, I just rent it now, I don't have to buy it. That evolves to, oh no it's actually, there are a set of things technically that are materially different when it's in a VM versus on a physical box and those are some of the first things that they did to a Linux distribution that nobody else did. Some of the reasons why Ubuntu became so popular in AWS was because we were optimized for it. Increasingly now, it isn't about the operating system, it's about the operation system. So I think Mark talked a little bit this morning. The class of software people are putting on these installations is just not your daddy's SAP installation or ERP system or CRM or some such. It is software composed of multiple pieces, typically integrated and configured per use specific to a custom user, scaled out across tens, maybe hundreds or even thousands of machines and with a chain cycle that is light years away from what you used to have. Nowadays we patch things every month, we upgrade them every six months and that is normal. Entities like an Amazon or a Google had to deal with this problem before they could deliver the services to deliver to us at scale. They figured out how to solve this 10 years ago. They did it at probably a massive cost but they all have internal infrastructure that runs a certain way. Most IT organizations haven't made that leap. They're still looking to operate an open stack the way they used to operate their legacy virtualization infrastructure. That is what is really new about this. Solving that problem will define the next two decades of how IT runs. And on its interest, we had theCUBE at both DockerCon and at Red Hat Summit and now we're here and you hear that whole containers are Linux, Linux is containers, who has the best expertise of course, where it all sits, what canonicals take on that container and who has the expertise, who's helping clients through all of this? Yes, so we've had containers as an option for a while. The bulk of our production open stack deployments are containerized and deploy open stack in containers. It's just something we never made a big deal of because to us it was just the way you would do it. Today there's a broader set of choices that customers have. Our conversation with customers ultimately hinges on the workload. Somebody wants to deploy media workloads fast, they have licensing rights that expire and they want to be in market in three months. They are indifferent honestly to whether or not that is done on an open stack or if it's done with Docker managed by Kubernetes, they just want it to be efficient. We try to deliver as many options to them as possible. So we've got large customers using us for open stack. We've got those same customers also starting to use us for Kubernetes. We deliver a distribution of Kubernetes that is supported by Economical. We don't bias the conversation one way or the other. And when it comes to containers, different strokes for different folks. Docker is great. We are one of their biggest partners. The vast majority of Docker deploy on us. We resell Docker and sell large deals to customers that will stand behind the installation and Docker is right beside us.  They want that VM to run faster and more of it on a single machine. The answer to that looks like Lexity which by the way, yes, happens to be a container. But that's kind of besides the point, they're looking for a better VM. So it isn't just about containers versus something else. We think VMs to different types of containers are all options. And the important thing is for customers to be able to have a choice and to change their minds about that choice. I love the way that you talk about this in a multi-valent way, in a multi, it's a multi-cloud, multi-platform world. It doesn't really matter, right? The customer at the end of the day, the business owner wants to be up and running and be able to change quickly. Yeah. I want to talk about buying center and design center for a little bit. In the olden days, infrastructure folks got to talk to the infrastructure folks and the sysadmins and we didn't really talk to the developers and that sort of, those sorts of people. Right. You know, Ubuntu, like as we started, right, long history working with developers. Yeah. When you go in and talk to a CIO right now, who's at the table with them? Are there, is it ops? Is it developers? Is it both? I mean, how are they looking at building this stuff? Yes. They have to, let me give you a few cases. It's probably the best way to illustrate it. We see a lot of organic Ubuntu because developers love us. It'll spin up as something that is a POC and it'll become production. Walmart is a large customer of Microsoft and of Red Hat and I'm sure VMware's as well. They're a very large customer to us. All of walmart.com runs on Ubuntu. That was not a decision we coaxed Walmart into making. That was made without us in the room. When they reached out to us, they were already running thousands of nodes of Ubuntu and Ubuntu OpenStack and powering the website with it. And that was the basis for the commercial relationship we had. Since then, the operations guys have told us that one of their biggest problems is bare metal provisioning at scale, which is something we happen to do very well in our tooling. So there's an ops conversation that expands beyond the original scope. So that's a good example of that kind of organic. We see a lot of this in the public cloud, certainly. Anybody large in the public cloud is almost certainly doing Ubuntu. They got there without asking us, but now they're asking us for specific set of things that matter at that scale, we can solve it. All the way at the other end of the extreme, you get telcos, big monstrous projects that are defining the next generation of telephony, big RFP process, everybody comes to the party, it's months before you kind of get to that process. There it is absolutely a IT and business led conversation that checks all the boxes. One really interesting thing across all of this, and speaking on the customer side now, if you go into a Spotify and ask them if there is an IT department versus a business division, they're probably going to look at you funny. Most legacy enterprise IT, enterprise organizations are figuring out now that they're all software companies. And so you see this a lot in telco, where our dialogue is not just with IT, with infra, it is just as much with the business guy that owns monetizing telephony, but now it relies on deploying telephony as applications on a cloud delivered by what used to be a service and is now a partner to him. They are both at the table, both dictating demands and very willing to go off and do their own thing if the other partner doesn't cooperate. That blurring at the line between business and IT is I think a necessary dynamic in the market. It is what allows ultimately a sky to compete with the Netflix in the longer run. Yeah, it's a fascinating discussion. I remember I think four or five years ago we did like a big info graphic on the changing role of the CIO. And it's like as cloud comes, are they a broker, they have some inside, some outside, that they handle a whole lot of this. You know, you could get a comment a little bit more. What do you see the role of the CIO going forward? You know, business versus CMO versus, you know, the application and the IT people? No, let me tell you a story. So Mobile World Congress earlier this year, Deutsche Telekom, one of our biggest customers, they were one of the first large telcos to start the journey into NFV, network function virtualization, which think of it as telephony done in software versus black boxes. DT has been a big partner to us, we're very much involved in that project. It is a monstrously complicated multi-country engagement. They invited all of the entities selling them applications that are part of the project to basically an open meeting at their booth. And there must have been about 40 people sitting in the audience. And up on stage was initially the head of the whole project, but subsequently two people. One heading up in for, and the other one more responsible for the business side of it. And they collectively had a single message back to the crowd, which is all about how the software ecosystem needs to iterate its own business models in order to meet the business need. Someone needs to roll out a new service in a country and needs to do that across four countries now. You are not going to have completely different procurement processes for each one of those. That's a requirement of the software vendor. In that conversation for me, without the titles, it was really difficult to tell whether I was speaking, hearing from the business guy or the IT guy. And that seamless side-by-side engagement is to me very much the kind of template I think most CIOs need to start thinking of. It isn't about being a broker. That world is gone. You absolutely have to be a partner and in some ways quasi-owner of the business. You know, WhatsApp has done the telephony. 32 engineers servicing 500 million users. You don't get that in a world where somebody owns the user and somebody else owns the infrastructure. Narn, you talked about that. Cloud Foundry tends to be on your platform a lot. Some of the other services. What's your talk about business and technology? How about the application and the infrastructure? Where does kind of that application modernization fit in with Canonical? How do you help customers? Or is that mostly through partners? Yeah, so this kind of goes right to the back of what I was saying earlier about operations. Nobody's building a cloud just to have one. They want to run stuff on it. The core, the real learning lesson for the customer comes when they start using their cloud to deploy things on top of it. Making that easier. The vision is that you'd want somebody to take components off a catalog, stitch them together in a way that makes sense for that user, and then deploy them to one of many target environments. That's what you want. What you have in practice is I'll put a change request in, a bunch of forms get filled out, some scripts get deployed. That is only specific to this one environment. You've changed your mind under that's too tough, that's another three months, that's to an RFP. That is the world we live in. This elegant model-driven user-initiated process is what we want to get to. The heart of that is where we think IT has to go from being run by people to being run by software, being run by a model that is designed by people. That's how Amazon runs their data center. That's what every organization has to do. And the heart of it, what you're really doing is not building infrastructure, but letting people deploy applications on top of it. That model-driven approach is at the heart of what we do, and it goes beyond just having Ubuntu. It's really about the tooling around it. All right, Anand, what conversations are you having with the users here? What's their state of mind? What would you want to share with our audience? So here, and this has been the case to an increasing degree in the last two OpenStack summits, my first ODS was two and a half years ago. This is my, you know, fifth one now. Two and a half years ago, it was very difficult to explain to somebody why building a cloud was the easy part. The really hard questions were, how many people does it take to run your cloud? A great answer would be one or two. A good answer would be four or five.  Many customers would tell you it's 15, 20, 25. It is very difficult to explain why headcount cannot scale with server count, why operations has to run on an economic benchmark set by AWS, like that is what you should be comparing yourself to in cost per cycle. Now we find two conversations, two types of conversation. We've got the customer that tried it the old way, has stopped the project after phase one went live and is now back and they want to do it the right way. And we're selling into customers that we didn't succeed in selling into two years ago. That is one class of customer at ODS. And then the other end of the spectrum, we get the customer that comes up and says, I want to do this, it's got to be on premise. Honestly, I don't care if it's open stack or not. I just want it to be done as a service and done quickly. For two years now, we've had a service called Bootstack. Build, operate and optionally transfer an open stack. It's a managed open stack. They just care about the workload functioning and they just want that delivered on a timeline. And those are the two. So in one case, it's very much, I love open stack, but I've learned what not to do about it. In the other case, it's very much a, I just want this done as a service. I want IT as a service. Can you make that happen for me? You talked about moving application development, old school, new school, the same conversation does also happen in public cloud, on-prem. Are you, as canonical, obviously works well with both, right? Partner with all the big players. It's still a Windows world and part of the world. I mean, how do you see your customers adapting to that? Are they, it seems to be hybrid, multi-cloud. I mean, is that a real factor in 2017? So I guess we see, there's bleeding going on in three directions. You can take your core infrastructure and throw it up into the public cloud and get hybrid. And we see a lot of customers. A lot of our public cloud customer base started out small, entirely on the public cloud. We'll then get to a size where it makes sense for portions of their infrastructure to come off and run on-premise. Box is a customer of ours, as many other logos, that did that last year, right? They came off of AWS for a portion and they're truly hybrid in how they run. That's one way, sort of, you think about both balance. Here's where Netflix didn't start out on Ubuntu. They were on Amazon Linux. Back when Amazon Linux was the default Linux on Amazon, they took the effort to port to Ubuntu. One reason is because we do a set of things that keep them at a cutting edge, but one reason is also because it gives them the flexibility then to be truly hybrid in their choices. And that's important. So that's one choice you see, and there in both the tooling, but also having a consistent experience across on-premise and off, is very important to the customer. It's important to us as well. The other kind of thing you see then is laterally, where someone wants to keep OpenStack, but they also want to give that customer a bare metal option, because the drill performance runs on bare metal or a container option. Multiple substrates is how we think of it. Right now, those look like independent projects. What we're trying to enable for them, what we do with JuJu, is the ability to take that workload and decide at deployment time where you want it to go and make that truly seamless behind a single-painter class. That's what the model of it allows you to do. Those two, everybody talks about. The third one, the most nascent one, and the most interesting one in some ways, is the spectrum from that data center down to the edge. So take a telco. Yes, I've got lots and lots of servers and I've got applications deployed. I've also got a different type of server. It's called a set-top box. It just happens to be a server because it's really got that much compute in it. I've got this spread out across millions of households, and right now it's sold as a dumb unit which comes to you and gets upgraded once every two years of the firmware. You want to put apps on it and configure those apps and treat them just like you do a server. That is a different class of infrastructure. There's no reason for that class of infrastructure to be treated differently from the one that's in the data center. And again, Ubuntu Core is how we think of that as a platform and the management of it to us, it's in the same class of problem. So would it be too much to say you'd like people not to think of Ubuntu as an operating system anymore but as a set of platform and services that can give you a consistent application environment in all these different areas you talked about? That's a great way to put it. We think of it as an operation system for at scale infrastructure. That to us is the defining problem in IT for the coming decade. A Linux operating system is absolutely a great part of it but it is a part of the solution. All right. And on Christian, perfect place to end there. Thank you so much for joining us and we'll be back with more coverage here from the OpenStack Summit. You're watching theCUBE.


What's up everybody, Jason here for jazzyinforjasmiescasebrakes.com sells off the mixer with this one here five spots even away the last five spots 2019-20, Kenini, Mosaic, Cello, Pack Break 306, Random Team. So again, Randomize customer names teams to distribute the hits out of the Cello and then at the end of the break we'll randomize the customer names again in a separate dice roll randomizer top five get the last spots in the Mixer and that'll be coming up next Let's do the break first roll it is a 3-0-1 for four times one two three and four Aaron down to Chris four times here one two three four Grizzlies down to the 76ers Aaron with the Grizzlies, Marlon with the Thunder, Jeremy with the Pistons, Aldo with the Lakers, Jeremy with the Wolves, John with the Hawks, Jeremy with the Wizards, Aaron with the Hornets, Chris with the Nets, Mark with the Warriors, Marlon with the Heats Tony with the T-Wills, Steve with the Pacers, Quinn with the Nuggets, Marlon with the Kings, Chris with the Sun's Knicks, Adam with the Cavs, Mark with the Magic, John with the Blazers, Danny with the Jazz, John with the Raptors, Quinn with the Bucks, Gordon, Osmojo Mavericks, Ryan Shackleton with the Rockets, Ace with the Celtics, Matthew with the Pelicans Matthew with, sorry, Adam with the Spurs, Oliver with the Clippers and Chris with the 76ers All right, let's close the trade window see what you got or stickle what you got and then um, we'll see who wins spots in the mixer at the end Jeremy Grant, Dee Lill, Kobe White for the Bulls going to Jeremy Let's see who wins the last five spots guys, good luck Let's roll it and it's a one and a three four times Good luck One, two, four times Top five, get in Matthew, Jeremy, John, Chris and Quinn after four times, three and a one Congratulations guys, now in the mixer, coming up next is the mixer