I'm Jessica Hartenberger and I'm the head of people here at Super Office. So we recently launched our early career program, it's the first time we've ever done it, and it's a program for young aspiring sales associates. And we give them this five month program where we give them all this information and knowledge and training and introduce them to Super Office and the way we do things in a five month period so that they can kickstart their career and account management with us. One of the cool things about the early career program is that you get insight into different areas like Super Office as a company, but also intense training in our product. You also get other skills that are important in your job, like presentation skills and other things. And then all this is mixed with on the job training. It's like a crash course into how we sell in our product and you sort of get all the training and tools you need and you get to meet a lot of our great colleagues along the way and you really just get sort of embedded into the company quickly, which of course could happen in any job, but this is sort of like there's a more focus on getting them up and running fast. We've had a full program and I think the associates would say that their heads are full but that they've learned a lot and I think they feel like they have a good overview of how this job is going to be and our product and our people and all those things. We went out for dinner and we battled each other and shuffleboard so that was also fun to get in some social time as well, to get to know each other and for the associates to start bonding because they come from different countries, it's like a sort of created team. At the end of the five months they'll have sort of a presentation to kind of put together everything they've done and show us what they've learned. And then they'll start the new year in 2023 as account managers and have that full year to look forward to working as a full-blown account manager.


Matthew Anthony Cotter-Bober is the Chief Executive Officer of Cox & Company Limited, a family-led enterprise with rich history and many roots in the development of the tourism product of St. Lucia. Mr.Bober was instrumental in visioning and developing St. Lucia's cruise industry from the late 1980s as he's always looked at St. Lucia's competitive advantage and brought to life podcastries which saw the eventual rise of multiple secondary ports in Rodney Bay, Suferet and Marigold Bay. He developed what St. Lucia had as its offerings to sell to the cruise companies at the time and today, much of the success and bustle of the cruise industry St. Lucia enjoys today stems from the work and vision of Mr. Matthew Bober. More so, he developed and shaped the lives of several tour guides throughout St. Lucia. They have been recognized by many cruise lines as the best in the Caribbean. Started the golf program, active in promoting junior golf. Within two years, there was at least four juniors on the OECS team that Matthew managed. An active member of the St. Lucia National Trust, involved in promoting swimming in St. Lucia, worked with the Police Reform Committee, mentored several young entrepreneurs. Director St. Lucia Tourist Board 1989-1993, member of the Ministry of Tourism Advisory Council, chairman of the St. Lucia Tourist Board 2011-2016. Cox & Company was the leader in the development of the industry. Ladies and gentlemen, up in the category for the Lifetime Achievement Award for the inaugural Ministry of Tourism Jimmy's Mr. Matthew Bober.


Everybody forced here ripping Elite basketball Hang on I got the full title here elite basketball four blocks number six picker team style Alexander L with the Hornets Alvin S Thunder Anthony C magic Austin P. Bucks Ching Hua with the Warriors get it ship 927 Mavericks Gregory M with the Nets bulls calves nuggets and clippers Thanks for grabbing those last few teams Gregory Hilton T with the pistons young men with the Grizzlies Jake M Celtics Jerry J Spurs Jonathan F. Nick's Jung Hewn jazz Carl P with the Sixers Lee Juan with the Lakers Nathan wizards Nicholas Heats Pension Rockets Robert P with the Blazers Ryan B Hawks Raptors Scott T Pelicans Timothy M Pacers Vaughn as the Kings Victor with the Suns and Wen Long with the T Wolves. Good luck everybody. Let's do it Dude that's awesome goalie That's what's up. Maybe we got some present photo Maybe we just haven't gotten it yet. I don't know. I know we got some honors photo back there. We got honors. Well, I know that You got us onto the Kumball Bucks Only insert. This is Jaden Hardy rookie for Dallas. Yeah, we have iMac photo too Got lots of photos. I like photos Orange Doug McDermott Spurs Some of that that's for sure. Oh look at that dimensions Anthony Davis He just goes up and he just Do a jump. It's like a two-bit jump. He's like on a Nintendo Your time for you to join our stream, huh? What's this? Throw that down real quick It is a Elite signatures of Jaren Jackson jr. For the Grizzlies You go Grizz, I'm pretty aggressive right now, don't he PJ Tucker blue 1099 for the Sixers Orange to barry Walker rookie for the Blazers Guys Lane's not gonna be here the next few days John Moran full throttle orange for the Grizzlies full throttle Rookie Auto Thunder who's Monsyang rookie yearbook auto Personal could just go live on match channel, but all right respect James Harden power formulas for the Sixers I've been more comfortable in the gaming channel What gaming is this? Rookie Purple Jalen Williams at 49 thunder That's sweet thunder rats. Okay, see what if Brady's in a honors look at dodge it spell bounce What's honors This is like a product where they mix Some like rookie autos and like buybacks all buy back Isaiah Stewart pistons orange To encase and the pack of like two cars is how it was low two base cards Orange Tobias Harris for the Sixers Spellbound orange Anthony Edwards T Wolves Greaties and honors. Yeah fear. Yeah, cuz he was like older buyback. So I have to have the cars I wonder if they have a complete or if it's just kind of full throttle down a bit Mitchell's Yeah, it's all like just random like any buyback. I think as long as this panini, right? Shrey young Hawks Clarity So you see like Josh Allen. I was on some of his rookie cards out of like buybacks not not technically a rookie auto And sometimes they just have like Walker Castle rookie for the jazz Well, sometimes they just have the older cards not even like like the older autos already worse Not technically a buyback. It was just Orange opera and Shanyard Rockets. I think I remember seeing very rarely you would see like the actual Jordan pool orange for the Warriors now. He's an Emmons.  There we go thunder Thunder a crush in this break. Nice Chet for sure mag down Yeah, look at look at Donnie look at me knowing two basketball players like Wesley rookie to 86 for the Spurs with a Ding on the bottom, right? We'll send a box napper to the Spurs Pull the old Bart Scott, huh star status Kyrie Irving Orange star status Lamello orange Middleton Bucks. I don't believe we'll have any more series one breaks Krl impact impressions Eddie Curry bulls auto. I don't believe so Usually when a series one or series two comes out, we'll rip a bunch of it like the first like week or two and Usually not a whole lot more didn't we be purple number 11 out of 49 For the Mavs Orange rookie Walker Kessler jazz. Yeah, of course, like I can't say for certain, but I wouldn't think so Odds are against another series one orange power formulas did not have a Mitchell calves Lamello ball on the power formulas Hornets What's an extra basketball goal label next week the Marta Rosen bulls Clarity She had a homekin rookie for the the Thunder Seating football orange basketball Orange Josh Giddy for the Thunder now is a Thunder break Well, we actually got a lot of that then we got the top screw on platinum anniversary. Oh, yeah Spellbound try young. Oh prison for melee. That's right next Friday. Yeah, let's go That could have some hype for what it's gonna cost. I think Power formulas John Morant's Contenders comes out Heck yeah, I'm excited for contenders Clippers co-wilder Kennedy Chandler Grizzlies rookie orange Markel folds magic You know Yeah, the rocks are cool tire Alex race you relics Spellbound Nathan Edwards and he racing is one of it's definitely a unique product Like that when that comes out all this personals it'll probably sell really fast my own standards of the Panthers I Was saying earlier. I wonder where he's gonna go after After they signs. What's his name shot penny? Interesting how much did he get Vaughn red trend of Watford Blazers numbered to 98 Spellbound Steph Curry Warriors John Moran Spellbound Grizzlies. Yeah, it's like a little less than baseball. It's typically Lebron power formulas Lakers Cavs Lebron James the insert there title waves Yoke it's 62 of 99 blue parallel for the Nuggets Driver spots are tomorrow. Everybody rich is breaking daytime tomorrow Sam in the evening Get those spots filled up rookie orange Jaden Hardy for the Mavericks TYT prism all day With rich power formulas orange Jalen Brown Celtics guys make sure to wish rich happy birthday tomorrow It's also his first day so go easy on him star status John Morant Grizzlies Get here ritual inside jokes easy missing out on Jimmy Butler on the heat acetate Like why why do you guys say these are you guys saying happy birthday? Because rich it's your birthday Johnny Davis wizards rookie Donnie and Sam do that together for like a month. I'm still I still go through when I thought was I'm still waiting for it Orange DFS for the Mavericks Maybe Higley, I don't know Anthony Davis star status Lakers Maybe even Lane Yeah Hey, thank you. Thank you for watching Donnie. Happy birthday. Hey Donnie. Thanks orange cam radish. Nick Would you get me? Guess you know the card to top load. Give me a sec Caleb Houston rookie number New breed auto for the magic happy birthday It's off As a mobility rookie calves Orange you pray Hornets No, he's not No, you should make it with him on it though Spell by Edwards T Wolves. I would just do like a prism logo and then rich and then yeah Orange dream on green warriors. You'll have to do it yourself. I think I'm like changing. You know what I mean like changing yourself Yeah, like when like when he goes live you might have to Kendall Brown rookie new breed auto for the Pacers paper cuts happy birthday Knock on wood. I haven't had a paper cut in a long time Usually when I get a paper cut, I'll show you guys and you're gonna love this It is right on the edge of this cardboard flap right here of any given sports card box Right on the right on that right on that. Mmm. Oh I don't like talking about it What I'll do is I'll like open it like this and move my hand too fast and like Oh Top's chrome that sounds that like tops from the longer flat box. That's the one that gets me. Yeah, I gotta I gotta show that to Halley Go while entered star status, you know, I'm not working tomorrow. Do whatever you wanted to Make the thumbnail whatever you want. I do not work tomorrow Yana son to the Kumpo title waves No way Lane, I would never do that Bryce McGowan's rookie for the Hornets orange Gary Harris magic Peel the cuticles back. Oh boy spellbound Luga Donchich Anthony Edwards full throttle Yeah, they are both way here. There's a day late words her and Lane. I are both not here She's gonna be here is the place to still be standing Yogesh for the Nuggets clarity come back Friday and find out Stay tuned Next time Nick, what's up, dude? Nicola Yovitch heat. Yeah, Zachara contrary to popular belief around here. I do need a day off Kid Cunningham on the power formulas same with Kyle I'll probably have to make a pot tonight actually I Still feel okay though and it's 730. It's honestly like usually this is when it hits I think when I get him like Kyle's heartbreaking, I'll probably like Get complacent Spellbound John or ants Just gonna fall asleep with the background of the camera. So Kevo Demi Lillard power formulas. Oh Packed for Vegas. That sounds like a good time. I wish I was packing for Vegas a Bobby Portas turn of the century auto for the bucks Number just 25 for the bucks six to 25. Josh. I'm pretty sure even if I volunteered they'd be like I Spellbound LeBron James I think it's more just like an intimidation factor. It's not like I ripped boxes before it's not like I don't know what I'm doing but like orangey ladle rookie for the from the pelicans I Think it's the intimidation that they're not mine. So like It's a different feel looks easy when I'm like flipping through cards like this, but yeah, it is a different feel Especially when you have to be like It feels weird to break with your arms planted. I don't know how to explain it orange here and Fox power formulas Like opening cards and then you do it here and it's Definitely is like an adjacent period of like getting comfortable with the camera in front of you orange Lonzo for the Bulls Trust me. That's how I felt when I was well I'll be watching Brad and rich break and they're just like second nature. Just it's like nothing and now I get there I'm like Like this. Oh nice a jailing green impact impressions auto for the Rockets took 49 Took his break kind of like after I started so I didn't really get to see Brad Red Chris Middleton is 78 for the Bucks real-time King Crumb King Crumb is such a good nickname it's better than it's better than Don Laceous Got star status John Moran Grizzlies So I don't know if you've seen this but It's the little like guy we're gonna have to show you spellbound orange Luca Donchich Mavericks What's up Bob Bob Bob Bob Bob who different All right, all those here Jalen green King Crumb Bobby Mortis Bucks Kendall Brown Pacers Caleb Houston magic Eddie Curry for the Bulls a Usman's Yang for the Thunder redemption Jaren Jackson jr. Grizzlies elite signatures Chet Holmgren pen pals to 49 thunder and a Dimensions Anthony Davis jumping like Mario. I'll do it. Thanks again everybody on to prism


