Hi guys, Eddie here. Happy Saturday. Today we're going to be discussing the real reasons for the stock market rally. And this is as a response of me getting loads of questions. The economy is meant to be in such a bad shape as a result of the coronavirus. We're seeing huge amounts of riots in the streets. Obviously this worldwide pandemic that shut down every major global economy in the world. Millions are unemployed and yet markets are approaching the highest levels ever. With the Nasdaq making all-time highs. When the stock market is booming, we're meant to think the economy is booming. But what is the stock market measuring? If the economy is in such a bad shape, does this stock market really reflect reality when the world is up in flames? So today we're going to be discussing some of the economic indicators. But also the real reason at the end of the video why I believe that stock markets are rallying at a time of unprecedented, my favourite word, economic crises and civil unrest is destroying the streets of America. We're seeing it in London. Why is the market so bullish about the future prospects and why have we seen such a rapid recovery in markets? And actually not the economy. So to put it into perspective, as you can see by this chart, this is the US GDP and this shrank by 5% in the first quarter of 2020. And this is the biggest drop in GDP since the last quarter of 2008. As basically the coronavirus obviously forced several states to impose lockdowns in mid-March. And this obviously led to mass unemployment in the United States. So what is GDP? It's a key economic indicator of activity. And this is the Atlanta Fed GDP now basically model. And this is measuring obviously the total output of the economy as a result of traditional economic theory. And this is now suggesting that we're going to see negative 53.8% annualized GDP. So this is obviously a horrendous figure and obviously there's talks of whether you should annualize a figure. Just because if we are pricing in that V shape recovery in the economy, then we're unlikely to see a number this bad. But this is what a federal model from the Fed of Atlanta is actually suggesting, which is obviously diabolical. Obviously we saw the jobs report, which was a complete surprise. So we saw 25 million jobs created in America in May. And the forecast was for a loss of minus 7 million by most Wall Street economists and those predicting the figure. But really obviously Trump came out. It's like jobs, jobs, jobs, you know, I'm the best, the stock market's rallying, the job situation's amazing. We created 25 million jobs in the economy in light of this pandemic and everything else going on. But this chart really suggests the reality of it. And millions of people are still out of work. And just because we, you know, lost, we made, sorry, created 25 million jobs in the month of May. This does not, this is not representative of the real damage of the economy. And this, this chart suggests this more than 40 million people have filed for unemployment benefits as a result of this. And as we can see over a longer time frame, average hourly wages, you know, have really not kept up with inflation and they've really done nothing.  And then if you overlaid the stock market to this, you know, there would be a huge disparity between what the average person is really making in terms of their net worth, their wages and things like that. And actually how the stock market has just been booming.  But what this is actually is, is removing the lowest paid jobs from the economy as a result of the coronavirus. So I think retail, leisure, you know, the casinos, hotels, all those, you know, really, I don't want to say unskilled labor, but those that, you know, maybe do not require a university degree have actually been removed from this figure. So then you see the average hourly wage go up dramatically. So this obviously is showing that the people that actually suffered the most from the coronavirus, you know, they're not the, the tech developers at Amazon, you know, they're not the CFOs, these are the people that are earning minimum wage, or something like that. They were unable to work, you know, fueling this kind of bad feeling of raising and rising inequality in America. But the Dow has surged since the March recovery. And obviously this is feeding equity holders. The unemployment rate, 14.7 was reading in April and May was 13.3. You know, and while people may be celebrating and in light of all these riots in response to George Floyd's murder by the policemen. People are celebrating this, but actually the racial disparities remain. Black unemployment has remained virtually unchanged. And this is actually increased in May while the unemployment figure went down 19.6 million jobs are still gone. Obviously 2.5 million jobs coming back. That's not insignificant. But March and April saw 1.4 million and 20.7 million decreases in employment retrospectively. So that means that 19.6 million have still not come back into work. Hospitality and leisure jobs gained 1.2 million, but there's still a 35% jobless rate. And the unemployment rate, whatever you think about that figure that came out, creating 25 million jobs took so many people by surprise. You know, there's something fishy going on there, whatever it is. And the unemployment rate is, in my opinion, definitely higher than it appears. Jobless claims probably are understating the true level of job losses. They don't include pandemic unemployment assistance, and they don't include the mass numbers of workers that were forced to retire. And the African American economic gap remains despite the US expansion. And this is the kind of argument is how can senators in America who have a median net worth of around 1.76 million empathize with the struggles of everyday people that have a median net worth of 97 million. And this is a net worth figure, not a salary. Okay, so this is what, you know, the total assets of people are. So how is it even possible for them to basically suggest and kind of empathize with people if their income and their net worth is so much higher? So how can you make money in the stock market? So this is flipping from the economics to the stock market. So you can make money by investing in an equity either by capital appreciation or dividends. So dividends are essentially this fixed income stream that gets paid out by companies to equity holders. And this may attract more equity investors into this company than thus fueling even more capital appreciation. So what is this capital appreciation? It's essentially when a stock market, when a stock price goes up, the stock market goes up. This is the prospect of the business growing, generating more earnings and the share price increasing. So perhaps you can sell this stock to another buyer at a higher price. And this is why private companies go public for this more, you know, this greater access to capital. And companies realize this, you know, in 1940s or 50s that you can grow a lot faster with outside investments. And this is why these companies have started to go up, go public, sorry. And this is what we're seeing now is software companies surpassing expectations in terms of their IPOs and things like that.  So what's the difference between exchanges and indices that you may ask from a stock market, you know, London Stock Exchange, New York Stock Exchange. The stock index is a gauge essentially to read the whole market of a sector. The stock exchange is where you buy and sell stocks, bonds and other securities that are listed on various exchanges. So what are these indices? These are a collection of different share prices weighted by price, market cap or equally weighted. And what does a stock market really do? It encourages people to invest in new ideas, right, but potentially risky ones like Zoom, Google, Apple, Facebook and Amazon. So this is the problem. So the stock market was originally meant to create wealth for average investors. But really what we see is, you know, huge institutional investors and high net worth individuals holding these equities and obviously really benefiting from the price appreciation, whereas average people do not have access to these equities. Of course they have access, but whether they have the means to buy into it is another story. So in terms of the stock market and why we've seen this rally, 20% of these indices is weighted with the tech names and growth stocks and the lowest skilled labor. They don't get a look in. So without the kind of investment in the poorest neighborhoods, encouraging equality in the boardrooms, all of this prosperity is concentrated with the skilled labor. So the people either working for the company or the high net worth individuals or institutional investors that can own these types of equities. So this rebound has really been driven by, you all know the names Apple, Facebook, Microsoft, Amazon, and they've been able to grow even when the economy doesn't grow. And when the economy does grow, they grow even faster. So Netflix and Amazon are people that have actually benefited from this pandemic when people are locked in, they buy more, they stream more. And the reason we're seeing these stock markets rise, one of the reasons is that tech giants make up such a high proportion of the stock market indices that they tend to have an outsized effect on the broader market. The stock market a glorified beauty contest. So this is something put to them, you know, the economic theory of John Maynard Cain saying, you know, you shouldn't. This is from newspapers where they used to literally say vote for, you know, whoever you think is the most beautiful or pretty. And then they would put collect all the results and that's very different from saying, you know, who do you think everyone else thinks is very pretty or beautiful. Right. And really, that's a good reflection of the stock market. It's not about what company you think the best is the best from a value or a fundamental perspective. It's what do you think other people are going to invest in. So you think of names like zoom, Amazon, you know that other people are looking at these names. More recently, we've seen them bidding up of, you know, really trouble names like Hertz Carnival cruise liners think people like that that are now up 100% 200% obviously from very depressed levels. Originally, but people are piling into these talking about kind of retail investors because they know other people will be buying these types of things. Another reason is the, you know, the thirst for yield. And obviously this is the MSCI world indexing showing that the stock market is recovered dramatically from that March 23 bottom and equities in this are denoted by the MSCI world. And they're trading around 20 times forward earnings, about 30% higher than their historical average. And in the US, obviously, this is from last week's video 24 times it's now around 25.5 26 times with Amazon, Google, Facebook, Microsoft leading the charge. So we've seen these work from home trends dominate obviously that we talked about, but global bond yields are trading around 350 bits 3.5% below their historical average. So the demand for credit funds also reveals this kind of hunger for yield among investors with short term interest rates falling to around zero. So basically the spread that you can get between inequities. So the return, the yield, but inequities versus bonds is much wider than usual. So if we look at the three month performance, for example, treasuries are up 2.3%. Amazon is up 30%. And this is one of the reasons we're seeing a big disconnect between markets and the economy. And lots of people like to include in myself and this was obviously the case. Blame the Fed. So it's nearly doubled its treasury holdings. Since July now to 4.13 trillion. The kind of balance sheet is nearly at 7.5 trillion, which is a huge amount. There's been record issuance in the corporate credit markets because they know they've got the Fed to backstop that. So if you're set if you have anything sell seems like the Fed is going to buy. And I got really interesting quote from Jay Powell from October 23 2012. I think we are actually at the point of encouraging risk taking investors really do understand now that we will be there to prevent any serious losses. So during Powell said it himself in 2012, he was encouraging risk taking and now he's obviously the chair of the Fed. He's now encouraging this moral hazard where we've got these zombie companies that just want to should be bankrupt. And now people are taking speculative bets because you know the Fed are there and investors are ignoring this near term economic, you know, turmoil and opt optimistically looking forward to an expected recovery and any wobble in that you'll see the Fed and any central banks around the world are willing to backstop this and growth versus value is a theory and growth has outperformed value since the global financial crisis. What are these growth and value are two fundamental approaches in styles or stocks where Invest growth is where investors essentially seek companies that offer strong earnings growth momentum, while value kind of investors seek stocks that appear to be undervalued and growth stocks have significantly according to this chart outperformed value stocks over the last decade, and this is changing in the short term more recently we've seen cyclicals like airlines casinos cruise liners banks, really outperforming over the last week or two weeks or so, as this kind of rotation flipped from those kind of growth names. But this could be short term. And I definitely think that the growth kind of beauty stock story will return with the with the vengeance record number of stocks are trading above their daily moving average. What, you know, with record levels of low downside protection, so what could possibly go wrong. Earnings are awful, but that's okay. And if you actually remember the 2000.com bubble, you know, they were tech companies and internet companies were almost encouraged not to try and make a profit or turn a profit. Why because they should be reinvesting those earnings into growing so they could generate them in the future. And if you're an investor, depending on your time horizon you didn't care because the capital appreciation of that stock would go up right and it would increase despite if they're generating earnings and this is kind of eerily similar to what we're seeing here valuations like we talked about have reached a higher since 2000 the dot com bubble, but hedge funds are getting ready for another slump in stock markets, and they're kind of a bit uneasy about this surging prices and it does not reflecting the economic problems ahead and some managers are fearing the equity investors used to buying the dips that ended in the March sharp sell off and you think about how, you know, how vicious that sell off was, you know, I think we're going to see this again, in terms of the steepness of the velocity of that sell off if we do see it. You know, in the future. And, you know, many have become so complacent about how quickly we can recover from this Coronavirus, you know, and how effective these stimulus packages actually will be like we saw with the stimulus checks saving rates went up but consumer expenditure didn't increase but that was the intended measure of the stimulus packages. So they're kind of doubting this kind of stimulus and whether this can be, you know, maintained investors are also very greedy the put cold cool ratio and measurement that's widely used by investors to gauge the overall mood of the market. This is essentially heading back to 0.5 so falling put cool ratio is bullish below 0.7 or approaching 0.5 is considered a bullish indicator. It means more calls are being bought sorry versus puts. Investors are also pumping record numbers 22.5 billion into US bond funds, shifting out of their money market accounts to riskier, more higher paying investments and flows are moving and migrating towards areas of fed support, hence a demand for investment grade and high yield credit. And the yield of the Barclays US corporate IG index has returned to pre pandemic levels of just under 2.5% from a March high of 4.5% last month. Investors have also plowed 4.3 billion into Black Rock's LQD corporate bond fund, which is now inevitably too big to fail so more investors are getting greedy and reaching for this higher yield. So where are the funds putting their money? They're putting money where the flow is going. They're going into money markets year to date, but this trend is starting to shift according to the kind of indicators that we look at if we build this holistic picture. Remember this chart from last week? Where is the smart money flowing? They're selling S&P, they're selling stocks and they're buying gold, so what are they scared of? And this is really the crux of the video. Why are stock markets rallying? It is that they are scared of inflation. So what is driving this market? It's fear. If you have a lot of cash, what happens to your money? If you have money in cash and there's assets, if let's say the stock market or real estate goes up, if you're holding cash, your money is now worth less. And when we're in this kind of irrational trend, people start to follow the crowds when they're scared. They don't care about fundamental valuations. They're chasing these growth earnings momentum stocks just so they don't essentially their money doesn't become worthless. So with all this QE money printing, money literally being created out of thin air being printed digitally, how do you preserve your capital? If you know before you would hold it in cash, you buy assets, right? And this is the stock market like real estate and stocks. But this is why you're seeing the so-called quote unquote smart money buying tips and gold. They are hugely scared of inflation as a result of all of this quantitative easing. It's almost at the point of if Amazon was trading at 5,000, would you care? Maybe not. If NASDAQ was at 10,000, would you care? Maybe not. So this is what people are really scared of. And when the bubble bursts, you can make your own mind up where we are in this kind of stages of a bubble. We could be in this kind of bull trap where really the economic reality and stock markets are completely disconnected. And we're just seeing huge greed taking over. And this is really the reasons why the stock market is rallying in my opinion. So I hope you enjoyed the video and gave you some things to think about. Please leave your comments down below, like and subscribe this video and to the channel. And if you like this kind of longer style, definitely leave your comments down below. Thank you. Have a good weekend and take care.