Thank you. It's a wonderful opportunity to be able to come here and share some thoughts. In the student days, one of the things we do when you say write a two-page essay is you have enough content for the one page and then for the next page you begin to wonder what to write. Then we use the in-our-words technique which is begin the next page with in-our-words, right? So you fill up two pages. So the challenge for me now is we've had fantastic set of speakers preceding me and I'll try my best not to do the in-our-words, right? So I'll try to take a different perspective on what cloud is for Yahoo and maybe sometimes act a little bit of odds with the people who came up preceded me but that's okay. This is an intellectual discussion. So there is room for that I proceed. Excellent. That's great. I'm known to do that. So good opening. Okay, quick one through a very two second definition of what cloud for Yahoo means. Little bit of what the data centers in cloud means. Yahoo recently was awarded the prize for designing the best or the greenest data center. So quick some thoughts on that. And why do we need a cloud infrastructure? Everybody talks about cloud seems very cloudy. It should actually be called sunshine software or sunshine computing system but everybody calls it cloudy and what does it mean to have clouds? Some case studies, right? Case studies are very important. Let me begin with a quick little story. There's an airplane that was about to take off and there were 10 CEOs who were going to attend a quote unquote CEO enclave, right? And then just before the plane took off, there's an announcement that said, hmm, there's no pilot in this airplane. A little bit of an upset. That's okay. No pilot. We've had pilotless drones spraying fertilizers all over the place. It's okay. And then there's another announcement that said, oh, by the way, the software that runs this airplane is one is the one that's written by your company. Now we had nine people bailing out, right? My grandmom is not male. My PTA meeting is this afternoon, all kinds of reasons and nine of them bail out. The one person remains very, very confident, absolutely unshaken. And so the people asking, what makes you stay here? You're very, very confident of what's going on. Oh, my company wrote that software, the plane won't even take off. Absolute sense of confidence. And what I want to do is to be confident in a very different way, which is, how do we open source? Which means we get a lot of code that is written by people outside. How does open source work in production? Does it really make sense? So case studies are important because I want to, I want to leave you with a message that we eat our own dog food, right? Basically what we develop, we use within Yahoo to make heck a lot of money so that they can, fine. Quick architecture. We won't spend much time on it. There was a good session yesterday about what architecture is and key challenges. That's the key thing that I probably want to focus. For all bright minds like you here, what are the challenges in distributed computing? Right? Is it real? Where can we take this? If you can pick up a couple of sections from what I stress, challenges and give us answers, wonderful. Q&A, obviously. Okay, so quick. Deepak Salam by laying, making a very profound statement. Cloud computing is not new. I fully agree with him. Cloud computing is not new. Right? When you type www.yahoo.com, for those people who have gray hair, if you were to paint a picture about 10 years ago, you would first get your leg and then the right arm and then all these comes together. It's cloud. You had no idea what was happening www.yahoo.com for a new site. It went, spawned out so many processes, routers routed them to different places, you got your result back. Fantastic example of cloud. So what's making cloud more realistic? What's making cloud more valuable for us? We have started to trust it more, right? From just getting content, we are willing to do cloud transactions on Amazon. When you buy book, Amazon uses a very interesting concept of how you may manage transactions. Somebody asked a question on transactions and I'll be happy to chat with that gentleman who asked that question. Very noble way of looking at what transactions are. We have started to trust them more. And why? Actually, the reason extremely simple and I think Deepak mentioned that. So the cheaper bandwidth that this one is actually supposed to become big, he didn't start workshop. They said, but doesn't matter, we will make it big. The cheaper bandwidth. And I think he alluded to very correctly. The systems are all first paper in distributed computing. When was it published 72? Right? So distributed computing as a concept is not new. But the cheaper bandwidth is what is making it fantastically usable, right? Very, very usable because as he was mentioning, they can they have their data centers somewhere in a place where the power station is very next to where the data center is. Talk of being cheap and talk of being not losing trans due electricity when you transmit, right? Very nice way to do it. Yet you can connect and as if your computer is in the next room, you can continue to do all the work that you wanted to do. So that's what is basically driving it. So what cloud computing therefore essentially becomes fire and forget, submit a job, get the result, which is again not not new at all, right?  So it's not new. Why should why should data centers be cloud? Right? This very simple reason is scalability. He alluded as a couple of speakers alluded to a lot of data. The one thing that's becoming common these days is data, data everywhere, right? And the more people come and search in Yahoo site, the more data we generate because we want to find out what people do. So when you generate more data, you will have to have an ability to scale pretty seamlessly. But I don't want to be able to honor a machine, expecting that something will happen three months from now, get the machines delivered six months after the event has actually happened, then spend another one month provisioning it, and then spend another one month installing all the software, right? I want to be able to use it when I need it. So that's what is driving the cloud actually in a way, the explosion of information that needs to come out that needs to be captured and the data and the intelligence we need to gather out of it, all pretty seamlessly, right? As if I want to open the tap, the waterfalls, pay for it. You want computing like that. So that's what is actually driving the cloud. So it's in a way the data explosion and the fact that you want to do it cheap. You can always buy 99.9999% accuracy machine, right? But we'll have to pay all the money that we have in the bank to buy machines like that around Yahoo. We can't, unaffordable, simply unaffordable. So it's basically the ROI in terms of doing computing cheap and effectively for the large amount of data sets that you generate. So let's look at each of these in a little more detail fashion. So we'll hit them as we go by. You can look at scalability in two different ways. If you have a lot more machines, I can do things faster. In Yahoo, what we believe is if you have a lot more machines, you can do a lot more things much faster than your competitors. So that's where there's a little bit of a controversy in terms of how we in Yahoo look at cloud. We're not looking at it as a cost saving proposition at all. We look and I'll give you some case studies to explain that. We look at it as ability for us to innovate to do things faster than the rest. Simple mathematics, you can do things fast log in years faster. If you have 1000 machines, you can do things three years faster than your competition. Interesting study, lot of our time that we spent in the information centers in our data centers, we spent on doing road work, software install, getting quotation, provisioning and then running applications for the rest of the 30%. So if I have all my engineers working on writing software without worrying about provisioning and installing the software and all that, how much more productive I can make my engineers. That is a huge advantage in terms of going to these infrastructures that essentially removes all the intermediate steps that you need to get your job done. Professor Janakram is going to talk about this very, very interesting challenge. You have the conflicting demands. You have enterprises that begin with private clouds and then when the peak or when the bust happens, the demand peaks up pretty unpredictably, you want to be able to go to public clouds, from your private cloud. Professor is going to talk about a very interesting topic. I'll give you a quick little example, though not an exact example of what the professor is going to talk, but then 2611 happened. All of the servers in Bombay got loaded. Everybody was going to yahoo.com, new site. All traffic, I don't know how many of you went and looked at yahoo during that time, but if you notice, there was a little bit of a performance degradation, not a whole lot, a little bit, but we moved a lot of traffic that was coming in addition to what we could handle in Bombay to Singapore. That got overloaded. And then we routed all the traffic to Sunnyvale. But in a way, if you look at the Bombay Center as Yahoo India's private cloud, what we were attempting to do is to get more resources to satisfy all of our users who come to the yahoo site to get their news, which is what makes you come back. Now, tell me a way to do it without using clouds. I'll buy the answer. And I'll work for you, actually. So what's coming down the pike? All of us, for those of us who are in the industry and for those students who will get to the industry or get to an academic institution sometime, depending on your interest, you will have all these nice little web interfaces which will tell you about all the history in your company. Now, you have a web for that. Why would you want to do something else different for your clients?  So that is another thing that will drive this. When you, as an individual in a company, working for a company, have all these nice little web interfaces, any business that you will eventually run, we also get into the cloud. That's another area that integrate both these pieces. And when you do something like that, when you move your business to cloud, there's nothing like closing the doors. I can't let anybody in if I close this door. It doesn't happen in a cloud. Anybody can come any time completely unpredictable. You cannot say only 15 people can shop on my Amazon.com today. No way. So the very fact that you will have to go web to survive. And when you go web, you can't close your doors and you can't predict how many number of people will come in. We'll essentially force you to go to an architecture that is very, very, very scalable. Seamlessly. Cloud. Only choice, at least so far. Why cloud at Yahoo? We have a very simple business model. It's amazing how simple our business model is. We want users who come to our site to have fantastic experience. Nothing but fantastic experience. Very simple business model. But that should stay irrespective of what evens happen. That's a challenge. So the challenge is very technological in terms of how do I give the best experience to my users. You want to be able to scale one node at a time. You want to be able to scale data centers at a time. Bombay to Singapore to US. How do you do that? Obviously, if you have an architecture that supports that, unfortunately, or fortunately, is cloud. That's the only way to do it. So we're trying to list a few use cases for why this is very, very important for Yahoo. We have millions of users who come to our sites. We have lots of data that we create when people do search. We have so much content that we get when we provide news. A lot of content from many different sources. Reuters.com, ABC.com, PQR.com. We integrate all this news. We enrich this news. So the amount of data that we produce is humongous and very unpredictable in terms of how people will use it. Very unpredictable in terms of how we will get it. If there's a big event that happens, we get a lot of data a lot more faster. Not on a normal day like this. Normal. Yeah, whatever that means. So cloud for us is the only answer. We need to do this very cost-effectively. We have to be multi-tenant, which means provide for any number of users coming in. And really, with all the data, we want to be able to experiment. So before we started using clouds, our researchers couldn't find out what happened three and a half months ago because that's all we could store. So if we want to find out how well the Sari or the shirt shopping season was this Deepavali versus last Deepavali, we couldn't do it because we couldn't store the data. But now we can. We'll talk a little bit about how to fuse a couple of slides. We use cloud computing and we build clouds on very, very, very commodity hardware. So what that does for us is provide storage, which is fairly cheap. So you can pretty much store data thinking that at some point you will use it. Earlier paradigm was you store data only if you can justify that if you can use it. So you first tell me that I need this data 15 minutes from now and therefore I'll store it. With clouds, the paradigm has become very different, at least for Yahoo, which is a store. It's cheap. Store it. Make 15 Xerox copies because Xerox copying is free. So we store those copies and what that does eventually is provide our researchers an ability to be able to go look at the data and then build excellent statistical models. So for those of you who have been using Yahoo Mail recently or for those of you have been using Yahoo Frontpage, there are significant enhancements, right? Spam. Yahoo is doing an excellent job of putting all the spam to the spam folder, right? The accuracy is very high because of cloud. The fact that if you go to the front page your news moves and you can see which one is being read by most people is being done by cloud within Yahoo. It's all real time. We look at how people click. You and you clicked on the same news and therefore the fourth person, crowds behave similarly, right? Which is where when somebody throws one store at McDonald's, all of us throw the same store. Clouds behave similarly. So we expect that the fourth person who comes in will also probably want this news and therefore put that news instead of having you click on it. One mouse click. Every click is, every click saved is many click saved for many users, right? So all that. You can only do them with unpredictable, very unpredictable peaks. The business model which we can't get away from unfortunately, right? So what are we doing? We are building private clouds. We are not doing any public cloud. Two reasons. This year for Yahoo is big year because we are spending a significant amount of time on security. So we're trying to solve the security problem for our clouds and hopefully after that we'll be able to make it public. But we don't have good enough answers for security. The problem with cloud security is unlike the old paradigm where the weakest chain. So as your data gets transmitted, if there's one point where the security is weak, doesn't matter how secure cloud is, right? So we haven't solved the end to end problem and we are spending a significant amount of effort this year to solve it. So hopefully after that it will make it public. Hadoop is our platform. It's completely open source and the reason we do open source is because we believe there's phenomenal amount of idea. I work a lot with universities. Basically go steal their ideas and put them into Hadoop, right? I don't have much here so I just go steal ideas. Open source provides a phenomenal opportunity to be able to gather all this collective intelligence and contribute to make a product, right? So that's why I'll spend some time talking about the slides and say how we are using this in Yahoo to make a... So quick note, these are the four segments that we look when we talk about cloud and Hadoop specifically for those of you who attended the talk yesterday comes here. It's a batch processing framework. So we have a lot of number crunching and a lot of data processing that we do happens in Hadoop. Please read about this. As I said everything that I'm talking here is open source. So even our design for Hadoop is open source. If you go to Apache.com and search for the word Hadoop, everything that we do is there including our design, including how we have done Hadoop. This is a classic case study of how cloud will actually help. New York Times wanted to get all their images, period of converted to GIFs so that people can search. Classic example. They even got machines from EC2. Use Hadoop as a platform to do their processing. Got it done, right? Otherwise, would you do this by investing a lot of machines? You would not. So that's where I was talking about the ROI, right? Sometimes you just don't necessarily plan, but you need to do things. And that's where cloud comes very handy because it's cheap, easy to use. And that slide that our friend mentioned was very nice, right? I mean, if you look at the last line that he showed, the flat, that's through a benefit of cloud. The costs have all been amortized. So you can continue to use it as opposed to buying a machine and then deciding how to amortize it. So the cool thing about Hadoop is that it's planned around failures. We have written the softwares so that we assume human beings will fail. Let me give you a quick little story. Two people were digging at road. One person was digging and the next person was coming and closing and then walking, moving on. So there's a gentleman who was walking around and he looked at that, look, a lot of work being done but absolutely unproductive, right? Very, very unproductive. So he goes and asks them, hey, what are you doing? Digging, somebody is closing, nothing meaningful seems to get that. Oh, the reason is actually we are three people. The person who actually plans the trees called in sick today, right? Failure wasn't planned. Hadoop is not like that, right? We actually planned for the fact that a machine can fail. So a machine can actually call in sick and the task will get done, right? That's the key thing about, so the map reduced itself was pioneered by Google. What we have done is taken that paradigm and built a platform infrastructure on top of it so that a person doesn't showing up, doesn't kill the job, right? So I would encourage you to read about the architecture behind Hadoop purely for the simple reason that the way it has been designed is to assume failures, which is quite unusual, right? I mean you don't plan for bugs when you write software. You just say it happens. Of course it's job security, but you say it happens, right? You don't plan on putting bugs, but at least in Hadoop we've planned that it'll fail and therefore jobs speculatively execute. If a machine is going bad, we know a machine is going bad, we'll take the job and put it on to something else. If a hard disk reads really slowly from last one to this one, it's on the watch list. And if it continues to behave that badly, the task will be moved to a different machine and the hard disk actually, the whole machine actually comes off the rack. We will not send any more jobs to those machines. We'll blacklist those machines. So interesting way to design software. Fail more, fail more often. How many of you know scum or the agile methodology? Fail more, fail often, right? Classic way. This is a Hadoop has two components, map reduced in HDFS. There's a big talk yesterday about what it means. I'm not going to spend a lot of time. Again, for those of you are interested, everything is downloadable on the Apache side. So please go ahead and take your time to read and give us feedback. We'd love it. So when you want to take challenges and learnings, lots of opportunities, what does this teach? So distributed computing, as I said, is not new, but there's lot of challenges as we try and make this workable for any system. Somebody asked a question on transaction systems. Amazon does a little bit of that when you buy your, when you give your credit card, actually they have a very wonderful model of how the transaction actually happens. What have we learned? Scaling. Right? Major problem. Even though we have those 25,000 machines, scaring is still an issue. How do we scale? The problems that you encounter when you move from 100,000 machines is very different from the problem you'll encounter when you go from 1,000 to 10,000. But it's amazing. All machines are the same, but why did they behave differently? I have no answer. So maybe one of you can provide the answer. Right? Availability. Handling failures. Handling failures is something we have done fairly well in Hadoop because we have believed, we have programmed with the paradigm thinking that, hey, machines are like human beings. We fail, they fail. Very nice way to relate and data diversity challenges. When you come to Yahoo, you leave a ton of data which is all very different format, very, very different format. Wouldn't it be great for me to know that you came as a male user and left a trace and when you come next time to look at finance news, I give you the piece of information that you came and your mail will be fantastic to be able to integrate all this big data and see you as one user. Right now we can't. Right? But huge challenges in terms of the kind of data we get, how to integrate and get meaning out of it. Growth challenges. People address this already. And how do we make this seamless if we want to cloud bust as Professor will talk in the following session? Do we have enough hooks in place and write APIs in place to do it? Right? How do you define, how do you find out bugs in distributed systems? If a machine failed 10,000 miles away and your job didn't run, then you know your distributed. But can you go fix that machine? Can you go find out that actually, can you even find out that the machine is failing? Right? Challenging problems. Adoption challenges. This is again for overall cloud. Can I go to Azure? Can I go to Google App and say that I want to stay with them? What happens if for some reason, as he mentioned, there's a fallout and we want to go to a different vendor? Why? Users. Why? We need them. We don't need them. When you give, have you ever my heart does? I don't have enough space. When you give free space, it always fills up, isn't it? That's the problem we face. There's a lot of storage, but everything gets filled up because everybody thinks they need everything that they'll always. So how do you handle these kind of challenges? So the problem of plenty, you have a lot of storage. You have a lot of data. But then how do you manage that? Our QE, we get input from people like you who actually write code and put it into Hadoop. We have to do quality control of that. Make sure it works and run our search. Right?  Nothing can be more open than that. But huge challenges in terms of how we do it. How do we scale? Right? How do we do repeatably? How do we, how can we reliably make some tests? Very, very interesting challenges in distribution. And if you, you can pick any one of these actually, and it's a research area in itself. There's enough challenges if you just pick scale. How do you test for 25,000 nodes on a test environment that is not 25,000 nodes. Right? How much can you simulate? How can you simulate first of all? And if you can simulate how much can you simulate? That is a problem in itself. This is where we want to get. We want to be able to move the curve up where we can quickly do things. And, and huge challenge in terms of testing. Given the fact that it's highly distributed, given the fact that we get software from external sources. People, anybody can write software and put it into Apache. Right? Because of its open source nature. Checkpointing parallel applications. Very, very interesting challenging research problems. And this is where I run to the universities to get some ideas. Right? How do we schedule? A job. If there's a problem how do we reschedule? We are not even good at scheduling now. Or how do we schedule optimally? We don't know. Talk about rescheduling. Right? Performance modeling. Energy-based optimizations. If all six cores of the machine are not being used, how can I shut off two cores? We are working with Intel to do that. So that at at its processor level we can determine how to keep them powered on or powered off. Right? Very, very interesting set of challenges. Extremely interesting set of challenges. Performance problems. How do we understand external failure? So we have become fairly good at that, but not fully yet. We can begin to understand machine failures and essentially blacklist that machine. But there are a lot of other things that can go wrong. Network. We don't know. How to find that out? How to prevent data from flowing from this machine to this machine over this network? Because this network may go bad. We don't know. Right? So are there ways to find out if something is going bad? A research problem in itself. Different kinds of challenges for providers. Right? Hardware, software, quality of service. And I guarantee quality of service. Somebody asked the question about banking. Unless we provide quality of service, ICICI Bank won't come to a cloud. Right? So we are far away from doing that. Very, very interesting studies in interesting area for research to try and come up with models that can be expected to run predictably. And you can use those models and run them on the clouds and then have these real-time customers come on to the cloud. For us as users, different sets of challenges. I need to be able to bust, go out, contract. And I also need the ability to be able to go with go to a different provider. Right? Do I have the right kind of APIs? Am I stuck if I go to Azure? Am I stuck if I go to Hadoop? Am I stuck if I go to Google? Do I have APIs that I can move across? So our view really is, right? It's not about saving money at least within Yahoo. For us, the plan it's about driving innovation. We build Hadoop, which is a platform on top of commodity hardware so that we can have storage that is very cheap and huge computing power to take the data that we store for long periods of time, compute and allow our research people to come up with predictive models that can be used very reliably and hence provide excellent experience to you as users. So that's a we think it's more about driving innovation than about money but it may eventually get there over a period of time that graph that he showed eventually it may get there but at least right now we view this as purely for innovation our ability to be able to do things much faster that we could not otherwise do. I have one scenario please share your thoughts on that. Suppose I have an organization I have 3,000 desktops with me and within my organization there are many projects are going on many projects using the third party tools third party applications there is a licensing issue with that but with the cloud at night all this my 3,000 desktops just shut down. So using Hadoop what are the possibilities to efficient utilization of my this 3,000 desktops? So I'll give you a quick answer now maybe we can chat later offline what the key thing to remember is Hadoop uses a map reduce paradigm so the fundamental requirement is if the application that you are trying to run is not conformable to the map reduce paradigm you can't use Hadoop at least now but we are working with to try and provide other parallel crossing interfaces like MPI and all that as part of Hadoop so that's the key thing typically in desktop applications they are mostly pieces that people individually work on why and I don't know what your infrastructure is whether all of them are virtual or all of them are desktops or all of them you simulate something on top of that I don't say desktop so in that case it becomes a little hard what you can do is if this machines can be combined together to run other applications that are map reducible then you can use Hadoop but right now for your situation I don't think Hadoop is an answer thank you


What's up everybody, Jayce here for JaspiersCaseMakes.com, 21-22, Panini, Mosaic, Basketball, Hobbies, 6-Box, Half Case Break, Picket Team's number 6 sold out, and here we go guys. So last but not least, going to Michael and the Spurs, and I hope we get some big stuff for the Spurs. It's half there for a little too long, but longer than I thought. Didn't have a couple stained glass, but we didn't really get a big rookie auto, so let's see what we got here guys. First box. Well, Ben Simmons to start us off, Brooklyn Nets, David Chan in 99, Trayman, Jayden Suggs, and Malik Monk for the Lakers. Lakers Matt Johnston. And nice! There we go, we did get another stained glass, so this might be one of those cases that have multiple stained glass. Usually on average too, but this is our third one now. Nice Steffan Curry stained glass going to Matt Johnson in the wars. This is Moody, Davion Mitchell, Chris Guarde, ooh let's see some gold maybe?  Gary Harris for the Atlanta Magic to 25, Gary Trent Jr. for the Raptors, Facundo Campazo auto for the Nuggets. Jayden Suggs red, Kevin Durant overdrive, Kate Cunningham US, and there you go, a box too.  Remember autograph wise, I just haven't hit anything crazy. After this box you guys, maybe halfway through, but stuff plenty of hits to go. There we go, next one. James Wiseman, Golden State Warriors, and a straight fire, Zach Levine for the Bulls, one of the last few teams taken Jenna. Davion Mitchell, Yannis Red, Eric Gordon, Zach Levine Red, Kate, nothing crazy, come on. Him it was something, him it was something. Jackson Jr., John Tim Murray, autograph gotta be here somewhere, right? And Quintin Richardson for the Clippers, another team that was one of the last few teams taken. That's Jenna again. Not the biggest auto, but we'll take it. This has got to be one huge autograph from you or something man. First half was a little rough. Alright, come on, come on, three left. Scotty Barnes to Silver, that's pretty nice. Soon Blue Red, ice rising stars, Josh Giddy. Giddy. Wendell Carter Jr., for the Orlando Magic, Al Horford Pink, Boston Celtics, Matt Johnson, and then Orlando Magic is Wolt. Little swagger, Kate Cunningham, Wagner, Minga, LeBron, Yannis, that's a nice card right there. Milwaukee Bucks, Sean. Blue. Two more boxes guys, good luck. I need something massive, not this case it's just been a little too weird. Here we go guys. Bird, actually moments in time. That's a gold four to ten, okay. Very nice one there for the Celtics, Matt Johnson. JT Thor Blue, Brian Wofford with the Charlotte Hornets. Nice, there we go, Scotty Barnes. I knew we had to hit a bigger rookie auto. Scotty Barnes that is for the Toronto Raptors Ken Baum. Swagger, Evan Mobley, Scotty Barnes there, Giddy. Holy introductions. Alright guys, last box. Justin Holliday, Josh Giddy Red. A rising stars Josh Giddy. New regards to True Silver. And Luke Longley, auto, that's for the Bulls on the last few teams taken as well. Again for Jenna, Steph Curry Silver. Swagger, LeBron James. Scotty Barnes Red, USA. Wagner. Stair Matches, LeBron. Alrighty guys, well there it is guys. Glad we got a Scotty, but I was hoping for a little bit more than just that. But we did get another Sting Glass, which does help. So that means in total there was three Sting Glass. We did get a couple of golds in the first half. We got a gold here in the second half. But I was hoping more for a couple more teams. But that's all it goes sometimes. So again Scotty, we got a gold Sting Glass.  And I guess a lot of the stuff is going to be shipping as well. Appreciate it guys. This is number six. Don't know if we got more. Nick will probably post some more in the morning if we do. Appreciate it guys. Jasperyscasebreaks.com