Item number SCP-918 Object Class Euclid Special Containment Procedures SCP-918 is to be marked on all maps as an artillery range and satellite images of the area are to be altered to corroborate with this cover story. Any instances of SCP-918-1 are to be shot down by on-site personnel, and any instances of SCP-918-1 that manage to leave SCP-918 are to be tracked and prevented from completing their task. Any civilians approaching SCP-918 are to be taken into Foundation custody and dozed with a Class A amnestic. Description SCP-918 is an abandoned mill located in ████. The time and nature of its abandonment are currently unknown, and records do not show any evidence that the mill was ever constructed. All machinery in SCP-918 related to the function of a standard mill is non-functional, and appears to have been stripped from metal. The interior of SCP-918 is filled with machinery of unknown purpose that appears to have been constructed from scrap metal. This mainly constitutes a series of intersecting pipes running through the building, however pulleys and what appears to be the engine of a tractor are also present. Every two months, three creatures resembling members of the syconeidae family will emerge from the chimney on the roof of SCP-918. These will hereafter be referred to as instances of SCP-918-1. Instances of SCP-918-1 when dissected do not appear to possess any skeleton, internal organs or flesh, instead being completely hollow. The method by which they ambulate or function is currently unknown. Witnesses report SCP-918-1 instances communicating with each other in the form of high-pitched clicks and screeches. After emerging, instances of SCP-918-1 will almost immediately begin to fly to an apparently predetermined residence located in the country of ██. The residence of SCP-918-1 flies to will always be home to one newborn infant and two parents. Upon arrival at the residence, SCP-918-1 instances will locate the newborn infant and carefully hold it utilizing their talons. SCP-918-1 instances will then, still carrying the infant, fly back to SCP-918 and insert the infant into the machinery inside SCP-918. Personnel reports a series of loud banging noises emitting from several points of machinery at this stage. After 15 minutes, varying amounts of talcum powder will be dispensed from the endpoint of the mechanisms. SCP-918-1 instances will then climb into the open point of the machinery. Scans of the machinery at this stage show that instances of SCP-918-1 remain in the pipes for 6 seconds before vanishing.


Hello, welcome everybody, here you go, just wait for a couple more people, how are you all going? Alright, yep, excellent, alright so this is the talk labelled beatbox, next generation VM for local development so we're going to discuss a bit about the project we've been working on, it's part of sort of Drupal Melbourne, it's back, so yeah, so my name is Tom Tugged, I'm a Kiwi that's actually living in Melbourne now, yep, still we're having the New Zealand accent of course, and yeah I've been doing Drupal since about 2006, so it's a wee while now, yeah, still loving it, so anyway we'll get started, so today we're basically going to introduce you to this project called beatbox, it is a virtualised development environment, so we're going to start off introducing that concept and make sure everyone understands what that means, we're going to jump into beatbox, talk about why, there's a whole bunch of projects around virtualisation and things at the moment, we'll talk specifically what makes beatbox different, we'll have an overview of the tools that we use to build the project itself, hopefully we'll fit in a few demos that have been recorded for safety purpose, we'll quickly touch on how the project utilises continuous integration and continuous delivery, hopefully introduce you to the way that you can potentially contribute to the project, it is open source, and then touch on the roadmap of where we're going with the project itself. So to jump straight into it, so what is virtualisation? Virtualisation essentially is a way that you can create a machine essentially or something inside something else, it's great for high density applications because you have a single big server and you can run a whole bunch of little machines inside it and try and get full utilisation out of those resources, it's really good for replicating because it's all virtualised, often you can pretty much cookie cut these virtualised things, clone them, back them up easily, and it creates an isolation environment inside a server so you can have a single server with a whole bunch of machines and they can be different operating systems, run different apps and have completely different stacks. So virtualisation is really great for that sort of stuff. So what that means is what does virtualisation mean for development? So it's actually great for allowing you to work on multiple different projects and these can have completely different stacks and also different versions and that sort of thing, but not conflict with each other. So for the triple world you could actually have multiple projects and have varying different versions of Drash, for example, and they will work nicely together. It really lowers that cost of experimentation as well, so you can actually very easily make experimental changes, things that you may or may not work, and quickly roll back because you'd normally take a snapshot of a virtualised environment, test something out and easily roll back. It limits the impact of host updates, so I don't know I've been through it before, but whenever you update your host machine, so your operating system or even your stack, like if you're using Lamp or Wamp, that can potentially impact the projects that you're working on. So this just removes that issue because the machine itself doesn't get updated so it works quite well. It also means that you can often automate the actual build of these virtualisation environments, so there's no real manual task of, especially when you get a new laptop, having to go through and set up all your development tools exactly how you want them, you can often just automate it, script it out and share it with a team. So it leads on to the next one, so it's shareable, which is really, really good for a team environment. It means that you're all working on the exact same machine, essentially, so you're creating something, if it works in one place, it should definitely work in another place. But also for myself, I actually have my machine at home and a machine at work, I'm able to keep them in sync and I don't have to actually carry the laptop around and they're identical, so it's great for shareability. And the whole really concept about it, you don't have to, but you really want to make your development environment as much as close to your production environment and if it can be exactly the same, it's great because essentially any bugs that you see in production, you can very easily replicate and fix up any issues. Plus, you know what you're developing as soon as you deploy it, it's going to run fine on production. So that sort of leads us into Beatbox. So Beatbox is a particular project for creating VMs and managing these VMs and integrating with your project. So it's built with Packer, Vagrant and Ansible and it's, as mentioned, supported and maintained by the Drupal Melbourne community. So a bit of the background is we had a camp last year in a Drupal camp and we were working, there were a couple of people working on similar sort of projects and what we tried to do is establish a baseline, a way that we could actually work at some level that we could share as much as possible but still provide the flexibility to really customise as you needed to. So this essentially was the birth of Beatbox. So the benefit specific to Beatbox is it's actually uses a pre-provision base box which is quite different to most other projects and this really speeds up the actual build time. I've used a lot of Vagrant projects and if you've used it before, sometimes it can take a good half an hour, even an hour to build that initial phase. And the problem there is that you're wasting not only that time but you're more likely to want to fix up and patch your existing environment if you've hit a problem rather than just blow it away and rebuild it.  So this leads on to the next thing is essentially there's a term coined called a pets versus cattle and that relates to how you treat your infrastructure or even your development environment. So a lot of the time, so if you've got let's say a lamp stack locally, you care about it, you treat it like a pet. If something breaks, you want to fix it up and you care about what's actually happening. Whereas with this sort of project, we're basically saying that hopefully the build is clean and it works and if you do run into any problems, the first thing you do is just blow it away and rebuild. That's the best thing to do. Go ahead, yeah. Well, yeah, not vegetarian. Yeah, so the great thing about it, and this came I guess during the development of Beatbox, is we started off with this idea that they would be pre-provisioned. So that means the box comes pretty packaged with a lamp stack, for example, brushes installed and all that sort of stuff. But the really great thing about that is this linked clones concept, which was only recently added to Vagrant. And this basically means that every project that you build from Beatbox is a clone of this base box. So many other Vagrant projects essentially starts with a very base level base box, which would, let's say, is around 200, 300 meg. And then you pre-provision this on top and that would add another 200, 300 meg to the box. And if you do that 20 times, you end up with 20 machines all really huge in size and you do run out of disk space. So linked clones means that we actually have a single master VM, which is the base box. And every project you spin up from that is just a clone and it's changes to the pre-provisioned base box. So it can, you know, each project can actually, the size can be only a couple of meg essentially because only tracking the changes. So that means you actually have hundreds of projects all using the same base box. So we've gone for the way as well, is trying to make it as clean as possible to integrate into an existing project. We really want to make it easy so you can use it or you can actually commit this and integrate it into an existing project and hopefully it will be also vision control. So that means it can be shared around a team or for other developers in the future. We've decided to try and make sure there's the minimal amount of host dependencies. So we really only have Vagrant as a project that we need and virtual box at the same stage. There's a couple of plugins that we still require, but you can only have young windows. Yeah, yeah, that's been a challenge. So, yeah, it's all CI backed. So that just means that we can easily make changes, test them and also provides the stability. So as we roll out new features, it's well tested. Saying that, we practice sort of snapshot releases. So because these boxes are pre-provisioned, we don't release these every day. So every few weeks we'll actually tag a new release and that goes and rebuilds this new base box. Benefit of doing that is that it was tested and built at a point in time and we sort of know it's going to work. So other projects you could be building within an hour period and there could be changes. So this way, it sort of built whatever, two weeks ago. It was stable. It was a known working state. So it's community supported, which is great because it allows anyone to get involved and then provide best practices and whatnot, as well as open source. So we have a very simple abstracted config structure. It's all YAML based. And that is specifically like a descriptive type language rather than instructive. So that means rather than particularly saying install this package, we just say we want this version or these packages or whatnot, I'll get into demos and show you about that. It's very, very highly sensible. So we've got thousands of these config attributes that you can change, but we've also had the ability to really just go nuts and create your own tasks and I'll demo that in a second. So it allows you essentially to keep what your project dependencies or your infrastructure dependencies inside your code base. And that can be version controlled, branched and whatnot. So you can actually, as an example, you can state that you want this project to be on PHP 5.6. You can create a branch and that branch can be on PHP 7. And that means when you build that branch, that branch in the VM will run on PHP 7. And that's great for say migration projects. So while work is still going in the main branch on say 5.6, you're able to test new features and then that upgrade path to 7. So we're focused on making sure it's got a really good modular architecture. So we're, yeah, so basically the project itself is a way that we manage this base box build. All the functionality and the features that we add are kind of like modules and they are externally supported. And that means they also can be reused by other projects, which is really cool. And it really provides that standardized model for both training and onboarding. So I worked on projects before where essentially the first day is basically setting up your development environment because it's a very complex project. What we want to do is throw all the dependencies, all the setup into the project itself to find in config. And basically the setup of a project should be get pull, vagrant up and you get all your dependencies, all the right versions and you're ready to go. So it leads on to sort of the features that come with beatbox by default. So at the moment we do default to 5.6. We've got the Apache 2.4, MySQL. Inside is the latest version, Composer, Drush, Xdebug, Xhprof, Memcache and MailHog. So this is just by default. So if you just pull up a project and don't configure anything, that's basically what you get. But on the other side we've got a whole bunch of optional features that you can enable and configure. So you can upgrade to PHP 7, use nginx as your web server and install other platforms like Node and Ruby and that sort of stuff. So it's really configurable. So I'll quickly touch on the tool set that we actually use to build the project. So it's a vagrant project and vagrant is essentially a wrapper for building virtual machines. So it's a way that you can script and determine a machine that will control a hypervisor and we use virtualbox. And virtualbox is the actual virtualization technology that will run your machine. On top of that we use Ansible. And Ansible is the provisioning layer. So vagrant will set it up, it'll give your machine an IP, it'll sync and just, you know, mount your code base and all that sort of stuff. Virtualbox runs it, Ansible comes in and actually configures that machine and builds it out. So we use Packer. Packer is the tool we use to actually build these base boxes and we do utilize the Packer sort of paid service Atlas and that is all cloud-based SaaS product. So for CI we're using Circle. Circle is really, really good in this case because it allows you to actually SSH into a build and do some debugging. A lot of development actually I do actually on Circle because it means I can just create a fork, test something out, SSH in and essentially develop in a clean environment. And it's all hosted actually on GitHub and yeah. So these are the tools that we use. So we'll get into a quick demo. Hopefully this isn't too small. So to quickly explain what I've done on the side here, it is very, very small, sorry. I've gone and downloaded the latest version of Truffle, which is 8.2.1. So just using Drush. I've entered into the actual project directory. And this is essentially initializing Beatbox. So we're pulling in the project's vagrant file, which you can see on the right there, which is essentially just a stub. Too small. Yeah. Yeah, it's not much really to read, but I can actually show you this file outside, which is a bit easier. We can talk to that after perhaps. But yeah, so just to show you that this is the basic setup of a new project, but this could be an existing project, like an existing code base. And all you need to do is drop this vagrant file into your project. Once that's done and you've got a vagrant virtualbox setup, you'll essentially just run a vagrant up. And that will do a couple of things, hopefully you'll see on the right side there. It's introduced a couple of more directories. And these directories are what you use to basically foil the configuration. So what I can do is actually skip through this bit because this will take about, let's say, five minutes depending on your machine and spec. But in that time, I'll be able to just show you what it's created. Essentially, it's created this beatbox folder for you and this configuration file. And this configuration file is where we'll provide the configuration for the build itself. So after this is built, we can just close that one. What we end up with is this on the side. So this is basically the next result of that vagrant up. We can see that beatbox has come up. We've got the URL. We've got some information about how it can be configured. And this URL here on the right, you can see, allows us to go and install Drupal. So, yeah. Drush ali, isn't it? Yeah, so that's part of the requirements in terms of the plugins. So we do rely on host manager, which is on Windows. Yeah, don't need it. And if you're using multiple domains, you will need it. So explain, that's basically mapping these domains because, obviously, they don't exist in real life. So inside your machine, you've got to be able to map what that domain points to in which virtual machine. So, yeah, so this is the default build. What we do is we grab whatever the directory was, add append local, and that's your default, your default domain. So what we'll do here, so rather than actually going and installing Drupal manually, we're going to add a couple more configuration items here. And you just can't see the text. What we've done is we've added three lines here. We're saying we want to install the site, and then we're saying the account we want will be admin and the password will be admin. Where are the sites? In the docs, yeah. So this is pretty much explaining the quick start guide. So they are on our main readme file. Correct, yes, yeah. So it's pretty simple, yeah. So this is saying, you know, once you get to the point where you know that Drupal's there, we're going to actually install the site and use this user account and password. So as we go along, we're also changing the domain to d8.local just to make it a bit easier. So you can see there. But back on the project, all we do is we basically edit that file, save it, and we're doing a vagrant reload and reprovisioning it. And so what this will do is we'll just restart the virtual machine, read in this config and apply it. So it's pretty simple. So Roland waiting for that. Oh, we'll jump back to here. And this is basically what we end up with again. So we end up with the same thing as before, but the main difference is we've actually now got a login link because we've got a... And we're hacking, yeah. Yeah, so it's really leaked, yeah. Yeah, so this gives you a nice login link, which means that you can just set one-time login link, and it will log you straight into Drupal. And you can share this around to any one, and they can vagrant it up with that configuration, and they'll end up exactly with the same thing. So there's no messing around with databases or installs or anything, which has also made it really good for meet-ups and the like, because we can create projects and demo specific features and share a repository that other people can test. So yeah, so you can see I'm logged in, and these basically Drupal 8.2.1, yeah, PHP 5.6 and all that sort of stuff. So that's all good and well, but... That's Drupal specific, but what we can do is obviously any of these configuration items can be changed. We'll go to the next. So that leads on to extending, and this is what we've touched on with the configuration. So the config.yaml, it's obviously in YAML format. These variables, because we're actually using a whole bunch of external roles, it's a bit of a case-by-case in terms of what they are, but we'll try our best to sort of list some generic examples. And inside the project, we actually have a whole bunch of these variables that you can reuse. So the left here is basically an example of a project which extends, has its own Apache configuration, has some custom modules that we want to enable, sets up sort of the error reporting for PHP, does that sort of thing. So it's all hierarchical as well, so we've inside the project itself, we've got a whole bunch of default config, and this is where you actually don't need anything because it will roll back to another configuration item. So if we removed any of those lines, at some point in the project, there is a setting for it. So the concept of this config.yaml file is you're always overriding something. So you're always wanting to find what it is at the moment and you can go and override what that is. And it's important to know that because let's say for example a list like here, if we were to add a module, let's say just the orphan core, it wouldn't add the other modules because we would actually want to bring in the default ones and add our new ones. So it overrides rather than inherits. So it also means that we can add roles, add roles and roles are these pieces of functionality that allows us to extend and we looked at those features before. So the other awesome part of this is Ansible tasks. So this really allows you to take beatbox and really customize the hell out of it because you may not like what we do, you can disable something and completely extend it. It also is great sort of feeding ground for contributing back to the project because you can create all of these custom tasks and you'll find that for projects you'll reuse a lot of these. And if you start reusing a lot, probably it's helpful for other people and other projects and we can push that upstream and into the project so everyone can utilize these things. So you can use it for installing packages, creating specific config files and a really useful one is importing a database. So yeah, correct. Yes, yes it is. So this is all raw Ansible. There's some documentation about that. But Ansible just has hundreds of modules that you can use. So in the example on the right, we're just using the command module and what this does is it's part of a post deployment that's provisioning and so when we bring up this particular project it will actually do an SQL sync with production environment and bring that down and run updates for you as well. Yeah, that's right. So very easily you can obviously configure this inside the project and just say clone this repository, figuring it up and that can actually go and pull in a database, either a dump or by a drosh. Yep, yeah. Exactly. So and this is where you can actually do a lot of that stuff in config so you can define node packages and do all that sort of stuff in config. But if we didn't have a feature or we didn't support something, you can jump into this custom task situation and really just install anything, configure anything you want. Cool, so quickly look at what's the demo. So this here, we basically just done a quick change of the PHP time zone. Again, just quick edit on the config side and then on the side we just provision it and this basically means that we end up with a server with a time zone change. You can't actually see it, but sorry about that. But you can see you could change your PHP memory limit. Any of these settings are configurable in usually in config. The last quick demo is drosh. So we do support the creation of drosh aliases and we've added now that to be optional. So you add in a new variable there called drosh create alias and that will create an alias for you. In this case, we've called it d8.local and as you can see from the host machine we can just run drosh commands directly inside the VM via a drosh alias. So that's sort of a quick introduction to how the project works. So we also, like I mentioned, practice continuous delivery. The project itself is so fully hosted on GitHub. Everything that the project needs is in that repository and that means to actually go and build and run the tests and everything. So every commit to master inside that project will go and create a new version of beatdev which is our latest development box. So in some cases you want some feature that we've just committed. You can actually override in your configuration and use our latest version of development. It is usually pretty stable. On the other hand, when we create a new release in GitHub that automatically triggers a build of our box which is the default for everybody. And these are meant to be far more stable and we do that sort of every two, three weeks, maybe every month. So yeah, so to add, to contribute, so set a tool on GitHub and we just use the GitHub pull request model where you can actually fork this project. The project by default comes in a state that's fully set up for debugging. So it'll actually sort of mount in any of our custom provisioning scripts and it does all that sort of stuff. So this is where it can be quite confusing for people because they see the project itself and think that you need the project to use the tool. You don't need the project. You just need that vagrant file to get started. But the project itself is fully usable and forkable and you can actually have your own version if you wanted to in the company. There's a contributing guide in our documentation. The biggest thing to remember is because we really strive for that modular architecture a lot of the features and functionality are external. So you might find the feature or change that you're wanting to make isn't actually part of this project. It's somewhere else but we can guide as required. So quickly touching on the roadmap of the project and where we're sort of heading. So we are still obviously using vagrant and virtual machines. This is fairly old technology now and there are really cool tools like Docker and containers and whatnot. The major issue at the moment is support for multiple platforms. Also there's some fairly serious performance issues with mounts and whatnot. So I haven't moved to Docker but that's definitely where we're trying to go and we've even got some proof of concept stuff which basically at this stage demonstrates how bad the performance is but hopefully Docker's... Yeah, it's awesome for CI and we do have a Docker file in the project. So that leads to the next one, better CI integration. So this is where we're wanting to try and make the project work very nicely with that. We're going to look at doing profiles and profiles essentially rather than having to really maintain these lists of configuration. What we'd rather do is say you'd have one configuration item saying I'm running this project on Acquia or Platform or Pantheon and as a community we'd maintain the configuration set for those profiles as talked about containerization and we're more than happy for ideas and features to go into issues required. So I've got to quickly touch on a few things to say thanks. Thanks to the Drupal Melbourne community. We've really been able to be the guinea pigs for this project and thrash out some of the difficulties getting this working. Jeff Girling, who's been referred to as the Dave Reed of Ansible he is the project and maintainer of Drupal VM and we actually reuse a lot of their roles which gives us a lot of synergy between the projects and a lot of the pull requests or work that we do contributes to both projects and features for example like custom tasks we've actually developed it in Beatbox and pushed that up to Drupal VM. He's got a really good book called Ansible for DevOps which I'd recommend if you're interested in getting to Ansible and we've got to thank HashiCorp they actually provide us with a free vagrant enterprise account and that allows us to do all of our builds in the cloud. So yeah, so that's Beatbox and hopefully we have maybe some time for questions. We do, we do. So we've got about five minutes for questions before lunch. So what I'll do is I'll get a show of hands and I'll come over and ask a question here. So this isn't necessarily a question but rather a quick statement I guess. We use Beatbox like I'm heavily involved in it but we use Beatbox for our clients and we're using it at VU at the moment and one of the things that we've done which I'd like to document and add into the process at some point is derivatives of Beatbox which basically means that we've added so many things to our stack on Beatbox like Selenium and Java and Chrome and etc. Things that, you know, we need to provision again on top and there are things that are so big that they take additional time so we had it back at one stage where it was back to 45 minutes. So with Beatbox, with the packer side of stuff, there's very simple ways like I will document at some point to provision your own vagrant base box from Beatbox without hacking it, without forking it just by adding in your additional configuration and then having a pre-provision version for your client specific box. So if anyone is considering it, have a chat to me or look out for a post at some point. Anyone? Thank you, Tom. Thanks, Stuart. Anyone else? I'll jump over here. Yeah, I'm just wondering, do you have any support for legacy PHP versions like 5.5, 5.4, 5.3 or Apache 2.2? So by default, I think we may still support 5.5. But if you needed an older version, you'd have to go down the custom task group and actually, unfortunately, you'd have to remove probably what's there and then install an older version. Yeah, sorry. But shouldn't really be using anything before 5.6 now because I can tell the support. Yeah, certainly sometimes we grab projects from older servers and they're only running on PHP, like 5.4, say. And if it doesn't work on 5.6, our development environment is kind of screwed. So sometimes we have to sort of back port, you know? Yeah, but you shouldn't probably be running any production server on those versions. They're no longer security maintained. So press some errors and move on. Yeah, true. It's internal, it's fine. So Tom, thanks for the talk. That was great. That is a really sensible and well-considered project. So thank you. I commend you and Stuart and Alex and the whole team. And yeah, my only question is, are you planning on doing a t-shirt? Yeah, as in talks. We're also maybe planning on getting a bit of logo, because it's pretty. It's all right, but yeah. I guess we'll create an issue in GitHub. Yeah, you can track it. Oh, yeah, Sprintbox. So yeah, this is another thing. It's a derivative of Beatbox. We're actually working on it at the moment. It's Sprintbox. And we're talking about trying to get this into triple cons and whatnot. So it's a VM which would have everything you need for a Sprint. And that actually includes like an IDE, an IRC client, effectively everything inside a box that you can bring up very easily. So that's also a repository out there. And if anyone's keen to get involved, just let us know. So starting on James there. My question is, like what I find is Beatbox and similar projects like Dribble VM are highly abstracted and they actually take away the experience from a lot of developers of actually understanding what's going on because either that works for them or it doesn't work for them or someone else handles it for them.  Yeah, so I guess we followed that path of Scotchbox. So Scotchbox would be the other big one which actually has a pre-provisioned basebox. The difficulty there is really when you're wanting to make those changes. So when you're wanting to make that tiny little change to the memory limit in PHP, you've really got to get into Bash and you're writing scripts. What about a bit of Ansible on top of Scotchbox? I guess so. Yeah, I guess you could script the Ansible, install and run Playbooks.  Thank you. We've got one time for more. Thanks, Tom. My question is just on the workflow. Like when you actually install the VM, you said you're getting support for an IDE within the VM. So is the expectation that you're developing within the VM or is there a shared folder which is kind of like the VM is exposing through the web server? For Sprintbox? This one? Okay, so this one really, it's designed so that you'd normally have an IDE on your host machine and that will have a folder that is synced inside the virtual machine. I personally don't really ever log into the playground. I use Drush aliases remotely and talk to it. Yeah, thanks. I just want to check on that. That's great. All right, I'm sure we want to get to lunch. I've squeezed one more in there. So just about lunch it'll be out here and we just want you to know that you can either eat lunch here but you can also be about onto the terrace. Don't forget there's a terrace that you can take your lunch out on to eat. So I want to thank Tom. I love Beatbox. I love watching it. I'm glad that Tom did the presentation. Yeah, thanks for joining.