This is Chris Pipe. My friends come a big see back in action today I'm gonna show you how to download hit film this used to be called hit film express and we did about 35 tutorials on how to use that software. Well, it's been rebranded and it's got a whole bunch of new changes And now it's called hit film So let's just go and learn this one from scratch to get it to Download it go to FX home calm like I've done here and then you're gonna see the download free option Just click on that. It's also up here as well.  Oh, let's put in my real name. Why not? Curtis I come on Curtis Curtis Pike. There we go Curtis and Mg n dot TV. I Don't know. Let's pick a password something like that. Okay. I do not want to receive emails No, no credit card required beauty. It's free. All right. Let's go It's already taken of course it is Curtis at Mg n dot gg then whatever Close enough. There we go. Now. It's gonna send me a bunch of stuff and let's go ahead and begin the install So there it goes. It's downloading. It's five almost 500 megabytes. So that's pretty big. Now. I'm gonna just check my email See if I got it. This is not the one. Let's go switch over to this one Bingo welcome to FX home. There it is guys So I'm gonna go ahead now and let this finish downloading and then I'm gonna come back Alrighty welcome back. It has finished downloading double click on the file the dot pkg and off we go Here we go. We're gonna get into hit film installer. I'm just gonna hit continue. Yeah, I read of course I read the agreement. I always read them front to back. Sure. I agree Blah blah blah. We're gonna install with the default spot 1.12 gigabytes of space and that needs my password Let's see if I remember it. Hopefully that's the one. Ha I remembered it That's a first and I guys I'm just showing you the steps for the free to find it to download it to install it and again This is free software I'm also gonna show you all the different techniques on how to use it as well But for those you that are new to YouTube or getting started, this is awesome This is a way to get in without having to pay for anything and get up and running real quick Anyways, I will come back with the final bits in a second. All right, welcome back It's now in my applications library here. I'm on a Mac But it does the same thing on a PC, but you will notice here that I've got hit film express and hit film So this is the old version and it is no longer usable. So I'm gonna go ahead and delete it just drag and drop it onto my little Onto my garbage can my recycling bin so to speak and now let's get into hit film. Here we go Double click on it. Let's see what we get There we go. Nice and easy Okay, off we go hit film FX home blah blah blah But anyways guys, that's how you do it using hit film that I'm in the next video I'm gonna show you how to bring any Content how to edit how to add in photos all those good things but for there, but for now, that's all we got guys Thanks for watching