Welcome back fellow techies to our latest tutorial video. I am the technician project and today's tutorials show you how to add automation in Adobe Audition. We're starting off our project today in Adobe Audition with a audio track in a multi-track project. Please see our previous video on how to add and create a multi-track project within Adobe Audition. So we want to add automation to this track. We want to turn it down, we want to turn it up. It's dead easy and dead simple to do. Automation can be used as volume or panning for example. So what we're going to do today we're going to do a bit of panning and a bit of volume editing. So we can edit the volume by using this little pot here and we can edit the panning by using this little pot here. But we don't want to do that. We want to go to automation which is just to click on this little arrow here next to the read symbol and it shows volume here and then we can select volume and that's our yellow line is our zero DB volume and if we want to edit that we can click and it create a node or Audition calls it a keyframe. So we're just going to create two to three to four keyframes. So we've got a fade in a fade out sorry and a fade back in. Let's move it a little bit closer. So let's play it through. Perfect. So we can automate throughout the whole piece by just clicking a node and dragging it down and dragging it up so we can go louder we can go quieter. Lovely. So that's an automation. So if we select show envelopes that shows that volume is being edited. We want to show panning now. We click on panning and it still shows the yellow automation of the volume line is in the background of the panic. Now panning is set one or two ways. So we're going to make a node and we're going to make another node and we're going to bring that up. We're going to create two more nodes and bring that down. So what's it going to do is it going to pan left to right. So from the start it will pan left into the right here and back into the right here. So it goes from right here to left here to right here and we can do that with normal volume so everyone can hear. So that should be coming out to your left speaker now and that should be coming out to your right speaker or headphone depending on what you're listening to. So that is showing panning. We can also show mute. So you can see that the mute line is up. We're going to turn it down so the track is then muted. So if we just do this and draw two more nodes in and draw three nodes in and just do a quick mute in the middle. So that's and you can see the tracks gone great because it's muted out. So the track is on at the top and off at the bottom. So if you click envelope you can see that we've enabled the volume, we've enabled the mute and we've enabled the panning. We can also add EQ and play with effects. Thanks for watching. Don't forget to like the video if you enjoyed it and subscribe for more and also ding dong that notification bell to get further updates. Thanks again. Goodbye.


I was staring at my desktop for a whole minute and I was like, wait a minute, something bad's happening right now, I just know something bad just happened. This video was sponsored by Surfshark, more on them later. If you guys saw my video with the Sea Rabbits, reliving the time I almost fell for an email scammer's tricks, oh my god I have some updates for you. Over the last couple months, I have actually found out exactly what these scammers were trying to do to me. And as you probably guessed it, it wasn't anything friendly. If you missed the original video though, link is in the description so please check that out so you're up to speed. This video was going to be a direct follow up to that whole situation. Once I had uploaded the Getting Scammed online video, I was checking the comments section constantly in case somebody had a similar experience to me. I was hoping that maybe someone would be able to tell me what the scammer was really up to and what damage I had actually managed to dodge, but nothing. There were some great comments though, not going to lie, for example. Reading your comments is always the highlight of releasing these videos, but alas, nobody had any information to offer about the topic. Or actually, maybe alas, isn't the right word there, let's go with… thankfully. I'm glad none of you guys have had any run-ins with scammers like this one. A few days passed and I was browsing my social media for some quality memes and I happened to check my DMs. I was surprised to find a message from a creator who I personally watch and I'm a big fan of, but the message itself was even more surprising to me. After checking out the original video's comments some more, I noticed some people helpfully pointed out another creator who had a similar experience to me. I checked out the video they made on the topic and I couldn't believe it. Exact… same experience as me. I wanted to speak to her.  I've since spoken to all three of these guys and I figured that a nice conclusion to this story would be to hear their side of the story. What's your scammer offering the same brain deal as mine? A game promotion for Epic Games? I have had a fake Epic Games reach out to me multiple times actually, but that's not the ones who scammed me. The ones who actually successfully hacked me and scammed me was a company for a game called Ever Forward. They were offering me $2000 to $4000 to play their game on a video and publish it in two days. They wanted me to get this positive done in two days. Usually I have a week or a month or two months, but two days? That was a little suspicious, not gonna lie. While yes they did also offer me a brain deal to promote their game, it wasn't the same company. Instead it was called quote unquote big game studios which I've never heard of before. No, they were actually offering something called Space Team.  It was like a video editor. I don't even know. The thing that's funny is this is actually a legit game. You can go to Steam and they have Ever Forward as an indie game on there and that's what confused me at first. I was like alright, if it's on Steam I guess it's legit. I guess this company isn't really a scam, it's nothing to worry about. Did you have any hesitation before you opened the file or were there no clear red flags from them? Honestly, this was probably one of the first emails I've gotten with this format. So there weren't that many red flags other than there being a downloadable file. I was kind of like okay, why? There was definitely a lot of red flags. The grammar was off. Their message, obviously they did not speak English as their first language and it all just felt very unprofessional even though they were trying to come off as professional. Which is kind of ironic actually. Nope, I didn't really hesitate at all. At the time nothing was really red flagged to me because this was my first time doing something like this so I didn't really expect anything bad to happen. Big mistake on my part. Back to the thing where they wanted me to do the whole video in two days.  I should have just never responded to them after that. I should have deleted the email and never responded. But I was just, I don't know, it felt like a challenge almost. Two days? I was like alright, let's see if we can get this video done in two days. And I kind of wanted to make a video for them. They were like an indie game company. I thought maybe, just maybe they really need some sponsorships and they're rushing because the game is going to be releasing soon. After you had opened the file, what exactly happened? After downloading it when I clicked on the file and tried to open it, literally nothing happened, despite several attempts, which I thought, hey, that's kind of weird. So I messaged the people and then they said they would fix the issue within a few days claiming that it must have been my PC's fault that the file was not working, which was a lie. I grabbed the file, I put it on my desktop and I double-click it and guess what happens? Nothing! Nothing happens! Like, literally nothing. I guess my cursor moved around a little bit and there was a flash on the screen. But then that's it. There wasn't any game. There wasn't any video. There was no program. It's just silence. I was staring at my desktop for a whole minute and I was like, wait a minute, something bad's happening right now. I just know something bad just happened. My credit card just got leaked or my password just got found out. So for some reason I just decided, okay, yeah, this is trustworthy, sure, it's a demo to the video editor. I was going to try it out. After I opened it, literally nothing happened. My mouse just loaded and then nothing. It's really important to keep safe when speaking to people online and the same goes for you when you're browsing. That's where you need Surfshark VPN, today's sponsor! Surfshark is a powerful VPN which helps you keep your online identity safe by encrypting all the information between you and the World Wide Web. This way, corporations can't use your information for their gain and hackers can't get a hold of your device and data. Phew! Ever wanted to visit London? Boom! Change your virtual location and your laptop is now over there having a nice vacation thanks to Surfshark while you're still stuck at home.  With your VPN set to the UK, you can now access all the media content from that part of the world. From the comfort of your own house. That's the fun stuff though. Now for the serious stuff. Surfshark secures your personal information even when you're out and about using that sketchy free public Wi-Fi. This is where hackers love to hang out and find new victims, but guess what? They're only able to find people who don't have VPNs. So you know. Links below to get started with Surfshark VPN! A VPN makes sure that your city, country and download history aren't linked to your identity. So head to the links in the description to get 83% off plus 3 extra months for free when you use the code jelly. 83% off plus 3 more months free with the code jelly. When did you realise the hackers had access to your information and passwords, etc? I was suspicious of that, but the moment I knew for sure is when I opened Google, I went to YouTube and I found that I had been signed out. So when I tried to sign in, it said, you changed your password two minutes ago. I did not remember changing my password. I knew I didn't change my password and somebody else had changed it and honestly that scared me a lot. Like at that moment I knew I had messed up big time. The worst possible thing in the back of my mind came true. One night I was in my bed and I grabbed my phone because I was going to scroll through YouTube and stuff and then when I went to login it said that I couldn't because the password is wrong. So I told my boyfriend about it and then he said he would be right back to check on it and then when he came back he told me that I was hacked. Well that mainly happened when I got a notification that my password was changed and that was obviously not me so yeah it was kind of concerning. They changed my phone number, they changed the backup email and the backup email is how we knew it was them because the backup email was literally their company name. What emotions did you feel when you had this realisation? Anger, sadness, confusion, but I'll tell you one thing I didn't feel, I didn't feel happy. Happiness was not one of those emotions. I was confused, I didn't know what was going on and then I was just disappointed but at the time I was actually working on a big video so that was kind of my focus. When I realised that I was hacked I freaked out. I mean I was literally about to go to bed and fall asleep while watching YouTube. It was 11 at night so I couldn't even call anyone for help for support. I literally woke up my sister and dad while they were sleeping to tell them about what happened and I was just freaking out and crying and hyperventilating. It was really hard for me to fall asleep that night. I was very confused, I was panicking, I was trying to figure out what exactly I'm gonna do if I could get my channel back, how I would get it back, I really was just in a state of panic. Do you have any idea what they wanted your account for? Was there a specific motive? I assumed they just wanted my account to promote their stupid bitcoin scam because a few days after I was hacked that's when they streamed an Elon Musk bitcoin scam on my channel which didn't really make sense to me because I didn't really think that would appeal to my audience of Roblox players. What they do with their channels that they hack is they try to scam other people because what they did with my channel was it used to be named MV Perry right? Well they changed it to PayPal US. They changed it to PayPal. The main motive was just promoting other people's videos. Nothing really more than that but let's just say people were confused. And then a week after hacking my channel PayPal US starts streaming. It's a live stream trying to get people to donate money to them. After 10 minutes or something the live stream was ended and my whole channel got terminated because all my subscribers could tell something wasn't right. This is not MV Perry. This isn't the channel they subscribed to. So they mass reported my channel and my channel got terminated. I was actually very very dead inside when that happened because when my channel was still up but I didn't have access I thought okay at least I can regain access. But now it was terminated and I thought it was over. I thought this was the end I give up. My channel just got deleted and I'm gonna have to start over from the very beginning. How did you manage to get your accounts back? How long did this process take? So I let people know on Twitter what was going on. I got in contact with Google support and I remember it took 10 full days for everything to come back which might not seem like a lot but at the time it felt like forever. I'd say I definitely got my account back through awareness being spread. I made a post on Twitter telling people what happened. I got a hectic ton of support from creators and people in the Roblox community. If it weren't for all of that I definitely would have been waiting a much longer time to get my account back. So to get my account back the first step I took was I went to Twitter and I immediately started tagging Team YouTube asking them guys please please save me please help me. Eventually they got me in contact with their internal team on their email so I started emailing back and forth but it got to the point where I was only going to get a response every two days and the response was something stupid like did you remember to turn off your caps lock? Yes YouTube. My channel got terminated you got to do more than this is not enough. Eventually after three weeks of these tedious back and forth emails YouTube finally sent me a wonderful golden email that said we found that you are the original owner of the channel and we are going to restore it and all the videos on it. Sorry for the inconvenience something like that. Since the hackers changed all the information it took a little while to verify that it was me I'd see it throughout the whole process it took around two weeks which actually isn't bad at all. It was overall just a learning experience. I will never ever accept a sponsorship if it has a red flag. I won't accept it if it has half a red flag. That's if it does anything suspicious whatsoever. I'm just gone like I'm not taking those chances it's too much of a risk and I suggest that to all YouTubers or anyone who is trying to become a YouTuber. If you're getting weird sponsorship emails and something seems a little bit off even just a little bit do not trust it it's not worth the risk of losing your channel. The hacker smells like doggy doo doo. If I was in their situation I too would be so upset and definitely would be freaking out. I find it really cool to see the creators audiences as well as other creators like work together to try and bring the channel back. Just seeing all the support on other social medias is just really cool. Really wholesome. I'm also really glad to see that these guys didn't lose their channels or their previous videos. And to other creators out there who may be watching please be aware of these scams um these people have no life. Again huge thank you guys for being so open and for offering an ending to an otherwise unfinished story.