Statistics and Excel. Standard deviation versus average deviation. Get ready, taking a deep breath, holding it in for 10 seconds, looking forward to a smooth soothing Excel. Here we are in Excel. If you don't have access to this workbook, that's okay because we basically built this from a blank worksheet, however, starting in a prior presentation. If you do have access to this workbook, three tabs down below. Example, practice blank. Example, in essence, answer key. Practice tab having pre-formatted cells so you can get right to the heart of the practice problem. The blank tab, we started with just a blank sheet so that we can practice formatting the cells within Excel as we work through the practice problem. Let's do a quick recap of what we have done in prior presentations as we have been calculating the average deviation and the standard deviation.


Aloha, and we are here at Poe Gallery to meet my darling, dear friend, Sandy Poe. Aloha Sandy. Hi. It's so fun to see you again. Tell us about the gallery, about how long have you been here in the gallery, in total galleries? In this neighborhood, I've been in maybe about 15 years. I was in Fort Street, Moss, Smith Street, Nuanu, and now I'm on Bethel Street. I love it. Every time I've moved, I've moved to a better location, so I'm really happy. Now, tell us, the name is Lewis Poe. So who was Lewis Poe? Well, Lewis was my second husband. I was his second wife. So we learned from each, you know, we learned from our first marriage. So it was a really good marriage. Lewis came to Hawaii in 1942. It was at the start of World War II. He told his, the recruiting officer that he was a painter. And so they shipped him over to Hawaii, and he painted ships, you know, he refurbished the ships. I don't think that's quite the word, but anyway, that's what he did for a living until he got medically discharged. The first chance he got to come back to Hawaii, he grabbed, and it was to start the Honolulu Art Academy Art School in 1945. He and his friends started it. And so they taught a lot of artists, well-known artists in Hawaii. And they kind of were, he and his friend were kind of the, put a stamp, their stamp on the measure of what Hawaii art is all about today. Yeah, because they were at the Art Academy for 35 years. So that's a really long time of just teaching and influencing people to do art. He thought that everybody could do art. Everybody was creative. And that Hawaii had the best artists ever, you know, nationwide. Because we're influenced by the world. And so the artwork reflects that. Yeah. So can we walk over here real quick and just take a look? This is Louis. That correct? Yeah. He was a pretty cool guy. Yeah. Yeah. So he went down to his studio every single day to paint.  So he painted every day. He painted, he had at least five oils going at a time. And he did watercolors. He didn't do acrylics. He did a lot of printmaking. He was a printmaker. That was his favorite thing to do. And that's pretty much what he's famous for. So you have been, you're the widow. And so you've carried on all of these years? Yeah. Right. In 1999. So 18 years, he's been gone. And so he wanted to be world famous. And so my mission, since he's been gone, is to try and see how I can promote that so that he could actually be among the greats of American art. So we have lots of artists from lots of different places. So all of these are different artists? So we represent about 10 different artists. They all live in Hawaii. They have to live in Hawaii to be eligible to show in the gallery. And so this is oils, watercolors, acrylics, printmaking. I, Louis liked art and he absolutely loved abstract art, really good abstract art. So that's what we kind of, we try to represent here. Now, real quick, tell us about you, the Arts District Merchants Association and all of the other things you've done since you've been in Chinatown. Oh my God, in the last 15 years we've been, we've done a lot of street festivals. When we, when I first came into this neighborhood to open the gallery, people were so afraid to come downtown, you know, because it was a red light district from World War II days. That was what it was known for, was brothels and, you know, drunks on the street. And so times have changed, but people's perceptions didn't change. So what we did was, you and I, we put, we helped put on a lot of street festivals and it was really fun. And people started to come and now, you know, it's not unusual with people to come. They come at like nine o'clock at night and they stay at two in the morning, way past my bedtime. But, but it's, it's, it's the safest place to come and, and have a drink, eat dinner, you know, catch some good entertainment. And sometimes galleries are open, on first Fridays the galleries are open and so it's really a fun night to just walk around and look at art. And just meet up with people, you know.


Hello students, let's work out the following problem. It says in a class of 25 students 15 are boys. The mean weight of boys is 50 kg and that of the girls is 45 kg. Find the mean weight of the class. So let's now move on to the solution. Well given that number of boys is equal to 15 Let it be n1 and the number of girls The total number of students are 25 out of which 15 are boys. So there are 10 girls Let this be n2. We are given that mean weight of boys is denoted by x1 bar equal to 50 kg and the mean weight girls is given to be 45 kg Now the mean weight will be given by n1 into x1 bar plus n2 into x2 bar upon n1 plus and n2 As we know that the mean x bar is given by the formula summation f i x i upon Summation f i by the same logic here. We find the mean weight of the class here So we have 15 into 15 plus 10 into 45 upon n1 plus n2 and 1 plus n2 is equal to 25 we are given that total number of students are 25 This is equal to 750 plus 450 upon 25 and this is equal to 1200 upon 25 and this is equal to 48 kg so the mean weight denoted by x bar is equal to 48 kg Question and the session. Bye for now. Thank you. Have a good day