From around the globe, it's theCUBE with coverage of SousaCon Digital, brought to you by Sousa. Welcome back, I'm Stu Miniman, coming to you from our Boston area studio and this is theCUBE's coverage of SousaCon Digital 20. Happy to welcome to the program two of the keynote present presenters. First of all, we have Dr. Thomas DiGiacomo. He is the president of engineering and innovation and joining him, his co-presenter from the keynote stage, Daniel Nelson, who is the vice president of product solutions, both of you with Sousa. Gentlemen, thanks so much for joining us. Thank you, thank you for having us. All right, so Dr. T, let's start out, innovation, open source. Give us a little bit of the message for our audience that you and Daniel were talking about on stage, how we've been watching for decades, the growth and the proliferation of open source in communities. So give us the update there. Yeah, and it's not stopping. It's actually growing even more and more and more and more innovations coming from open source. The way we look at it is that our customers, they have their business problems, they have their business reality. And so we have to curate and prepare and filter all the open source innovation that they can benefit from because that takes time to understand how that can match your needs and fix your problems. So at Sousa, we've always done that since 27 plus years. So working in the open source projects, innovating there, but with customers in mind. And what is pretty clear in 2020 is that large enterprises, small startups, everybody is doing software, everybody is doing IT, and they all have the same type of needs in a way. They need to simplify their landscape because they've been accumulating investments, hardware, infrastructure, software, different solutions, different platforms from different vendors. They need to simplify that. They need to modernize and they need to accelerate their business to stay relevant and competitive in their own industries. And that's what we are focusing on. Yeah, it's interesting. I completely agree when you say simplify thing.  So it gives a little bit of insight as to, you know, the impact this is having on ecosystems and of course, you know, Susie now has a broad portfolio of that at all. It's a great question and I totally get where you're coming from. Like if you look 20 years ago, the landscape is completely different. The technologies we're using are completely different. The problems we're trying to solve with technology are more and more sophisticated. You know, at the same time, though, you know, there's kind of nothing new under the sun. Every company, every technology, you know, every, you know, modality goes through this expansion of capabilities and then the collapse around simplification as the capabilities become more and more complex and manageable. And so there's this continuous tension between capabilities, ease of use, consumability. What we see with open source is that, that's kind of dynamic, it still exists, but it's more online of like developers want easy to use technologies, but they want the cutting edge. They want the latest things. They want those things within their packages. And then if you look at operations groups or people that are trying to consume that technology, they want that technology to be consumable, simple. It works well with others. Be able to pick and choose and have one pane of glass to be able to operate within that. And that's where we see this dynamic. And that's kind of what the SUSE portfolio was built upon. It's like, how do we take, you know, the thousands and thousands of developers that are working on these really critical projects, whether it's Linux, like you mentioned, or Kubernetes, or Cloud Foundry, and how do we make that then more consumable to the thousands of companies that are trying to do it, who may even be new to open source, or may not contribute directly, but want to have all the benefits that are coming to it. And that's where SUSE fits, and where SUSE fits historically, and where we see us continuing to fit long term is taking all those Legos, put them together for companies that want that, and then allow them a lot of autonomy and choice and how those technologies are consumed. One of the themes that I heard you both talk about in the keynote, it was simplify, modernize, accelerate really reminded me of the imperatives of the CIO. There's always run the business, they need to help grow the business, and if they have the opportunity, they want to transform the business. I think in the keynote you said, run, improve, and scale. Scale, absolutely, you know, a critical thing that we talk about these days. When I think back to the Cloud Foundry Summit, in the keynote stage, it was in the old way, if I could do faster, better, cheaper, you really could choose two of them. Today, we know faster, faster, faster is what you want. So give us a little bit of insight as to, you talked about Cloud Foundry and Kubernetes, application modernization. What are the imperatives that you're hearing from customers and how are we with all of these tools out there helping IT not just be responsive to the business, but actually be a driver for the transformation of the business? It's a great question. And so when I talk to customers, and Dr. T, feel free to chime in, you talk to as many or more customers than I do. They do have these, what are historically competing imperatives. But what we see with the adoption of some of these technologies is that faster is cheaper, faster is safer, you know, creating more opportunities to grow and to innovate better is the business. It's not risk injection when we change something, it's actually risk mitigation when we get good at changing. And so it's kind of that modality of moving from, you know, a simplified model or a very kind of like manufacturing model of software to a much more organic, much more permissive, much more being able to learn with an ecosystem model. And so that's how we see companies start to change the way they're adopting these technologies. What's interesting about them is that same level of adoption, that same thought of adoption is also how open sources is developed. Open sources developed organically. It's developed with many eyes, make shallow bucks. It's developed by like, let me try this and see what happens, right? And being able to do that in smaller and smaller recommends, just like we look at red-green deployments or being able to do microservices or canary or any of those things, it's like, let's not, you know, do one greatly forward, but we're used to in waterfall, because that's actually really risky. Let's do many, many, many steps forward and be able to transform iteratively and be able to go faster iteratively and make that just part of what the business is good at. And so you're exactly right. Like those are the three imperatives of the CIO. What I see with customers is the more that they are aligning those three imperatives together and not making them separate, but we have to be better at being faster and being transformative. Those are the companies that are really using IT as a competitive advantage within their industry. Yeah, because most of the time they have different starting points. They have an history, they have different business strategy and things they've done in the past. So you need to be able to accommodate all of that. And the faster microservice, start native development for sure for the new apps, but they're also coming from somewhere. And if you don't take care of that together, you can just accelerate if you simplify your existing because otherwise you spend your time making sure that your existing is still running. So you have to combine all of that together. And Stu, you mentioned Cloud Foundry and Kubernetes and that's really, I love those topics because, I mean, everybody knows about Kubernetes. Now it's picking up in terms of adoption, in terms of innovation, technology, building AI, ML framework on top of it. Now what's very interesting as well is that Cloud Foundry was designed for fast software development and cloud native from the beginning. The 12-factor apps and several like four, five years ago, right? What we see now is we can extract the value that Cloud Foundry brings to speed up and accelerate your software development cycles. And we can combine that very nicely and very smoothly, in a simple way, with all the benefit you get from Kubernetes and not from one Kubernetes. From your Kubernetes running in your public clouds because you have workloads there, you have services that you want to consume from one public cloud. We have a great Suzecon fireside chat with Alpansha from Microsoft Azure, actually discussing those topics. Or you might have also Kubernetes clusters at the edge that you want to run in your factory or close to your data and workloads in the field. So those things, and Daniel mentioned that as well, taking care of the IT ops, like simplify, modernize and accelerate for the IT ops and also accelerate for the developers themselves with benefiting from a combination of open source technologies. And today there's not one open source technology that can do that. You need to bundle, combine them together at best, make sure that they are integrated, that they are certified together, that they are stable together, that the security aspects, all the technology around them are deep integrated, the services as well. Well, I'm really glad you brought up some of those Kubernetes that are out there. We've been saying for a couple of years on theCUBE, Kubernetes is getting baked in everywhere. Suze's got partnership with all the cloud providers and you're not fighting them over whether to use a solution that you have versus theirs. I worry a little bit about how do I manage all of those environments? Do I end up with Kubernetes sprawl just like we have with every other technology out there? Help us understand what differentiates Suze's offerings in this space and how do you fit in with the rest of that very dynamic and diverse. So let me start with the aspect of combining things together. And Daniel, maybe you can take the management piece. So first of all, we are making sure at Suze that we don't force our customers into a Suze stack. Of course, we have a Suze stack and we're very happy if people use it. But the reality is that our customers, they have some investments, they have different needs, they use different technologies from the past or they want to try different technologies. So you have to make sure that for Kubernetes, like for any other part of the stack, the IT stack or the developer stack, your pieces are modular that you can accommodate different elements. So typically at Suze, we support different types of hypervisors. We're not focused on one, but we can support KVM, Zen, Hyper-V, V-Sphere, all of the Nutanix hypervisor, NetApp hypervisors and everything. Same thing with the OS. There's not only one Linux that people are running and that's exactly the same with Kubernetes. There's no one probably that I've seen in our customer base that will just need one vendor for Kubernetes because they have a hybrid cloud needs and strategy and they will benefit from the native Kubernetes they found on AKS, EKS, GKE, Alibaba clouds, you name them. And we have cloud vendors in Europe as well doing that. So for us, it's very important that what we bring as Suze to our customers can be combined with what they have, what they want, even if it's from the so-called competition. And so the Suze Cloud Fundry is running on AKS. You can find it on the marketplace of public clouds. It could run on any Kubernetes. It doesn't have to be Suze Kubernetes. But then you end up with a lot of clusters, right? So how do we deal with that, Daniel? So it's a great question and I'll actually even broaden that out because it's not like we're only running Kubernetes. Yes, we've got lots of clusters. We've got lots of containers. We've got lots of applications that are moving there. But it's not like all the VMs disappear. It's not like all the beige boxes, like in the data center, like suddenly don't exist. You know, we all bring all the sins and decisions of the past forward with us wherever we go. And so for us, it's not just that lens of how do we manage the most modern, the most cutting edge. That's definitely a part of it. But how do you do that within the context of all the other things you have to do within your business? How do I manage virtual machines? How do I manage bare metal? How do I manage all those? And so for us, it's about creating a presentation layer on top of that where you can look at your clusters, look at your VMs, look at all your deployments and be able to understand what's actually happening within your environment. We don't take a prescriptive approach. We don't say you have to use one technology or you have to use that technology. What we wanna do is to be adaptive to the customer's needs and say, you've got these things. Here's some of our offerings. You've got some legacy offerings too. Let's show you how to bring those together. Let's show you how you modernize your viewpoints, how you simplify your operational framework and how you end up accelerating what you can do with the staff that you've got in place. Yeah, I'm just on the management piece. Is there any recommendation from your team? Last year at Microsoft Ignite, there was the launch of Azure R. And we're starting to see a lot of solutions come out there. Our concern is that any of us that live through the multi-vendor management days, don't have good memories from those. It is a different discussion if we're just talking about kind of managing multiple Kubernetes, but how do we learn from the past and what are you recommending for people in this multi-cloud era? So my suggestion to customers is you always start with what are your needs? What are strategic problems you're trying to solve? And then choose a vendor that is going to help you solve those strategic problems. So it isn't going to take a product-centric view, it isn't going to tell you use this technology and this technology and this technology, but it's going to take the view of like, this is the problem you're going to solve. Let me be your advisor within that and choose people that you're going to trust within that. That being said, you want to have relationships with customers that have been there for a while, that have done this, that have a breadth of experience in solving enterprise problems. Because I mean, everything that we're talking about is mostly around the new things, but keep in mind that there are nuances about the enterprise, there are things that are intrinsically bound within the enterprise that it takes a vendor with a lot of enterprise experience to be able to meet customers where they are. I think you've seen that in some of the real growth opportunities within the hyperscalers as they've kind of moved into being more enterprise view of things, kind of moving away from just an individual developer's perspective to enterprise problems, you're seeing that more and more. I think vendors and customers need to choose companies that meet them where they are, that enable their decisions, don't prescribe their decisions. Okay. I want to make sure we- Let me just add to that, I think- Please go ahead. Yeah, sorry, it's true. Yeah, I also wanted to add that I would recommend people to look at open source based solutions because that will prevent them to be in a difficult situation potentially in a few years from now. So there are open source solutions that can do that and look at viable, sustainable, healthy open source solutions that are not just one vendor but multi-vendor as well because that leaves those options open for you in the future as well. So if you need to move for another vendor or if you need to complement with an additional technology or you've made a new investment or you go to a new public cloud, if you base your choices on open source you have a better chance to accommodate a lot. I think that's a great point, Dr. T. And I would, you know, glom on to that by saying customers need to bring a new perspective on how they adjudicate these solutions. Like it's really important to look at the health of the open source community. Just because it's open source doesn't mean that there's a secret army of gnomes that, you know, in the middle of the night go and fix bugs. Like there needs to be a healthy community around that. And that is not just individual contributors. That is also, what are the companies that are invested in this? Where are they dedicating resources? Like that's another level of sophistication that a lot of customers need to bring into their own vendor selection process. Excellent, you know, speaking about, you know communities in open source, want to make sure you have time to share a little bit about the AI platform that we've discussed in your... Yeah, it's very, very interesting. And something I'm super excited about at SUSE. And it's kind of this, we're starting to see AI done in these really interesting problems to solve. And like, I'll just give you one example is that we're working with a Formula One team around using AI to help them actually manage in-car mechanics and actually manage some of the things that they're doing to get super high performance out of their vehicles. And that is such an interesting problem to solve. And it's such a natural artificial intelligence problem that even when you're talking about cars instead of servers, you're talking about race tracks, you know, instead of data centers you still got a lot of the same problems. And so you need an easy to use AI stack. You need it to be high performance. You need it to be real time. You need to be able to get decisions made really quickly. These are the same kinds of problems, but we're starting to see them in all these really interesting wheel-weld scenarios. Which is one of the coolest things that I've seen in my career, especially as it turns out of IT, is that IT is really everywhere. It's not just grab your sweater and go to the data center because it's 43 degrees in there. You know, it's also get on the racetrack. It's also go to the airfield. It's also go to the grocery store and look at some of the problems being addressed and solved there. And that is super fascinating. One of the things that I'm super excited about in our industry in total. All right, well, really good discussion here. Daniel, Dr. T. Thank you so much for sharing everything from your keynote and been a pleasure watching. Thank you. All right, back with lots more coverage from SUSECON Digital 20. I'm Stu Miniman and as always, thank you for watching the Q.


ceiling! Ssssssssssssssssssssss That's drunk! With the arrival of stuff like the NES classic, SNES Classic, and all the other new plug and play retro systems, lots of people are rediscovering older games they'd forgotten about, and as a result many folks are now getting their kids into retro games as well. To try and help out, I made a video about the best kid-friendly games on the Super Nintendo a year ago but I have to admit there's one glaring one I forgot, and Believe it or not, it's Super Widget. This one's actually a licensed game based on the cartoon Widget the World Watcher, which aired for 65 episodes between 1990 and 1992. You play as a 4 foot tall purple alien who's named Widget, and he's hell-bent on protecting the Earth from evildoers who pollute and exploit the Earth's environment and natural resources for profit. And before you say this is a rip-off of Captain Planet, this show arrived just about at the same time as that show did, although in my opinion Widget is slightly less overbearing and obnoxious, and the art style and design has more of a Hanna-Barbera feel to it. Widget first arrived on the NES as just your standard side-scrolling platformer before the sequel Super Widget arrived on the Super Nintendo a couple years later as a, you guessed it, a standard side-scrolling platformer. Both games were developed by Atlas, and when you think of Atlas, most people think of Shin Megami Tensei, or the subsequent series Persona, so these games keep some very strange company. Now, when I first played this one, I was ready to dismiss it as a waste of time because after 30 minutes I had steamrolled through the game without dying once. Not because I completed the game, I just got bored. There is next to zero difficulty here, but then I realized, oh yeah, duh, this game is based on a kid's cartoon, and the game is targeted to kids, not for 37-year-old doofuses like me. And that's one question I still get pretty often from dads out there that say, hey, I want my 4 or 5-year-old to get into retro gaming, but stuff like Super Mario World and the Mario All-Stars games are just too difficult for them. What do you recommend? So in addition to stuff like Kirby Superstar, Doraemi Fantasy, and Super Adventure Island, I'd have to put Super Widget up there too. No, this game definitely is not perfect. The controls are slow to respond, and Widget has a certain weight and momentum to him that's a little hard to get used to. But the level design is pretty straightforward, the enemy design is exceedingly simple, the boss fights are super easy, and the game is really colorful and playful looking, featuring all sorts of environments and settings. In addition to being easy, Super Widget is also really forgiving. You get 4 lives and 3 continues to get through over 30 stages in several different worlds, and there's tons of opportunities to get extra lives. There is a password system as well. Now, the key to this game being such a breeze is the transformation or shape-shifting power-ups that you find throughout the game. Widget can change into up to 12 different characters, everything from an ostrich, a wasp, an octopus, a dragon, or just kind of a superhero looking guy, I guess? There's two tiers of power-ups, for example, when you're the lobster and you find another transformation power-up, you turn into an octopus. Hey man, I don't know how or why, that's just, you know, how the game is laid out, man. Take one hit as an octopus, and you revert back into a lobster. Take one hit as a lobster, and revert back into Widget.  But bear in mind, there's plenty of other power-ups here as well, like Force Fields and the like. Super Widget may be kid-friendly, but it's definitely still a flawed game. There's some serious issues with hit detection and with the platforming. It's one of those games like Wizard of Oz where, for whatever reason, you just can't friggin' land on the platform you want to, so that can be frustrating. Also, when you're stuck as just Widget, his attack is a straightforward punch. And it's pretty lousy, especially when you're trying to hit flying enemies. So yeah, if you're someone around my age and you play Super Widget, you're likely to get bored and or frustrated within about five minutes. But that's because you're not the target audience for this one. This game is clearly made for kids of a certain age, and if you consider that, this game does a good enough job. The pixel art is well done, the art direction is good, the music is good, the game is super forgiving, and the gameplay features some cool power-ups that get more interesting the further you progress. So yeah, for kids of a certain age, Super Widget gets the job done. Just don't expect that age to be 37. Alright, I want to thank you for watching, and I hope you have a great rest of your day.