My name is Calla Varis-Virta, I'm from Finland working for a company called XO, I'm here to talk to you about auditing triple sites, some things that I just want to say is that I'm going to be going in and out of triple in a technical manner as well, so some parts might be difficult to understand if you're not a technical person then sometimes might be boring if you are, so hopefully I bore all. Also some understanding of the business-involving triple should be useful while listening to me, so let's get a hands-up first for technical people and then triple business people, our first they are both, what I'm gonna talk about here is that why are triple audits done in the first place, there are several different reasons for those, how they are done and I'm gonna include some technical details as I said earlier and then I'm gonna go briefly into the business of triple audits, there are some challenges that needs to be taken into account when doing audits as a business, so let's start what's an audit, that side, I wonder if I can switch off the lights from somehow, better? Okay, good, that was for the light switching guy, thank you. Okay, so audit is a run-through of an implementation of a site, that means that an experienced developer goes to a site in and out all aspects of it, it doesn't mean that he reads every row of code but it's a very thorough thing usually and as I said audits are done for many different reasons and the process of doing an audit varies a lot, we'll get to that next but so how many of you have done an audit, okay, how many of you had your work scrutinized by an audit? Less people, we have more auditors than the people getting audited, okay, good one. Alright, why are audits done? So we have four categories of audits, acquisition audit, implementation verification audit, vendor management audit and support audit, these are not official categorizations of audits, this is just my hunch of how I would divide them into groups. Acquisition audit, that's part of a, well it's usually done before making the decision to buy a business, that means that it's part of the due diligence process and some people know what that means but that means a investigation of a company before signing a contract usually to buy it, so that's for acquisitions that that means obviously due diligence means also financial side and all the others but when the company's business involves web or the site in really key aspect of it then it's usually a really key aspect of the whole due diligence to do the audit for the site. Usually they are done obviously to smaller startups, anyone who based their whole business online and it's a very in-depth and focuses on kind of a hidden agenda, usually the company that's buying the other company, the buyer has plans for the site and they don't tell the target of the deal what those plans are but the auditor needs to know what those plans are so you need to know what they want to do with the site so you can actually audit it in a proper way. The next category is the implementation verification audit, I would say that's just to verify an implementation of a site that's more like an insurance policy, the customer just wants to pay to not have any problems, they're not expecting a lot of problems. These are usually pretty brief done in collaboration with the vendor who's working with the site and shouldn't ever be done to a system that's not finished.  Then there's the vendor management audit and this is a bit complicated one that means that your customer who's buying the audit is wanting to switch their vendors not necessarily to you but to something else and they usually have some problems with the current vendor and that makes it a bit difficult because usually they don't tell the current vendor that this is happening so you'll have to do it without any help from the current vendor and that makes an audit a bit harder. We'll come to that also. These might be very brief but usually it's a bit longer audit. My longest audit that I've ever done was a vendor management audit took about more than 30 man days to do that. It wasn't a Drupal though, it was a custom code a lot of it and this time the client expects to find something that taken base on their decision to switch vendors. They might just have a personality clash with the current vendor but they still want something to base their decisions on and you shouldn't go into that trap. We can we come to that later as well. Then there's the support audit. This is when it happens when you move an existing system to your support. Unfortunately this is a very important audit to you but not very important to anyone else so you won't probably get paid a lot or paid at all doing this but you should still do it. This means that you'll be getting someone else's code into your support and you'll have to support it later on and then you should do an audit at least a brief one and this is also the type of audit where you can learn from the experience because in the long run if you take an existing site to your support you'll find out all the problems with the site. You'll also learn what you missed in the audit. So this is really a learning experience. Unfortunately it's also when it's a really good learning experience also a pretty nasty one because you have a really broken site in your support. That happens every once in a while. So going to how it's actually done. Tip one, you always need the source code. Always. First and foremost. Okay start taking notes from day one. You need those notes to back your memory up. You'll forget everything and remember stuff wrong later on. Then you'll have to go back and recheck and even though it's fun it's kind of exhilarating to get a USB stick of some code you never seen before and you want to just investigate code through everything at once. You should write notes while doing that because you'll forget to do that and you'll forget everything you saw and you'll just remember that it might have had this in this file and this directory somewhere and then you'll have to recheck and have to do the work twice or three times. Secure the source code. As I said you always need to search source code. Ask for a dump from the database. Now there's the whole concept of having private data in the database which is kind of problematic. Sometimes it's possible to obfuscate the most private parts of it. Social security numbers or something like that in the database so you can actually get the data because you need the data as well because you have to see how the system works with data. Without data it's kind of a shell. The obfuscation is done by the current vendor or your customer if they can do that. It's sometimes very hard. Sometimes even impossible. You just need it so you'll just have to figure out a way to do it somehow. Don't ever settle for partial source code. Now this is a really typical thing I keep hearing. We'll just give you the custom modules. That's not enough. You need all the modules. You need all the source code. There might be hacks in core. There might be hacks in the content modules and there might be stuff in the wrong places all around and there might be some really odd configurations in a non-hacked core as well. You need the whole Drupal. I've been hit with this once. We had a really juicy big customer and I tried to persuade them to give me everything but they didn't. They only gave us the custom modules and when we finally got the whole site into our support it had two cores running different versions side by side. You can imagine what kind of a mess that was. Drupal is, unfortunately, still is, totally impossible to update. Well, let's try and forget that. Anyway, then the next thing you should do is to install the site. Now this might sound a bit odd. They have an existing site installation somewhere but installing a site gives you a lot of insight into the whole thing. Have you ever done your custom modules and done a lot of update hooks there and forget to update the install hook? Yeah, that's why. You learn what's missing from the system and what's not documented or what tweaks need to be done that's not supposed to be there and you'll probably have to stop several times getting more data. Code, vcls, API definitions to create dummy APIs. We serve enough calendar time for this and it's still worth the time. Next thing, you must understand the architecture. Once you have installed the site, look at the architecture. Drupal sites are based on different combinations of modules. Certain combinations of conjured modules. You can do blocks with context or panels. You can search with search API, maybe Apache source search integration. Translates, translations, you can use internationalization, you can use field translations. Translate blocks. Use a multi-site, maybe. You can control access by domain access, taxonomy access. So plenty of options. You have your favorite option, obviously. You have your favorite combination. You know them by heart. Don't be biased. They're probably not the only way to do it and it might be just equally proper way to do stuff even though it's not the way you do stuff. So don't get biased by your own opinions on which contracts to use. Next on architecture, does it fit its purpose? If you see a Drupal and all the custom code in the Drupal, it's just circumventing the shortcomings or Drupal's practices because it doesn't fit the bill, then it's not the right tool for doing that. And I know this might get me killed saying Drupal conduct isn't suitable for everything, but it isn't. So in some cases, you have to see that this is not just not the right tool. It's the site using Drupal as it should. I've seen a lot of, well, several sites using Drupal in a way that it has like three pages out of Drupal and then everything else goes to a custom module to some custom backend and pushes data from there. Just an empty shell with some theming on it. That's not a proper way to use Drupal. Usually the customers are asking that why doesn't any contracts do anything to my site? That's because your site isn't on Drupal really. It's somewhere else. That happens. Are there custom parts somewhere where there's a well-working contract available? The custom parts might be built well and they might be even good for the purpose. But if there's a contract available, you have to judge by looking at the contract's possibilities and the custom code, that which one would be better, at least have an opinion about it when you write the report. And then you have to look at if it's overly complicated. Obviously, Drupal sites can be overly complicated and they can be for various different reasons overly complicated. But you'll have to report that as well. So make sure you understand the architecture. It might take you a long time and it's really easy to fall in the trap of just writing the report without understanding the whole thing. But you really, really, really need to understand how the architecture works. What were they thinking when they were doing it? Because if you write your document or your report, your audit report, without understanding the whole architecture, it's just going to be a bad report. And it might take days to go through the code and go through the modules and wonder why is this done? Why is this done? What is this? Why is it here? But when you finally realize why it was done, then you can actually write an intelligent document saying what should have been done and what should be done next. Then there's the whole concept of reading code. Remember, reading code isn't the main purpose of an audit. It's not a code review. But reading code isn't a big problem in Drupal audits. And there's usually relatively little custom code to be read. And if you have trouble finding it, for instance, if it's not in module slash custom, then you might find it with hacked if it's in totally wrong place. And when there's a lot of code, as sometimes is, remember you can't read it all. Reading code row by row doesn't benefit anyone. So when you're going to be reading code and there's a lot of it, focus on the parts that make a difference in the end result. Look at security holes. Look at beginner mistakes. Look at performance problems. These are the typical ones. You want a list on your findings report. When you're looking for security holes, well, here's just a checklist. This is totally not exhaustive list. So there's plenty of more stuff to look. But I'm just listing a couple of things here just to give you an idea what you would be doing. Check for SSL login, check for old contracts without patches, check for abstractions, unclean inputs in the UI, JavaScript, a lot of XSS available there, API calls without HTTPS to the backend systems. This is something that happens ever so often that we connect to a CRM back there somewhere and it gets left on the development settings and then data is going to HTTP without any protection. And there's personal information there. Beginner mistakes, unclean access to Drupal. That's what happens when beginners start with Drupal and they don't really know how to do it. Hook for unnecessary custom modules? Well, obviously you have to think that also the time span where the contract is available when the custom code was made, written or is it doing exactly the same thing as the contract modules? Look for wrong hooks. That's something also that happens every once in a while that people just use a hook they find first and that's probably not the hook that they should be using so they might run stuff too frequently, for instance. Performance problems, static cache is time consuming functions, check out the amount of processing in any hooks. Look for slow backend APIs. That's something that you can't do anything about but you might want to list that on your report. Check out the caching strategy. There are plenty of different caching strategies but you should definitely have one at least. Well, we don't cache anything. It's a caching strategy as long as it works. Look for unnecessary but very slow contract modules or misuse of contract modules. I've seen that as well. Site crashes every once in a while. It uses a contract module for something that it definitely shouldn't be used. Then there's the whole social engineering side of the whole audit. You'll be talking, not in all audits but most audits, you'll be talking with the original developers. It's very important. Don't miss that opportunity. If you have an opportunity to interview the original developers, please do that. They'll tell you not only how it works but why it works in a certain way. They might even tell you that this and this part is totally wrong and we had to do it like this because we were tied on time or something like that. They'll point you straight to problems. Just be polite and friendly. I wrote a blog post about the social aspects. I thought it's just a couple of weeks back. I had a couple of lines there. What you should do when talking with the original developers, they were first introduce yourself, your background and your expertise. You get their respect in that way. Explain what your task is and what is not your task. Your task is not to blame anyone or something like that. You're just trying to find kind of an understanding of how the system is right now. Don't speak any of your findings out loud when you're looking at over someone's shoulder and you see something really horrible.  And you use positive language always. You're not there to find out problems. You're just there to verify it's as good as the climate is. And when you're asking questions about the code, be very understanding of the situations with the original developers. They probably were busy and there were demands in all different directions and stuff like that.  You won't get any friends like that. Let your customer do the whole telling people stuff for you. You don't want to do that. But it's not just the code. Okay. You might have a really good site, a really professionally made site and it's installed by Total Newbie. It doesn't come up with a good result at all. So always look at the production environment. Now this is something that is usually pretty difficult to get, which is access to production. But you should try and do that because if you don't see how it's actually running production, you probably miss out a lot of what's actually happening in the site. You at least need read access to the production or at least a copy of all relevant configuration files. The problem is though that you should verify that you actually have all the configuration files that they have and you can't if you don't have access. Even if you have access supervised so that someone's looking over your shoulder when you're poking around, that's okay. You can just poke around.  Make mental notes. Don't write them at that point. So there's a lot to check in the production environment obviously for security, for performance, for reliability. Installation and server configuration. Look at the PHP. Look at the HCTPD process management configurations. Upcode caches. PHP scary options. Apache, nginx configurations. MySQL and other databases, replication configurations. Backups, by the way. That's a wonderful thing. Ask if they do backups. They say yes, then maybe they do. You can't usually check that, but you can just hope that they were telling you the truth. Check for open ports, services running, MySQL passwords, all the extras, Swanish, VCLs, MongoDB, Redis, Solar configurations. Do check the Solar schemas as well if you're poking around in Solar. Take a look at the Drupal configuration. User roles and privileges, registration and login settings, caching settings, content modules settings. Content modules might have really scary settings, beware. Good, look at them. You might have trouble finding them as well. They might not be listed anywhere. You just have to look at the module to see if it has any many callbacks. Custom module settings, even scarier, usually. They might be just config files on the disk. Make sure you check them because they might have really, really scary stuff. SEO configurations, that's something that people tend to forget. Us developers, we don't think about SEO. Cleanup for automatic imports. An automatic feed import running some RSS feed-in might chew in a lot of data over time. It might have a really big chunk of stuff in the database. Multisite configurations, language configurations. Well, the site might not be about performance, but a quick benchmark never hurt anyone. Depending on the audit, obviously, performance is just a part of the audit or it's a main part. In acquisition audits, performance is usually important. The idea is that the customer, your customer, the buyer, wants to use the site for something bigger, better, and something that needs more juice in the system. They're going to ask you that the site is now serving 100,000 uniques a week or 20,000 registered users. Can we double that? Can we triple that? Where's the limit? It's really hard to estimate that, honestly, but you have some idea of that when you do a quick benchmark of the site. Not a quick one, but if you benchmark it a bit. Just run a couple of pages with anonymous users, logged in users with a benchmarking tool, profile the site, under load, see how it's doing, what it's doing, especially what it's doing. You'll probably see potential bottlenecks very fast and you'll be able to just write them down. Now, two really important things. Auditing is a gentleman's game now, or a woman obviously, but you have to be very polite. Usually, you write one or two written reports that are kind of the outcome of the audit. Sometimes just one, but sometimes two if you need a non-technical and a technical one. Usually, the non-technical is just for the business people to understand something. The technical one is for deciding what to do about the site. Sometimes you can add code snippets and runtime grinds from the code, but sometimes you can't. In acquisition audits, generally speaking, you can't add any code or anything in there, because usually the custom parts of the site are kind of owned by the company still running it, and the buyer doesn't have any, doesn't get any access to them. Even as you're doing the audit, you can see the code, but your customer can't see the code. They are not allowed to see that. They can just see your opinion. Your opinion is what you write down, not what's happening or what's in the code. This is what I usually do. I divide audit document into three main parts. There's the introduction, explain the system, architecture, the platform, the modules, implementation on a high level. Then there's the finding spot. I list all things that I think are worth mentioning in the document. I sometimes mention good stuff, but mostly it's very problem-focused. We tend to be as coders. Then there's the improvement suggestion spot, where you suggest improvements. Now, this is debatable if it should be a part of an audit, but I usually do it as a kind of professional courtesy always to tell what I think should be a better solution, because it's easy to blame some solution bad and not give an alternate better solution. Just being kind of, you can always say that something's bad and not tell what's better. In that sense, I would suggest that everyone who's writing these documents would write also your idea of a better way of doing that. Whatever you do, don't ever bash. Don't get personal. Don't bash. Don't bash the system. Don't bash the coders or the decisions. Just try to be as neutral as possible.  You don't have to understand why it was written there, but there's no need to bash the expertise of the original vendor, even though it might be debatable in that case if they actually have any expertise. But still, don't write it down. Not only because it doesn't make any difference in the end result, but also because you'll be at the receiving end at some point, and you'll really appreciate the professional courtesy from the auditor, not bashing you for your really hard and fast decisions you had to make, that and that fall or that and that spring in that project when you were running out of time. There are different circumstances when we do triple sites, and we all know that some circumstances are harder than others, so you will have to just understand. And we're a small community. We don't need to get business by bashing other people in this community. List only real findings. Now, what if you can't find anything wrong with the site? Doesn't it feel kind of sad that you're taking 6,000 euros of your client's money and not even giving him anything in return? Isn't it kind of sad? Maybe you should come up with something. You should not. Just write down that there's nothing wrong with the site. Manage the customer expectations when you're selling. Tell them that you might not find anything, that it might be totally fine. The site might have nothing wrong with it, and never exaggerate problems, because when you go to that, you'll just get into the whole game of blaming people for trivial problems that can be easily fixed or that were done in a haste and can be well rectified in no time, or the problem isn't even that big. Unfortunately, I see some of this in the security audit business. They tend to list really odd security holes, holes just to fill up the whole report. I don't like that. We don't have to do that, so let's not. If you can't find anything, don't list anything. End of story. I just did a really big, big, big audit this spring, and I couldn't find anything wrong with the system. The only thing that was wrong with the system was it was built in 2006 and using that time's technology. I told them that it's like a really beautiful car that's a bit dated. There's nothing wrong with it, but it's old, and the customer was fine with that, even though that was a big audit. They shelled out a lot of money for that. So just real findings. Also, don't put your junior devs to do audits. It doesn't end well. In the business of an audit, the time needed for a drip audit is really, really hard to estimate. You could estimate it well after you've done it when you know what the site entails of. That's kind of redundant at that point. You could also just check the clock. Ranging from two man days, I would, like, an hour game with audits isn't something that I would opt for. I would say that from two man days, and then you can go on. Obviously, a good deal is to get a limited budget to do that. Try and do that. Probably not that easy to get, but usually the customer wants something, something, some limit, some number, something, and then something in return as well. Pricing goes by the hour or whatever, but it goes by the price of the highest consultant you have. Always, you should also use the highest price consultant you have to do that. For support audits, obviously, time is very limited, and you'll just have to do what you can in the limited time. Then who is the person who can do an audit? Now, the person needs to be a real expert. Honestly, a real expert. I would say that years of experience in not only Drupal, but Rocksolid PHP programming skills, they need to know what they're looking for. The more experienced they are, the faster they can find the problems in the system. They know where they are. They know their way around different architectures. They can understand different setups, different architectures, different systems. When doing integrations into external systems, you'd have to understand a lot about integrations. High performance security integrations, hugely beneficial. I would say that four years of experience to start, okay, so you can go to our website and see how many references do we have from audits. Not many, I can tell you. The most problematic part in selling Drupal audits is that the customer would want to buy from an experienced, well, someone who's experienced in audits, and still they won't give a public reference for doing that. So they're pissing in their own pond. They can't find anyone who's done audits publicly because they won't allow you to tell that. And it's a really subtle business because when coming to an audit, the NDAs get really heavy. And we once had to take an insurance policy just for signing the NDA because the damage causes were so steep, there were two dangers that they would tip the whole company if we would go to that. We didn't, obviously, but still we had to take an insurance policy for that. So they really get bad. Some are so bad that small Drupal shops just can't do audits. Some audits are the kind of an audit that only go to bigger Drupal shops because they have insurance policies or money enough to sign such an NDA. They might also demand a personal NDA from the person doing the audit. That would find as well, read that if you're about to sign one because you really want to know what it says in the contract. So one out of 20 audits I've done, give out a public reference, that's about the range. So do 20, you get one reference, do another 20, you get the second one. Then your experience, you have multiple references. All right, okay. When is the perfect time to sell an audit? Well, obviously when the customer is changing vendors from someone to you, you should try and sell an audit. That's the place where you should basically demand it. It's for your own security to know what you're getting into and the same goes for taking existing sites into your support. That's also a place where you should definitely demand to, well, to have some conversation for the audit. If you can't get any compensation then do it on your own money, out of your own pockets. You'll have to do it anyway before you take someone else's code into your soft care. And just a reminder, selling audits, never promise you'll find anything wrong. You don't know that. Never promise that you'll find everything that's wrong. You can't guarantee that. Nobody can. Unfortunately, you'll probably miss out a lot. I can guarantee you that.  In other words, it's maybe not. You get a free pass. Then a quick recap. Get the source code. All of it. You need it. Get the configurations. Get access to production. Understand the architecture. Optimize code reading. Read only code that matters. Remember to test the performance. Be a gentleman. And list only real findings. Okay. That's it. Thank you. Well, according to schedule, I have about 15 minutes left. So if you have any questions, please use the microphones. Or I'll have to repeat your question if I can. When you're doing an audit, is it always one person that does it? Or do you sometimes work with a system manager that knows more about that field? Okay. That's a good question. Obviously, people's expertise differ a lot. So you might need an expert of a certain area to do that. So not at all. We do all audits by ourselves, but there's a person who's mainly responsible for writing the report. So small audits yourself, maybe, especially if it's just a regular triple site. You can, you know, pretty much all that's needed. But when it's a big audit or has a lot of different systems around, then you might want to use other expertise you can find in your own company. Okay. I have a question about your reports. Is it not smarter to have the findings and the solutions together instead of two separate chapters? Well, yes, this in a way. But I kind of think that they are not at all always one to one. So there might be three or four findings that can be all solved with just one solution. So there's no connection one to one, but it's one to many or many to one or many to many in the findings and solutions because they're not usually that straightforward. And do you do something like Moscow? Like the must-haves and the should-haves for recommendations? Oh, so I would prioritize the findings and the listings. Yeah, I usually at least somehow explain the severity of the finding or the priority of the fix that should be done, especially if it's a security thing. Then you usually want to say that this is something that you really need to fix. But yeah, you can do a different kind of prioritization or severity listings or severity, whatever. And you can even categorize them by that. I actually have done that. That like critical findings or something like that. Thank you. Anyone else? Okay, then I'll thank you. Take the survey.