Item number, SCP-699. Object Class, Euclid. Special Containment Procedures SCP-699 is to be kept in a standard 8 meter by 8 meter by 5 meter research bay, which was built around the object in the sub-basement of Site 83. The object shall be guarded at all times, by two level one personnel who have had a negative reaction to the object, see below, and have shown no interest in opening it. In addition, the artifact is to be kept under video surveillance at all times. Unauthorized attempts to open SCP-699 will be met with severe disciplinary procedures, up to and including termination. Any signs of an escape attempt by the contents of SCP-699 must immediately be reported to a level 4 staff member, so that further containment procedures can be initiated. Any containment breach is to be met with full force. Description SCP-699 is a clear rectangular case, 2.5 meters by 1.5 meters by 1 meter in size. Engraved on one side is the SCP Foundation Ketter symbol and SCP-17591. The artifact appears to be plexiglass, but is in fact a super dense polymer, much stronger and heavier than any material currently manufactured. The weight of the object is estimated at 24,000 kilograms. SCP-699 shows no seams in its construction and no obvious means of opening it. It has resisted all attempts to open, damage, or acquire a sample of the material it is composed of, attempts to acquire a small sample of the material so that it can be reproduced or ongoing. The contents of SCP-699 are under investigation and currently in dispute among researchers. The contents of SCP-699 are apparently telepathic and appear differently to most observers, depending upon their desires in psychological state. 90% of observers see the contents in a positive way, as something they want to possess or to release. These viewers have reported seeing precious metals, artwork, family members, pets, religious figures and apparently useful technology contained in SCP-699 and experience a strong desire to open the container. Approximately 9% of observers have a negative reaction to SCP-699's contents and view something frightening or dangerous. Reported contents have included spiders, snakes, demonic humanoids and other dangerous SCP artifacts, including SCP-1. These observers do not exhibit any desire to release the contents of SCP-699. Two observers, Dr. Wu and Dr. Wu, have observed the same thing when viewing SCP-699. They claim it is entirely empty, it's obviously just a prank. Dr. Wu, the contents of SCP-699 are capable of appearing in different forms simultaneously to multiple observers. Within the form-masking telepathy and the transmission of a desire to be released, SCP-699 has not attempted to communicate with anyone. Addendum, SCP-699 was first discovered when it appeared in the third floor break room of Site-83 at 3.14 am on f***ing 2000 f***ing. Due to its weight, it immediately crashed through several floors of the site, landing undamaged in the sub-basement. Unfortunately, it caused $1 million in damage to the building, released SCP-1 and SCP-1 was crushed beneath it upon landing. SCP-699 is too heavy to move without causing major structural damage to Site-83, so containment was built around it. A partial report on SCP-699 was found attached to the artifact. This report is for level 4 and above eyes only. Unfortunately, most of the report was damaged when SCP-699 arrived and is unreadable. Item, SCP-17591, Object Class, Keter, Date of Capture, 7-6-24-55, Researcher in Charge, Dr. B, Notes, 7-6-24-55, SCP-17591, who calls report damaged, self, report damaged and unreadable, desires to implement report damaged, referred to as Protocol Z within this document. As this is obviously undesirable and given subject's ability to report damaged, placed in a standard Keter class containment vessel, report damaged. Added data expunged to containment protocol to prevent report damaged after escape or recapture and extensive damage to Site-83. Ability to inflict report damaged, Protocol Z at a distance of 5 report damaged for concern. 8-7-24-55, Escape Attempts Continue, Subversion of Site-83 personnel required termination of Dr. B and Researcher B, Report Damaged, 2-7-24-66, Escape Imminent, Experimental Containment Procedure T to be implemented immediately. We believe the inhabitants of the receiving timeline lack the Report Damaged and Will for many years. Note from the Records Clerk. I am not about to mess up our database and call this thing SCP-17591. It is SCP-699 until further notice. Note from 05, Do not start tossing recalcitrant or dangerous artifacts into the nearest dimensional portal. It is clearly not safe for many of the items under our control, and there is significant debate among senior staff over whether it should ever be done. Lesson complete. If you missed the previous orientation, go watch SCP-698, Judgemental Turtle, right now, or for the complete course, watch this playlist.