What is up YouTube welcome back to the living room we are the October so we've been diving down this horror rabbit hole man And you guys have been saying we need to check out the Blair witch project So this is one of those movies man when I was a kid I was too scared to watch it next thing you know I'm an adult and I just never have so we're finally about to check this out But have you seen this movie? Of course I haven't I don't like scary movies. I already know that I just have to ask you the sort of part of our skit anyways Anyways, man, I know that you have not seen this movie But who directed it Daniel Merrick directed it and also Eduardo Sanchez So I guess I had two directors never seen that before it was a 86% on Rotten Tomatoes and it came out in 1999 So that's a really old movie. I'm sure I personally love old movies. I don't know if this is October Do you love old movies, baby? I like old movies, but like I said, I just don't really love scary movies Like I'm really not excited for this. I'm actually very terrified of this. I'm really excited I think this is gonna be some authentic horror But before we get into the video man, if you guys want to get the early access make sure you're following us on Patreon guys, we're uploading over there like crazy as soon as we get these things recorded we get them over there So enough talking Blair Witch project. Let's get scared. No, okay.  Just the Blair Witch project. You ready? Mm-hmm part of the spookiness in October 1994 three student filmmakers disappeared in the woods near Burkittsville Maryland while shooting a documentary a year later their footage was found Okay, I Just to have one of those things. This is my home. Okay, which I am leaving the comforts of for the weekend Some essential reading how to stay alive in the woods because you never know what's gonna happen And this is a very important book because it has the article about what happened at coffin rock. Hey, it's mr. punctuality I got the CP up. Good. That's what we're shooting on. No one knows. I took it, but I got it This is tripping me out.  So where's Mikey at? We have to go get him Which means we're already gonna be behind schedule. How are you Mike? It's nice to meet you. I'm tired, but I'm doing good I'm really excited about this. Thank you for the opportunity. I'm very glad. Well, thank you for getting the equipment together Uh, we got rice. You got mott's punch. Mm. Hope meal raisin, baby Have you ever heard of the Blair witch? It's kind of scary I actually sound kind of familiar. My older sister went to Blair High School I don't want to go cheesy. I want to present this in as straightforward a way as possible Here he is filling out our first slate for our first shot Should we all like cut our fingers open and bleed on it? Oh, we'll save that for later It took me so long to understand what that thing was until I started making videos and now I get it Oh, he licked it. Do you know what it is? No, they clap it to sync the audio to the camera 200 years ago Many of whom remain either on this hill or in the town below There are an unusually high number of children laid to rest here Well, we have shot the first scene and the opening is shot. Oh, we're doing a documentary About the Blair witch. Oh, yeah, that's an old old store. He lived up on the mountain He had a place up there been there for a long long time. You've heard of the Blair witch several times Well, I've heard I've heard stories about her from people and neighbors and stuff like that Say if you stay up after dark to walk around the house too much a Blair witch All of the winter 1940, uh, some of the young kids started to disappear The creepy That I ever heard She ain't trying to hear that miss Or something that she's supposed to haunt And they disappeared off the face of the earth I'm just telling a scary story, but it's not true It's not true Mr. Pire come down into the market and said I'm finally finished And what did he mean by that? Well, I guess nobody knew at first but the police, uh, funny went up on the mount and uh, They searched this house and they found the bodies of seven kids from the area What he did is he took uh kids down to the basement by Tuesday made one Face into the corner and then he would kill the other one And then when it's done with that he grabbed the one out of the corner and killed that one too Do you believe in witchcraft? No All righty, and you think that it's possible that she's still up there now I don't go up You don't go up there Yeah, I believe enough not to go up there And they say that the the woods are all haunted out there and stuff like that But what do they say? How are they haunted? Well, I don't there really isn't many people that say that it's haunted But there was this old old woman, Mary Brown, crazy lady How was she seen by the community? Crazy That's it the American flag That's Mary's house She's probably the smartest one in the town Take a look around to see what the best light is, all right?  It's just kind of like strange looking Checking my depth of field To see how bad So you measured for meters?  Brown ones are feet But I thought you've used this camera before, man I've used it like once before You've learned a lot about Mary Brown Okay, we're going to do an equipment check But I'm going to call my mom Okay, that's good That's good, thank you Let's be relaxed because we've got a really long day to march Today was cake, pour me a shot please We have any weed? Here I go Drink, drink! There's something about this camera that's just so creepy dude Look on the date too Maybe you see all the ghost footage you've ever seen It's been on one of these old pixelated cameras I know, and it's always grainy looking I've heard of this, I don't really believe much in it Bro, if I saw him at the creek I would not talk to this dude at all He was creepy First of all, can I have your permission to put your image on video For the purposes of a documentary entitled The Blair Witch Project? Yeah, sure, that's all right Some girl back in the late 1800s Supposedly just wandered off Just peered into the woods And she got lost Three days later Appears back on her grandmother's porch Yeah, she was babbling something about An old woman whose feet never touched the ground I like that I like your fall of it So now that you've done that How was that possible? Anybody worth their salt or their nose at this area By that old woman's feet All that bullshit They probably had to use MapQuest back then That's so creepy They all are kind of wild for this So she just got these random people together Found them like AOL or something In the chat room Documentary recording I wouldn't park my car right there I don't think we're going to see that car again They're going to be all dead I want to get her going across, man They went into the woods prepared to find death There was a desecration of humanity at the site Which trappers have often referred to as coffin rock Each man's hands bound to the next man's feet In the torso of each man The intestines had been torn out crudely But upon inspection, the bodies had been removed By persons unknown that happened here At coffin rock Dude, does that happen?  Off the map Wait, wait, wait, say that again I said I knew where we were going Are they lost? I mean what you take on the Blair Witch You think she exists? Right? We like shortcuts, don't we? That's a scary name though, the Blair Witch Oh my gosh It's a little warmer today, so this is the first time we're seeing Mike's chest Mike has really sporadic hair patterns on his chest Terry Blank Is that the Blair Witch? We are hot on the cemetery trail As long as you know where we're going Can you hang? I know exactly where we're going I just feel it's necessary to look at the map now Even though I know where we're going I don't I know we're not lost Did you agree to do this project?  Not about us getting lost We're making a documentary about a witch Just breathe and don't look down, Mamie They said you're going to have to crawl Okay, I'm quiet Dude, you better just walk across So you don't get the camera wet How are we going to get the data cross?  I didn't drop I'm very, very, very close now I guess they figured it out The acting is kind of insane on this Do you think about it? Because it's supposed to look like it's not What is this? Dude, guys, do you remember something that Mary Brown said the other day? What did she say? I don't know if this counts 3, 4, Mamie, stop! Tony! I was just about to scare you But you jumped so fast Well, stop It's for them, it's for them You're kind of like the captain No offense You didn't just knock that over What'd you think? It was, you know, the same thing Only darker Hello? We're sleeping Just keep it by the opening in the tent Hello?             He's laughing Michael that is the first time I've heard you laugh in days I'm really happy You find it very amusing that I'm going to be Incredibly uncomfortable for the rest of the day Can we keep going please?    Does anybody have a reason why we're stopped? What about the plan to keep going south? We all seem very happy with that plan What? What kind of stuff? What?      Where are you? Josh I'm hitting downstairs Is that you down there? He probably got ghosted up Oh my god Her screams scares me That's what I'm getting is anxiety because her screams She shrieks She's not the person I want to die with For sure Now she dropped the camera So you think something hit him He dropped the camera it possessed him And then she walked in there saw him something hit her I don't even know what the hell to think about that Oh my god Alright guys so that was the Blair Witch Project I don't even know what to think about it Honestly it was insanely fun That movie was a lot of fun to watch It just was so suspenseful I would say It was riveting I had no idea where it was going I had anxiety from the moment they got in the woods Because I felt like something bad was going to happen And I honestly thought the movie was going to be about a witch Which I guess it was right But I thought it was going to show the witch more But the thing to me is I thought it was so much better Not seeing her Looking back at this movie now that we've watched it It was about psychosis And going crazy and how people would handle Being haunted in the woods And lost There was so lost The acting was pretty phenomenal In the movie The directing was pretty phenomenal in this movie That was a work of art honestly That was kind of horrific man I don't really have too many things to say about it Other than I had a lot of fun watching it It's a pretty incredible movie Do you have any more movies like this that you guys want to see And maybe ones from that camera angle I wasn't the hugest fan of that But it made it really freaky Yeah just the way they shot the movie And in multiple little angles More in a view style So it was almost like watching it You know when you watch like a serial killer documentary Or something like that And you see the footage because a lot of that stuff happened back in the day Like in the 90s and stuff And that's the vibe you get When you see people on pictures like that It's usually like a home video Like a victim or something It gave you the idea that these people were going to die The whole time they were on film It was just eerie That was a lot of fun guys Love helps, we say it a lot But a lot of you people are watching And comment, comment, comment I try to respond to all of them Yeah you guys are watching A lot of you guys are coming back and coming back But you're not subscribing Kind of weird but you know what I'm saying It is free, if you'd like to do that You should go ahead and do that now So that way you don't miss an upload And yeah come hit us up on Patreon guys We got the $5 here and the $10 here So thank you guys for the suggestion on this movie