Now, so far, we've only been creating actions where it's me clicking on a button, but what happens if I want to do something with my mouse? Say for example, I want to take my BTN OK, and I want to indicate when the mouse actually kind of enters in, when it kind of gets the mouse over it, what do I want to do? So what I can come in here, and I can do the exact same thing I did with my set on action, I can actually come in here and I can go BTN OK, dot, and now instead of doing set on action, which is the button being clicked, set on mouse. Now as you notice I start to type out mouse, I get a whole slew of options that I can work from. On mouse, click, on mouse, drag, enter, on mouse, drag, exit, on mouse, drag, drag over, enter, exit, moved, pressed, clicked, released, I have so many mouse actions, if we think about it, that's really the case. I have things like my drag and drop method, I have just moving my mouse over it. Let's say for example, I want to deal with when I kind of enter in. Now what I'm going to do before I work on the Lambda expression is I'm going to do the old fashion way, the inner anonymous class, the event handler. Now instead of this being an action event, this is actually a mouse event, and the exact same thing comes into play. I throw in my curly braces and then my squigglies. Now it's airing out only because I must implement the handle method just like when I used an action event. And so again, what's it complaining about? I need to import this just like always, all right. I imported my, just to show that off, I imported scene.input, I'm going to just put the star there because that way I don't have to worry about the errors again. And now because of this, this event, again, it's just my parameter. This is no different than when I did AE for action event. I can do ME for mouse event. I wouldn't actually do that, ME, that sounds me, naming of that. I'm going to keep it event. I really wouldn't go with ME for mouse event. That doesn't sound, that sounds like it might be more confusing than helpful. But now what I can say is, oh, when the btnok, when the mouse enters into btnok, I want it to say something. And for my sake, I'll just have it say system.out.println, okay, button, mouse over. I run it, and as soon as I mouse over it, I can do this with all of them as you can guess. What I can do is I'm going to go ahead and just take this exact same code, and instead of entered, we're going to do 1, 4 when it exits, exited, mouse over, exited, mouse no longer mouse over. There we are, no longer mouse over. Ha, I run it again, now I mouse over the okay button, boop, as soon as I leave the okay button, boop, I'm no longer mouse over. So I can now kind of do this back and forth between it. So let's see if we can't maybe do something with that. So I mouse over, entered. So let's see, the btnok.set, let's see, where are you, where were you, set, we'll just do text fill for right now, color.rgb, or we'll just do color.red, why not, color.red. Make sure to import our color, I know, all these imports, craziness. Now when I run this, what should happen when I mouse over it, boop, my color turned red, ooh, my color didn't change, well guess what we can do, we can come back over here, take the same command, maybe put it over here, and instead put it back to black. Again now I run through this, and now I'm pretty much making sort of that indication, I get, you know, I get that effect for buttons just by default, but now I'm saying do a little bit more, ooh, look at that, make it red, make it not red, make it red, make it not red, make it red, make it not red, red. So we can continue to advance this out, one more thing I'll do is, again, let's reduce it down, let's do that lambda expression for now, set on mouse entered. These are the only two commands I want, and I have to do one, two, three, four, five, six lines for that now. What, what are we, are we in the stone ages here or something, let's just reduce that down to the bare essentials, let me just say event dash greater than, again that's for my lambda expression, boom, boom, boom, look at that, beautiful, I'm going to take that same code, I'm going to put it again for my BTN, let's see where are you, there you are, BTN exited, no longer black, so I've done the exact same thing just with lambda expressions, I've reduced how much I have to type, let's take a look at what happens when I run it, mouse over, ooh, oh, ooh, oh, ooh, oh, all with now just four lines of code.


How many tabs do you have open right now on your computer? One to two tabs, five tabs, 10 plus tabs? I mean, if you only have one tab open right now, you deserve a round of applause. Multitasking does not make us more productive, but it's always helpful to have multiple tabs open to reference different screens. In ClickUp, you can reference multiple items and save items for later using the tray. Simply open up a task or document, click on the move to tray button in the top right, and easily navigate through your docs and tasks in the bottom right corner of your screen. So have you used the tray in ClickUp?


The study aimed to characterize physiologic changes in response to COVID-19 vaccination in a small cohort of participants using a wearable device, Woopstrap 3.0. The primary outcomes were percent change from baseline in heart rate variability, HRV, resting heart rate, RHR, and respiratory rate, RR. Secondary outcomes were percent change from baseline in total rapid eye movement and deep sleep. The study found that HRV decreased on day one following administration of the first vaccine dose and second vaccine dose, with no significant changes in RHR or RR. Sleep duration initially decreased following each dose with a subsequent increase thereafter. Increased sleep prior to vaccination was associated with a greater change in HRV. The study raises the possibility that increased sleep prior to vaccination may impact physiologic responses and may be a modifiable way to increase vaccine response. This article was authored by Alexander G. Hadjiksok, Kara M. D. Joseph, Brinny Bent, and others. We are article.tv, links in the description below.


Mi yw Neil Amatage. I'm a deployment engineer for Continuant, basically Continuant provided a software platform for making highly available database clusters. I'm a DBA for about 25, 26 years, which is a scary number nowadays, and I do deployments for Continuant. We tend to do two or three deployments a week, and these are all done remotely, so I actually live locally here, but work generally around the world. I'm also a developer for their cloud operations team, so I sort of wear two different hats. This talk came about, because we were doing an awful lot of deployments for customers, and they suddenly wanted to go in the cloud, and they hadn't really thought about the differences. They'd been in on-premise deployments for years, essentially, and they thought they knew how to do things, and then they started to move into the cloud, and they were using the same mentality. So, if you do an on-premise or a co-location deployment, you'd generally raise a project, then you'd need to get that signed off various levels of management, then you'd have to order the hardware, which could take sometimes a month to arrive. Then you'd have to get someone to rack and cable it. In a large company, that would be a totally different team. Then it would need to be connected to the network, which, again, could involve paperwork, get an IPs. Then you'd normally have to get someone else to install the operating system. Then it would quite often need to be connected to the SAN. And all of that was different teams. And that could potentially take weeks, months. I've actually seen stuff like that take years. And you end up with a nice rack of hardware neatly cabled. Some guy, normally me, would spend an afternoon making the cables and all neat and tidy and labelled. And then we started moving into the cloud. And all you needed to get your data centre up and running in the cloud was someone's credit card. You'd call an API, an open stack, that would give you three servers. And that would do the same in Amazon. Bang, you've got your servers up and running. Quite often people would go and deploy in production like that without really thinking about what they were doing. There's various cloud providers out there. Amazon is still the king in this market. We deal 90% of our cloud, actually 99% of our cloud deployments are in Amazon still. We deal a little bit with Rackspace. I haven't come across HP Cloud yet. We do an awful lot of on-premise clouds in VMware. That's quite common in big companies. I haven't seen open stack in the world yet, but we use it internally for testing development. So in Amazon, if you spin up a server, where does it actually exist? Amazon have seven or eight data centres all around the world. If I'm working with a European company, we're normally restricted using the Irish data centre, because in the EU you want your data within the EU, essentially. So that cuts down the number of data centres you can use. Each Amazon data centre is then broken into regions. You have Amazon regions, and then within that region you have availability zones. So those availability zones normally refer to a single physical data centre. So in North Virginia, they have five data centres which make up US East, and they're normally labelled A, B, C, D, E and F. What I have found out is, on my account, US East B would be different to someone else's US East B. So they seem to switch the letters around so we don't all get the same data centres if we go for B. So if you provision a node on the cloud, you say, I want three nodes. Amazon will pick a bit of hardware and stick those nodes on them. You don't know if, in this case, I've provisioned three nodes, and two of them have ended up on the same physical hardware. You've got no control generally with Amazon where those nodes are going. They will just pick a bit of hardware. So in this case, if server A disappears, you've suddenly lost 66% of your servers in one file-swip. The same with the data. Amazon store data in what they call EBS. Rackspace is a similar thing. Your data can end up on any disk and it can be spread around various disks. You don't know where it is. Amazon will claim they have two copies of your data all the time. I assume it's true. It's the same with the networking. We generally find networking in Amazon is very unreliable. You get an awful lot of dropouts. Servers can go be disconnected without you knowing about it and they'll come back milliseconds later, but we're doing high volume data transfers normally. That millisecond outage will disconnect our processes. So we've had to re-architect our software to work in Amazon specifically. I'm assuming it's going to be the same in all of the other clouds. You don't actually know what the networking is. They just provide you with a connection. It can be whatever they fancy. There's obviously a security consideration about moving data around cloud environments. You don't know where your data is going. When we used to do high availability, I used this phrase we used to do and it was only probably a year or so ago I was doing this on-premise and this is considered old hat nowadays. You would make sure you had two servers in different racks. So if you had a master and a slave you'd make sure the guys racked it in two different racks. All the machines used to have redundant power on them. So if one power supply failed, the other one would kick in. And they would normally have two nicks as well so you'd have redundant network. And you'd have redundant disks so it'd be raided or backed up onto a sand. And if you were going to deploy a backup server you'd have it in a separate location and you'd normally have two network connections to your backup data centre. When you get into the cloud, it's sort of very different. And we're finding cloud reliability certainly in Amazon is quite poor. Amazon has quite a lot of outages at the moment. I think we've had five or six in the last year and it's taken out companies like Netflix so you need to engineer your database layer to handle these failures. You're now going from... Failures used to be rare in your on-premise locations. I can't personally remember losing a server in probably ten years. It was a rare event. And now we're getting from our support desk we're getting people losing Amazon instances every day. So you need to think differently. I mean Netflix has had quite a few outages in Amazon recently. How do you rethink how you need to rethink how you're spreading your database servers? If you're only going to deploy two which we try and talk our customers out of nowadays you want to make sure they're in different availability zones. So if Amazon loses an availability zone you're still going to have one machine. What we try and get our customers to do now is at least have a backup in another Amazon region because we have seen the whole US East drop-off line and it's quite painful for them. What we prefer, this is how we run our own internal systems as well we now replicate out into rack space as well so we're not dependent on Amazon at all. So if Amazon goes completely we've still got our databases up and running. Basically we've seen enough problems with Amazon that we've now got a bit paranoid about one day Amazon may go down. It's going to be a fun day but hopefully it doesn't come soon. So you need to consider locations where you're going to deploy these servers to. You need to have more nodes than you would. In the past I would quite happily recommend a master and a slave for databases and I'd be fairly certain we would only ever lose one of those machines at once. I got away with it generally. In Amazon anyone deploying with two nodes gets a strong warning from us that it's probably not a good idea. Nodes in Amazon can just disappear. We've seen this recently, I had a customer this has actually come out of one of our support tickets. The master database just disappeared. The whole server just went. We never found it. Amazon never responded to their support tickets which is quite normal for Amazon. We recovered the EBS volumes eventually but the node never came back. That's fairly normal. Basically you need to assume you're going to lose some nodes and don't assume you will be able to reprovision nodes quickly either. When Amazon have an outage quite often their APIs get saturated by everyone trying to spin up new nodes and people like Netflix will have priority over us on those, getting those new nodes up and running so the big customers will have priority over us. I've been in a position where there's been an outage I can't spin up new nodes. I'm just in a queue waiting. Make sure you back up everything many times. S3 backup is cheap. It's nothing. The cost of backing up 10 times into S3 is irrelevant for most big businesses. You can also deploy and find you've got a bad node. Basically they come up and they run really slow. There's no reason for it. They can have bad performance. You could be on a machine where another customer has got a virtual machine which is doing something a bit weird and all of a sudden your node just gets really slow. You need to get into the mentality that our customers will go on to those nodes and start trying to debug what's wrong with them and we'll get a support ticket saying we've run some so tools. I'm getting bad performance. They've just wasted half a day giving us that information. You might as well just throw it away. It's pointless. If you've got a bad node, throw it away and get a new one. I think the phrase is it's pets versus cattle. In the old days you used to treat your servers like pets. You'd look after them, you'd care for them. With cloud environments, treat them like cattle.  You're wasting your time trying to fix a bad node in Amazon. By the time you've probably never worked out what's wrong with it, Amazon very rarely respond to support tickets. Normally because we're running master and several slaves, that slave will suddenly get really far behind. You'll get a huge lag on that slave. No, you can even log on and see it's slow. Just create one terabyte or one gigabyte file on one machine and another and it will be an awful lot slower. You're just wasting your time trying to fix it when you can deploy another node in an hour and copy the data across. In the cloud there's various ways of running databases. Amazon have their RDS service. It runs MySQL, Oracle and SQL Server. It's very popular. You can have read-only slaves in it. It spans multiple availability zones within one region. You can't replicate your data with RDS across to another region. It's simple to set up and use, but you're locked into RDS, so you're committed to using Amazon's tools. It's AWS only. You can now replicate the data out. They've changed it recently, but you can only replicate the data out to migrate to another platform. But you can't have your main database running in Amazon, RDS, replicating to something in Rackspace. There are some options for replicating data in. Our open source replicator I think is one of the few tools that will replicate from MySQL into RDS, which actually got one of our engineers in trouble because we're actually a competitor of RDS, and we provided a tool to replicate the data in. Because it's open source, we can't pull it in. So there's no multi-region support. Failover between, if one of the nodes goes, their failover can be up to 10 minutes. I've certainly seen it take 10 minutes to failover between nodes. But in some cases it's quite acceptable. It's not a problem for some people. Rackspace, they have a product which is MySQL only. As far as I can tell, it's single node. There's no replication built into it. The documentation is a bit better on what they provide. There doesn't actually appear to be any way of doing backups from it either. Google Cloud have a solution. As far as I know, it's Google only. There's no way of replicating in or out of it. HP Cloud are running Trove, I believe, which is part of OpenStack. But at the moment, Trove doesn't support any form of replication. It's single node only. And OpenStack itself has the Trove product, which is not in Havana, and it's probably going to be available in Icehouse. As far as I know, we're slightly involved with Trove, hopefully, to do the replication side of it. We'll get to Hong Kong next week to discuss it with them. This is how we deploy stuff in the cloud. We generally are customers split into various camps that we've got a lot of big customers that want it on-premise. We deal with people like the Financial Times, Marketo, and a few other customers I'm not allowed to talk about. And they've got it in a private data centre. They're quite happy with that. We've got a lot of customers that are in Amazon only, running, I think, I like, we've got biggest customers, about 100 clusters in Amazon. So quite large deployments in Amazon only. And they're used to working in Amazon, and they know they're going to lose nodes occasionally. Quite common, we're doing a lot of setting up backup and DR sites in Amazon. So if they lost their main data centre, they can fail over to Amazon. Or we've got people that are running Amazon and back up into rack space. Generally, they're looking for flexibility, and they want to put their data where it's most cost-effective for them. So they're looking... Generally, they use us because we can move their data into another cloud if they want to, or another on-premise location. We don't care where we work. Most of our on-premise clouds are VM where it's still hugely popular. Basically, they want to spread the risk of their data. If their data goes, most of these companies don't exist. If constant contact loses all its email addresses, constant contact doesn't exist. That's another one of our bigger customers. So they're very paranoid about their data. We deploy in the cloud, we automate everything. We don't rely on me remembering to do a certain set of steps on each machine. We use Puppet to work across clouds. So we started off going down the route and we had build images for each cloud environment with all our prerequisites built into it. But we found that was too difficult to maintain, so we pulled all that out into standard Puppet scripts. We now just use standard OS images. Generally, we just pull a CentOS 6 image from the cloud provider we're going to use and customize it with Puppet. We run in what we call masterless Puppet mode. We don't have a Puppet master because we find that would introduce a single point of failure. If you've lost your database server, your Puppet master may have gone as well. So before you can get your database server, you've got to re-provision your Puppet server first. So essentially, we just pull Puppet modules onto the local machine and run them on the local machine. We've got install nodes that will work across multiple nodes in parallel now. So we're deploying large clusters very quickly. And we've got a prototype GUI which we're using generally for sales demonstrations because most real CIS admins don't want to use a GUI. But it's very powerful for demonstrating how we deploy in the cloud. Underneath there, there's an API that we actually use from the command line for deploying clusters. Generally we've found most cloud providers don't provide a secure way of communicating between their sites. So if you've got something running in Amazon East, something running in Amazon West, all that traffic is going across the public internet. So you then need to provision your own secure way of communicating between the data centres. We used to deploy OpenVPN on each site, and then we would need to put in a second backup OpenVPN server in case the primary VPN server disappeared. So we were running multiple OpenVPN servers. And it got to the point where this was getting annoying, so we've actually now beaten up the developers and we've actually built in encryption in our own software. So we're encrypting everything. All our network traffic is encrypted within the software, which means we don't need to worry about setting up VPN tunnels all over the place. So that made my life an awful lot easier when they deployed it. So we've just encrypted everything. So I think it took the Java guys a couple of days to do it, and they found it was really easy, which was quite nice. As practises, we raid EBS volumes. EBS volumes are essentially in Amazon's version of a SAN. So you allocate a 10 gig EBS volume, and we found they can disappear as well. So we actually take three or four EBS volumes and raid them with software raid normally on the servers. You get about a 10% loss of throughput on them. We would rather the data is a bit more secure. We take backups of every machine every few hours quite often. We use extra backup, which is an open source MySQL backup tool, which we backup into S3. We also use EBS snapshotting on all of our raid volumes. So we've got snapshot copies of everything as well. And we monitor everything. If a customer hasn't got any form of monitoring switched on, we don't let them go into production. So we use Nagios, Sabix, Email Alerts, Uralic. Just about every form of monitoring we support, and we would recommend having two forms of monitoring wherever possible as well. I've generally found Amazon's own monitoring is not particularly reliable. So we try and use a third-party monitoring tool. The future, where we're coming from, we're finding we're dealing with more and more clouds regularly. This is not a great slide. It's not easy to view. And each cloud has its own API. So we were repeating things over and over again. So we've built an API layer which sits in front of all the clouds that we deal with. So I now say, give me a node in Amazon, and the API will return me those nodes or give me some nodes in our open stack environment. And we get the same. I just get an array back with the details of those nodes. I don't care where they are generally. And it means we can now deploy. I deployed as an example for a customer the other day. It was 15 nodes across five data centres, three in Amazon, two in open stack. And it took us 32 minutes to deploy the nodes, configure them, we pop it and install our software. And probably 31 of those minutes was us tailing the logs watching it happen. So we're automating as much as possible. A demo, which will normally go wrong. My experience with live demos is not great. It's gone. So what I have here is a node I've just deployed. It's in one of our open stack environments. It's got nothing at all running on it. It's just a clean sentos installation. So there's no, I don't think there's any Java on it. There's no MySQL. All I've done is I've installed my, we've got some puppet modules which we use to deploy nodes. And the only thing I've got deployed on here is those modules. So all we do is we set up a puppet command to install the node. So we're just going to call our, our puppet module is called Continuant Install. It's possibly not the most imaginative name for it, but it worked on GitHub for us.  We say, I want this to be called East DV1. The IP address will come from puppet itself. That means take the IP address of the machine and use it. In this cluster, I'm also going to install another node called East DV2. So I give it the information to go in the host files. And then I just say this cluster is going to be East DV1 to install some SSH keys. Download MySQL Connector J for me. Install the cluster. And it's using a test repo. So I have to give it the IP address of that repo because it's not in DNS. So what I do is tell puppet to apply those, apply that, no, puppet module. First of all, it throws up some warnings because I actually haven't given it a password to use. So it's using the default one. And then it will go through. It's created a group called MySQL. It's created the Tungsten Unix user. It started creating directories. It's downloaded the MySQL J command file for me. It's installed NTP, and it's installed the NTP config file. It's installed WGAT. It's installed Java now. It's creating the profile files for Tungsten user, configuring sudo for me. It's installed that repository I asked for. It's configured the Tungsten. It's configured the host file, set the host name. And when I set that host name, it's actually triggered a refresh of MySQL because it knows if I change the host name on a file, I need to restart MySQL because MySQL doesn't like it when you change the host name and don't restart it. Then it is probably installing our software now, which takes about 30 seconds, generally, on these machines. Actually, no, sorry, it started MySQL. It's configured all the MySQL users for me. Puppet will run in whatever order it likes, generally. So every time I do this demo, it runs in a different order. You set dependencies within Puppet to force some things to run in the same order. But if you don't set those dependencies, it will just run them generally in whatever order it fence is. It should just normally be one run of Puppet. That's what we try and get it to do. And that's finished. So it's running. It's got our software running. See, the host name has changed now as well. So it's configured that for us. And our software is up and running on the machine. And that is something... Before we used Puppet, that would have taken me on a good day. It used to take me about an hour to configure each machine. And that took, I think it was about... It normally takes about two minutes with Puppet. So... And what we can do with this is, while one node is configuring, all the other nodes are configuring as well. We're doing this all in parallel. If you lose a node in Amazon, I normally can get one up and running in about five minutes. It depends on the size of the dataset that I need to copy across. If I need to snapshot quite a large EBS volume, that can take longer. Where are we next with this? We want to do instance autoscaling. That for us is going to be our next big thing. So as we see more and more load on the database, we're going to provision more slaves automatically for you. Our software gives automatic read-write splitting. So it will detect read-only queries and offload them onto the slaves automatically. And what I want to be in the position is, if I see a lot more read-only queries coming in, I want to spin up new nodes automatically to handle that load for us. And as that load comes off, we're going to destroy those nodes. We already support replication to MongoDB, but we have to configure it by hand. So that's something we're going to build into this. We do the same with Oracle. We can replicate MySQL to Oracle, Oracle to MySQL. We also do quite a lot of Oracle to Oracle replication now. And at the moment, we're configuring those by hand. So that's all going to be puppetised as well. And we do sometimes Postgres. Yeah, we used to do an awful lot with Postgres and we had problems replicating from it. A lot of our customers moved away from it, so we stopped supporting it. But it's something we're going to get back into probably when we find a customer that needs it will sort of brush off the code and start working with Postgres again. I'm doing an awful lot of deployments at the moment on VMware and private cloud, so I want to expand this to work properly with VMware. So some very painfully learnt lessons, which we've learnt over the last year in the cloud. EC2 instances just fail. Get used to it. One of anything is never enough. So I have two servers. I had a customer complain in the other day that I wanted to install two servers. Then I pointed out to him that with reserved instances it was going to cost him $20 a month extra. He'd probably put it on his credit card and expense it somewhere. Don't assume you'll have resources available when you want them. I've actually got, for a lot of our customers, I've got instances already sitting, waiting, running, if it's business critical to them. And we'll just fail over to them when we need them. Think more than one cloud provider wherever possible. Don't put all your eggs in Amazon's basket. One day Amazon's going to have a big outage or Rackspace will have a big outage, or HP Cloud. You need to assume it may happen. Resources are disposable. Just throw them away. Key thing for us was monitoring. You need to make sure we monitor everything now. Automation. We spent probably the last year deploying clouds and then manually configuring servers and it started to get very time consuming, which is why all the puppet stuff has come around. Back up everything. Any questions? No. Enjoy probably what's left of the day. I think there's a party tonight. This is the one event I actually like because I actually live only an hour away from here. So it makes a change. That's our contact details if anyone's interested. And enjoy the rest of the conference. We normally monitor centrally. Yeah, generally if we lose contact with them, we'll assume they've gone and promote something else. We generally find in the web stuff, in the cloud environment we don't try and fix things as much as we used to. I think that's the right way and fail over somewhere else. That's probably one of the biggest lessons we've learnt. Don't spend an afternoon trying to fix something.


After hours of investigation, the Bemidji Police Department has determined that an eyewitness report of an abduction was in fact unfounded. The alleged abduction happened Wednesday night near the area of 26th Street, Northeast and Callahan Avenue. The eyewitness told authorities that they saw a black four-door jeep approach of female and that a rear-seat passenger grabbed the female and pulled her inside the vehicle. Bemidji police located the vehicle and the young woman described in the situation and found out that no abduction took place. We don't know if this was a prank. Authorities say it is best to let them know whenever something like, when you see something like this. There are no consequences that someone could face for something like that. It's not illegal to play a prank on somebody. It's just very concerning and it causes alarm in the public and we want to make sure that we ensure that everybody's safe and you remind the public this is a safe neighborhood, that this is a safe town. The Bemidji Police Department says they're thankful to the juvenile who reported what they saw. Authorities also say there is no danger to the public.


I'm in the contour booth with Andrew Morgan and he was using something really strange looking with his keyboard and I couldn't figure out what it was, so we decided to ask him about it. How are you doing Andrew? I'm good, yeah. So this is the Roller Mouse Red Plus and it's an ergonomic solution to the average mousing and it provides a much more comfortable feel to mousing, removing that whole clawed hand that you get and reducing the pain in your wrists or in your shoulders by just giving you a very nice squared up position against your keyboard. So this is audio as well as video so for the people who can't see what we're looking at describe what you're showing to us because this is not a mouse, this is not a trackpad, this is not a roller ball, what is this? So it is a mouse but it's a roller bar so the idea is that it has a large wrist with a small button section as well as a roller bar with a tube on it. It's a cylinder, the length of the keyboard with a roller thing on it. Yes and actually with our design there's a sensor inside the tube which reads the movement of the bar as it goes back and forth and rolls forward and backward which allows for that nice smooth rolling feel. It really looks fun to use. It is and it does take a short time to get used to it for the average person who's used to using a normal mouse up and down and all over but once people get used to it and have tried it for about a week it really does improve their quality of mousing incredibly. It's amazing how quickly some of that pain goes away, I mean if you've done permanent nerve damage no but a lot of us get to the point where we find another solution early as I did and all of a sudden you're not in pain anymore so that's a great thing. Yes absolutely. So you mentioned that there's some control keys not quite on center in this case it looks like it's slightly off center so what is that? Yes so with our roller mouse we put the button section actually in line to be more directly underneath your main typing section normally we like to keep it aligned with the B key on a typical keyboard. Okay what he's got here is an extended keyboard so that's why it's off to one Right exactly but yeah so along with its position we have these multiple keys and within our contour driver all of these keys can be customized along with having their set functions so out of the box it'll give you your left click your right click a double click and a copy and paste up top plus a scroll wheel and an additional button which helps you change the sensitivity of your roller bar. Okay and then within the contour driver you can set these keys to be any additional functions you like so I know personally I like to have an undo and a redo up top as well. Make a lot of mistakes do you? Yes all the time. I never do. This is pretty cool so this is the product Deanna is called the roller mouse red plus and how much does that cost? I believe it's actually what is it? Tyler we'll take a short intermission while he finds out how much the the roller red. The roller mouse red plus is going for 265 right now. All right and now this has a pretty substantial wrist rest area you've got another one that we're there's other people looking at right now as a smaller wrist rest what is that one called? So that is the roller mouse red and it's essentially it's the same product just with it's got the standard wrist rest this one is the next one up which gives you the extended wrist rest. Okay and how much is that product? Same cost so yeah so you can actually you can purchase you could purchase that one and then as well you could purchase an extended wrist rest separately if you wanted to. Oh I see I see it works okay yeah. All right and how would people find out more about these products? You can find out more about our products at ContourDesign.com. All right that sounds really good thanks a lot Andrew. Great thank you very much.


Welcome back fellow techies to our latest tutorial video. I am The Technician Project. The next video we're going to talk about is how to record using an app on your iPhone called Voice Memo. Voice Memo can be downloaded from the App Store on your iPhone or Apple device. This works on iPad and Macs as they have built-in microphones. This will not work on a Mac mini as it does not have a built-in microphone unless you have a webcam built-in. So how to record on Voice Memo? You want to tap the record icon once and tap it again to stop. And when you tap the record icon your memo is saved automatically to your current location as the title. You can change that by editing the Voice Memo. By editing the Voice Memo you can click edit or then click the three little dots on your audio recording which is on the left hand side of your audio. And you can edit your form by pausing and replacing audio within it. You can trim audio within it and you can also delete parts of the memo at the same time.  To share your Voice Memo you need to tap those dots and click share. You need to share the files with your email. 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.


Hello, my name is Adelito Square. I work at the School of Financial Management of SOAS University of London, where I'm convener of the MSc programs in Public Policy Management, Public Financial Management, and I'm also convener of the summer school in Public Financial Management. The summer school course on Public Financial Management has been designed with the idea to bring in a concise way some of the most interesting topics in our master's courses. So we have issues of where does the government take the money from for finding the operations, the decisions which are made for finding public policies and programs, then how can the government be held accountable, how do they report to the public, and what's the role of auditors in ensuring that public money is properly spent. So we compress all these topics within a three-week course and we aim to provide the participants some insights into this important function for the working of the government. This program on Public Financial Management is different from other similar courses that you can see around. But first it's a course about public policies, how does the government make choices about funding programs and spending public money. But it's not really a course about accounting or public finance. The key concern for us is the decisions which are made from the side of public authorities. So it's more a course about political science, if you like, or generally policy sciences. In addition to these, we do not have any particular regional focus. So we may look at countries from the developed world, from Western countries, Europe and North America, but we also place attention to emergent and developing countries, with the idea that some countries can learn from others' experiences, with the idea also that the local institutions and culture and history and traditions are also quite important in seeing how the government makes use of financial resources. So the course is about lectures, but it is also pretty much about classes or tutorials. So students will have the opportunity to interact in small groups with their teachers and with other coursemates and to discuss specific case studies. We also typically, every year, bring about some new topics which are around. So, for instance, what we plan to do this year is to have a look at the rise of cryptocurrencies and some attention from the side of some central banks to use central bank controlled and issued cryptocurrency and especially what does this mean in terms of public finances. So, I hope to welcome any of you to come and study here at SOAS and London more generally. London, as you know, is an international capital of the world and so here you can have the opportunity to interact with the people coming from all over the places. This can be the case especially of SOAS University of London because we have a huge variety of students coming from different regions in the world with different backgrounds and so typically there is plenty of opportunity to learn from each other's experience.


Hey everyone, how's it going? Not normally I'd be all dressed up as Snazzy, but you know what, it is getting nice out. It's like 78 degrees out here. Screw it.  In all seriousness, folks, why don't you hit that subscribe button, comment down below. Giveaway going on for $100 cash money, making it rain up in here at Nintendo Prime. To enter it down in the description or the pinned comment, a bunch of different ways to enter. Most of it just involves subscribing to the channel, commenting, also pushing our podcast episodes, all that jazz. Hopefully you guys enjoy that. Now here's the deal. We have some big news for you today because of Oatmeal Dome. Now it's not really Oatmeal Dome, Switch Brew and others have discovered this. It's really because of Nintendo. We've talked a little bit about this Switch 12.0 update because it looks like on the surface Nintendo didn't do much. It was like minor maintenance. It was just, hey, here's like, we're patching a few things with your saves on the cloud server, like, yay, here's a 12.0 update, like jumping a full version ahead of the last update. Really strange. Usually that would be like a minor update. That would be one of those, hey, we have stabilized your Nintendo Switch system. It turns out this update actually contained a lot more. We already talked about the fact that it actually contains information on a new dock or a new update for a dock that currently doesn't exist for a system codenamed Alula, which we have seen references to in the past. It seems to be an unreleased Nintendo Switch piece of hardware, potentially Switch Pro. We'll have to wait and see for sure because we're not sure that Alula is that per se. We just know it's a reference to a hardware that currently doesn't exist. So, yes, there's a new dock coming using the same codename as the other stuff that has the same codename for the new Switch. So it does appear if we get a Switch Pro, it'll have a new dock. I don't think that's surprising with all the 4K DLSS rumors out there. But we're not talking about that in this video. We're actually talking about another thing Nintendo slipped into this update that would be a really, really big deal, although it's not being used yet. And this could be for this Switch up here. It could also be for a Switch Pro. It could also be for new accessories coming. And that potentially is Bluetooth audio. Now, the Switch has had a Bluetooth audio chip, or really just a Bluetooth chip in general inside of the system from day one. That's how their controllers connect. They're not using some proprietary connection like Xbox Series Xs. They're using just straight up Bluetooth.  And the thing is that Bluetooth has always had the ability, if Nintendo would enable it, to allow Bluetooth audio. What you're seeing up here is one of the many solutions people have already been doing for Bluetooth audio. And that is using a dongle. It's kind of cumbersome. It takes up the USB-C port on your Switch. So you can't just plug it cleanly into a dock. There are workarounds and dongles that go through the headphone jack to give you that Bluetooth experience. But none of it's as seamless or as interconnected or with the lowest possible latency that could occur if you would just enable it through the platform. Now, there is no headphone jack on a Pro controller. There's no headphone jack on the Joy-Cons themselves. So even having Bluetooth audio run through a controller and then being able to plug headphones in would be at least a compromise. If you're not going to allow full wireless Bluetooth headphones, at least allow Bluetooth connectivity through the controllers to use any headphones you want there and not have to run a cord all the way up to your Switch if you're in dock mode. Or obviously, we know the dongle mess, the hot dongle mess it is, to do voice chat through a phone plus have the audio come from your Switch and have it all be in one headset. It's really not a clean, elegant solution. It's one of the least elegant things from Switch, from a platform that I got to limit even today with that massive bezel still looks pretty elegant. Now, my thing is, what could this all mean? One, yes, they have added the capabilities for Bluetooth audio in this update, but this not being used. You can't use Bluetooth audio with the Switch right now. So there's a couple ideas floating up there. One, they're going to enable Bluetooth audio, just full board and let you use wireless headphones and wireless headsets for the games that let you do local voice chat. Fortnite, I always bring this up, is a prime example of a third-party game that does not use Nintendo Switch's phone app and uses their own in-game voice chat. You could literally in-game voice chat on Fortnite, on Switch, right? Now, you just have to be plugged into the Switch. That's not too bad when you're in portable, of course. A bit of a hassle when you're in, obviously in a doctoral situation, but it is what it is. At least it's an option. Now, my big thing with all of this is that I think this means there is new stuff coming. I think this is more applicable to a new Switch. Now, this does not definitively have anything to do with Switch Pro, but I do think it has something to do with it because I do think that they're going to enable you to use headphones at least through a Joy-Cons or a Pro Controller in the future. Basically, what I'm saying is I think they're going to actually put a headphone jack on a future Pro Controller or Pro Controller Plus, whatever they might call it, that's just a guess right here, or on new Joy-Cons Plus or something like that, where there's going to be new Joy-Cons that come with the Switch Pro that they're gonna take the headphone jack off of the main Switch unit. Well, maybe they'll leave it on the Switch unit. They could have it on both, by the way. You don't have to definitively remove the headphone jack off of the Switch, but I think they're gonna put a headphone jack on the bottom of one of the Joy-Con, and yeah, you're gonna be able to then plug headphones into that, and for plugging headphones into your Joy-Con or into your controller to work over Bluetooth, they have to be able to accept a Bluetooth audio signal, so adding Bluetooth audio support would be required in the operating system and at a hardware level, of course, in order for you to even use wired headphones over Bluetooth with a controller. So, yes, it could just be as simple as that. They might not be letting you go full Bluetooth standard headphones on their own, not plugged into a controller, because there are audio latency issues. It's been a constant issue with Bluetooth over time. Yes, there are better Bluetooth signals than others, higher quality products than others that create less latency. I can just use my car as an example. Bluetooth audio in my car, which is a 2013 Dodge Durango Citadel, it has Bluetooth audio. You can Bluetooth hook your phone up to it and watch videos or play music, but there is an audio delay, and the audio delay is significant. It's like one and a half to two seconds, and if you're watching a video, things are out of sync, it's just not good. Now, I'm not saying you should watch videos in your car, but I'm just wondering, there is an audio sync issue, and that's over Bluetooth. Now that's seven, eight-year-old Bluetooth, and my parents' 2016 Vovo, their Bluetooth audio, it's only about a 0.2 millisecond delay. So it's barely noticeable. You really gotta be a big audio file to notice that there is a delay. And that is what I think we really wanna see here with Bluetooth audio on Switch. If they're gonna allow full wireless headphones, then yeah, we want it to be the high quality Bluetooth. Now that's gonna depend obviously on the Bluetooth chip in the system, and also depend on the quality of the signal. You'll gather the antenna and all that on your Bluetooth headphones. If you're basically buying $10 wireless headphones, you can't really expect to suddenly not have good latency, but for those that do invest in the best they can get for Bluetooth headphones, which by the way, there is a limit on the sound quality from Bluetooth headphones. So that is something to keep in mind. But yeah, I think it's more apt that Nintendo's looking to potentially support a 3.5 millimeter jack on a future pro controller or on future Joy-Cons for a brand new Switch. Now those Joy-Cons might be cross compatible with the current Switch, and therefore this might not just be an update for Switch Pro, but also be an update for the current Switch. So this is actually an exciting update for all Switch owners because of the potential. Now again, we don't actually know what's going to happen, but I'm excited. I'm excited by this entire prospect that finally a basic feature that's pretty much available in one way or another on every other platform in existence, including that phone in your pocket is now finally gonna be available on Switch. At some point, Nintendo would not add this support if they weren't planning to do something with it. That's the big thing. It's one thing, you know, when you see patents and other things thrown out there, those products don't always come to exist, but this isn't a patent. This is just an update in the firmware for an ability that the hardware, one way or another, will be able to support. So third parties have been asking for this for a while. Gamers have been asking for this for a while. So stay tuned. I think this is some really, really exciting stuff, and I'm just glad to be part of it. That being said, thank you so much for tuning in. I am Nathan and RoboJance from the Nintendo Prime. Be sure to enter our giveaway. It's just cool to give back to the community. Use that $100 cash or anything. You gotta pay bills. You need some diapers for your baby. You need to, you know, get some groceries. Whatever you need to do, I wish I could give away more, to be completely honest. I wish I had thousands and thousands to hand to you guys to help out as many people as I can, but I'm just not in that kind of financial position, but I am in a position to give you a hundred bucks or give at least one person a hundred bucks. So that's our giveaway for this month. Heck, use it to buy games. Whatever suits your fancy, I'm here to judge. All right, folks, I'll catch you guys in the next video. I'll catch you guys in the next video. I'll catch you guys in the next video. Bye.


Live from San Francisco, it's theCUBE, covering Samsung Developer Conference 2017. Brought to you by Samsung. Okay, welcome back everyone. We are here live with theCUBE coverage. We're cloud native and smart things conference from Samsung Developer Conference. I'm John Furrier, the founder, co-founder of SiliconANGLE Media, co-host of theCUBE here with Reg Stodgrass with the chairman of Read-Write and Read-Write Labs. Also been an entrepreneur, he's done the wearable world events, done a lot of things in tech. Riding the waves, you've seen them, a lot of action going on, Reg. You want to get your thoughts as we wrap up day one of two days of wall-to-wall coverage of theCUBE's Samsung Developer Conference, a lot going on. You know, Samsung, they're trying to play their best hand if possible. Obviously, they're not going to come out and say, we're not really ready for prime time for the cloud, but the reality is they're not ready for prime time for the cloud and IoT. However, huge strides in positioning, messaging, and the self-awareness of their stovepipes. They are a series of stovepipes that they've recognized, we got to make this a 2.0 Bixie that crosses across all the Samsung, open up IoT, which I thought was great. Open ecosystem. Everything else to me is a work in progress, kind of hide the ball a little bit. I mean, what's your thoughts? Do you agree or what's your reaction? Oh man, well, I was on a panel earlier today and somebody was like, oh, this is great. And I wanted to go back to back when we did the open API service with Alcatel Lucent, when we roll out all this stuff for the telcos. I mean, it's just, it's a lot of hype initially, but what I do like about it is it seems like there's a dogged commitment to creating all the different like documentation that's necessary and bringing that in. I mean, if they really put the full marketing weight behind it, this could get really interesting really fast. I mean, they own almost every device in your home already. Well, I said the word hide the ball. Maybe I should take a step back and not be too harsh. What I mean by that is they're not hiding the ball on purpose. I think they're by design. I think Greg mentioned this real Greg Narrison who said, they're doing it by design. And I think that's a good call. Smarter things is a good positioning. It highlights multiple devices and connecting it together. I think if they played the data card in the cloud too much, they would have overplayed their hand and it's not needed. I mean, do you think it's needed? I mean, I don't think it's needed. One of the biggest problems with IoT right now is that you have multiple different silos creating data. And then all those data silos have to figure out how to come together and talk about it. I mean, it seems like they're taking a step out saying, hey, we want to build that solution, which is great. I'm more interested in the orchestration between different OSs. Like how are they really going to do that? Because it's, we talked a lot about when you build one of these ecosystems, you're really just building an economy. And the more open that you let your economy, right, the more business models come in, the more people that can be there. And so, if we were to start thinking about these OSs as real economies, like what do you need to have an economy work? Well, I think this is why we were talking earlier. I think you had a good point. I think that validates what I'm thinking out loud here, which is why play the data card? They don't need to because it's still open book. They still got to figure it out. And that's not a bad thing. They play with their best hand, which is the consumer hand. It's consumerism. The devices are awesome. The screen on the phones are phenomenal. They got TVs, they got, they got a little bit of a family hub going on with the living room kitchen thing with the refrigerators. That's IOT. They got healthcare because it's a device issue. So they work in their way from the consumer edge into the industrial edge. Now, if you're in the IT world, you have security problems. So most people that we talk to at theCUBE and say, hey, John, my plate is full. I got to staff up my DevOps and my application developers. I got to unbolt security from my IT department, make that report to the boys of profit center now. And I got all this machine learning and ops, cloud ops. And you want me to do what? Like instrument my entire factory with this IOT thing. So people are holding the brakes. Well, I mean, think about it every day, right? You're confronted with another executive that has like fallen on a sword of a major security hack, major security issue.  And it used to, you used to come and say, okay, we're going to make decisions every eight, nine months.  And you know that from your vendors, everything was predictable. And now it's like, oh man, I got to get into this Google Glass stuff. And I've got, no, now it's wearables. And wearables, that doesn't work. I need my IOT infrastructure stuff. And so we're moving the court, you know, away from all these CIO CTOs consistently of what they need to think about next. It's interesting, if you look at the stack, go back to the old 80s OSI model, you had the lower level stack, middleware and then application stacks. If you follow the data and the networks and the packets, how it moves, you almost see the trends, batch versus real time. And I think what we've seen in the big data world and data sciences, which can be analytics, obviously specialty industry, but the role of data in real time in self-driving cars really highlights this really huge wave coming, which is how that people dealt with data and software, the relationship between software and data was different. Store it in a database, build the database, call the database, get the data out, load it in, slow, monolithic, siloed. But now you have data that you need in really low latency at any given time in any different app from any different database in less than a millisecond. How do you do that? Well, think about it. It takes intelligence. About two years ago, I had a great conversation with a big packet moving company that managed most of the packet movement from most of the internet, and we were talking about, what does it look like per person in the US in the next three, four years? And it could be up to a pet-a-pie-to-data per person. Now that sounds awesome, because if you look at all the different videos we watch, it's like, oh, that's great, really cool flying car, connected windows, no one's really doing the math on that. And if it's a pet-a-pie-to-data per person, flying in the US, a year even, or I could see models where it could be a month, think about what that does to the network load. We just don't have the math to be able, possibly they handle that. This is why the decentralization with blockchain is interesting. Even though blockchain is hyped up, I think it's fundamental to the internet, as does Dr. Wong from Alibaba who told me that last week, he said it was like TCP IP, I agree with him, because you have distributed computing, which we know about. We've been there, done that, but now you've got decentralized and distributed two different concepts at the same time. That's a fundamental paradigm shift. It's insane. Well, I mean, it's just, so, I mean. It's intoxicating to think about what that disrupts. No, no, I love it. I mean, honestly, I've fallen in love with NeuroBand Networks last week for some reason I'm the weirdest person on the planet, because it's such a solution for security. It's such a solution for a lot of this, you know, backhauling of data that we're going to have. It'll be interesting, okay? But when you think about the pure math on- You backhauling data, you backhauling compute. Oh, well, so. That's a different conversation. The trend is don't move the data, throw the compute at it, because compute is, it just, well. This is an architectural renaissance happening. People are reimagining. How many start-ups can even draw architecture, right? With all the lean startups, I mean, when was the last time you saw, like, somebody pitch, when they came to pitch, it's like, let me talk about my architecture. That should be the first slide. It should be the slide that you talk about as an executive in everything. I don't see startups deliver architecture. If you can't get on the whiteboard and lay out an architecture on fundamentally the core engine of your technology, you shouldn't get funded. So, that is a major issue that's happening right now, because I do think that we have this group think where we've disallowed a lot of R&D thinking. Like, we don't do long-term R&D before we get a product to market. And now, like all these- Sometimes you can't. Well. Sometimes you have to sprint out and put a stake in the ground and iterate. Think about all the connected device products. How do you test the connected device product to scale? Right?  They're getting this data. It's coming in. They can actually iterate on that product and make decisions. Well, that brings up a good point. We saw this at the Cube at VMworld. The first time we heard people grumbling in the hallways, like, you know, I love the ENC drives, but they just haven't tested this use case. And the use case was a new workload that had unique characteristics. In this case, they needed low latency. It was an edge device. Some edge devices have no latency as well. It's just trickling data in. But in this case, they had set up their virtual SAN in a tiered basis, and they needed a certain hardware configuration with VSAN. And they've never tested the hardware stack with the software stack. So it's just one of those things that the hardware vendor just never imagined. You can't QA the unknown. So this is where I see Samsung doing things like in chip and seeing what Intel's doing with some of their FPGA stuff. You can see that these infrastructure guys got to bring that DevOps concept to the consumer world. Oh, it's going to be so hard. Which is programming the hardware at will. Yeah, well. Like the cloud DevOps ethos. Do you, what do you think of that? Yeah, no, no. Like, look, I mean, I'm such a big fan of being able to get your product in people's hands to be able to see the use cases, develop them out and push that forward. You know, big corporations can do that.  So when you look at like the competitor, which is your device right now versus every other piece of IoT technology that isn't been perfect or anything, our biggest issue is we're driven by the success of the smartphone for every other piece of technology today. And that makes it hard to drive adoption for any other devices. So we got to get your thoughts on this because we wrap up day one. Obviously, let's talk about the developers that they're targeting, okay? The Samsung developers that they're targeting is the same kind of developers that Apple's targeting. Let's just call it out. However, you see voice activated touch. You're seeing the services tools. Now they're bringing in an IoT. You're not hearing Apple talk about IoT? Yeah. This is unique. You got Google on stage, wink, wink. Hey everybody, we're here. We're Google, Android. Coming together. What is in the mind of the developer in the Samsung ecosystem right now? What's your take on the psychology of that developer? I built an app at one point in time. It was dating Apple a long time ago, right? With some other guys. They built it. That was just the mouth. It's called Scout. And we were on the Symbian platform on the iPhone. We were on web. We were on mobile web. And the iPhone app store all with one engineer. And that was really hard because we had real time chat.  At the end of the day, what always matters is again, you're building economies. You're not building fun playgrounds or anything else like that. And if your economy is, your platform is the easiest to use. It has the capabilities and advantages that are the norm. You'll win. Bastiff Fusion is great. This guy out here, you want to know about prize, but Bastiff Fusion says in order for you to win in a market, you need two things. Imitation and innovation. Imitation, for instance, in TVs. Is your TV black and white? Is it color? As things move up, innovation eventually overtakes and always becomes innovation. So when you look at what's needed in market, the platform that is the easiest to use, the platform that has the most capable, imitative qualities. It's just very easy for you to push things to market, universally from OS to OS, along with certain pieces of innovation around business models, certain API capabilities that may make it easier for them to deliver revenues. If those are the things that are delivered that we see pushed out for a good blend of imitation and innovation, the win, it's that person that actually can deliver it. Well, we're seeing gaming and entertainment, really driving change. Netflix earnings just came out, they blew it away again. You're seeing the core cutters are clearly there. So much for Disney, right?  No one's really falling out of the chair for Prime. I mean, I don't know a lot of people who wake up and say turn on Prime. They shop on Prime, but not necessarily watching any entertainment. So a little critical of Amazon on that. But again, but Amazon's doing the right thing. Netflix, Amazon, YouTube, you're seeing a culture of digital entertainment shifting. E-commerce is shifting, and now you got web services. I think Amazon encapsulates in my mind a great strategy. Retail and services. But if you extend that out to the rest of the world, voice activated apps, you can blend in commerce, entertainment, you can replicate Amazon.  Amazon is so good at understanding where they fit in the stack. And then pushing the edge case further and further and further along, they're really brilliant. Versus VMware that's like, oh man, we can make apps. No problem, they went to make apps and that didn't work out so well. They're great with the VM. They're great with operators in the enterprise. Not so much with DevOps. No, no, no. I'm like a pivotal for that now. Michael Dell bought everyone up. Yeah, exactly. It's understanding where you fit in the stack and being able to take advantage of it strategically. I mean, like I said, I think Samsung's positioned really well.  There's a lot of really exciting things. Yeah, a lot of eye candy. No doubt about it. Oh yeah. I love their TVs, I love their screens. The new Samsung phone is spectacular. Yeah. I mean, it was the first phone that wanted me to get, transfer off my iPhone and I ended up getting the little junior Samsung there. Oh no, it'll be interesting as they start to connect their platform together as all of these other developers start pushing the pieces of their strategy together.  I mean, the question I have for you is let's just close out the segment. What do you think, what areas should Samsung really be doubling down on or peddling faster, I should say, which should be developing faster? Is it the open APIs? Is it the cloud? And they got to get the open ecosystem going in my opinion, that's my take. What do you think they should be working on the most right now? Yeah, I mean, like, look, I mean, cloud is going to be really, there's a lot of competitors out in cloud. There's a lot of multiple, there's a lot of choices, right? Where I've seen them like really do well, I'll go back to the fact that I firmly believe that Google never really monetized Android, that Samsung did that a lot better. And so by looking at the different points in the market where they're good, I mean, their ecosystem is solid. I mean, yes, I mean, it seems like the sexy thing is Apple, but I've talked to several developers and I know where they make their money and they do a strong amount of revenue. If not equivalent to where the iPhone is, at least from what I've heard so far. The Android market share is not shabby at all. Not, so. Damn good. So they've been able to do this from that, taking that Android stack, applying that imitation and innovation on top of it, fascinatingly so. I wouldn't count them out for this and I'm pretty encouraged to see all the other aspects but I like the ecosystem build out, too. Rex, not grass, read, write, read my labs. Quick plug for you, what's going on in your world? Is there some recent activities happening? Please share, update. So that's great. So we just launched our IoT revolution event series where we look at the atomic unit of different markets and what that means is we find the real buyers and sellers, a lot like what Debbie Land, who I love, did. We had the buyers and sellers together along with the top series, A Startups, all around newsworthy issues. And so, whatever it's like, is it hacking and Russia? We'll get cyber security experts up and we'll talk about those issues from an executive point of view and that's the thing that's making me most excited because I get to have all these conversations with people. It will be on video, on stage. November 13th is the first one. It's a private event but we'll work out on anybody. It'll be in San Francisco, around 100 Broadway. So it's kind of a quiet thing but I'd love for everybody to come if you're interested in everything. It's quiet, I think, but I want everyone to come. Yeah, yeah.  It's like my parties. It's like a yogi bearer. Well, thanks for coming on. I appreciate you wrapping up. Day one of coverage theCUBE. This is Samsung Developer Conference 2017. Hashtag SDC 2017, that's what they're calling it. A lot of great guests today. Go to youtube.com slash SiliconANGLE for all the great footage. And also check the Twitter sphere. A lot of photos.  Appreciate it and great to the team. That's day one wrap up. Thanks for watching.


You have a book out there to write. You have a song to create. You have a movie script to write. You have advice to give other people you may or may not know because of these past regrets and mistakes. So don't downplay them and don't beat yourself up about them because in those regrets and in those mistakes is magic. A mistake is never really a mistake unless you give it the power to be one, unless you let it weigh you down like it is one. So give yourself grace and know that you were doing the best that you could in that moment and then it's okay.  You're not gonna make the right decision every single time, but every decision is gonna get you one step closer. One step further. It's gonna be able to help one more person. So just think of it that way. Like you're always where you're supposed to be right now in this moment.


Okay. So this one's number one. This is just a dilution problem. If you're having problems with this, there's a couple more dilution problems on the website. So you can look at those videos as well. But this one's calculate the number of builds you would need to use to prepare a 5.0 liter of .2 molar NaOH from a 5.23 molar stock solution. So you need to know that you need to use the equation m1v1 equals m2v2 or mcvc equals mgvd. So this is concentration and diluted, concentrated and diluted, if you want to think of it that way. And then what I would do with these ones is just write down the variables. So the molarity of the concentrated is 5.23 molar. That's more concentrated. The volume of the concentrated is what we're looking for. The molarity of the dilute is 0.20 molar. And the volume of the dilute is 5.0 liters. So all you got to do in this one is isolate the vc variable. So you're just going to divide both sides by mc. Of course that will cancel that out. Given you this equation here, vc equals mgvd over mc. So md is 0.20 molar, vd divided by mc is 5.23 molar. Okay, notice molar and molar cancel out. And you're left with liters. So if we do this, we get 0.2 times 5 divided by liters, right? But it asks us at milliliters. Not to mention this is the right number of supers. So we're going to get milliliters out of this, 191 milliliters. Or since that's not the right number of supers, you could do 1.9 times 10 squared.


and no we're not reviewing my book but it it does play into this a little bit we'll get into that in a minute but for those of you who don't know I did write a book this is it it is a journaling workbook and it is a book that I hope helps you figure out if you want to have more creativity in your life and if you do how you can go about doing that at least indirectly the whole book is filled with narratives on one side and a workspace on the other side in which I usually ask you one or two questions and there's space for you to actually work on those questions on that page now this is the copy that you can buy for me in my Etsy shop it's signed you can also get my book on Amazon and you can literally just if you go to the Amazon search engine type my name Gina Bronzini Erin's it should come up if you also type creativity and self-expression that the book should still come up it's available on your Kindle it's all of also available in paperback I do recommend if you are gonna work in the book when you get your paperback copy take it over to your local art supply art supply office supply store like Staples or Office Depot have them chop the spine off and have them put a spiral binding on it because then you'll be able to open it flat and work on your pages nicely okay that being said once you've worked your way through my book and you figured out that yes you do indeed want creativity in your life and you want to make it part of your regular routine and your regular life and I hope that my book helps you get to that point and figure that out and hopefully helps get you down the road and figuring out how you can do that but once you read my book and you work through my book I found a book that you should follow it up with I love this book it is by Twila Tharp she is a dancer and a choreographer and it's called the creative habit learn it and use it for life it is a fabulous book it's so fabulous I was taking notes last night that's how you know it's a great book and I'm having issues of course with my asthma this morning so sorry right in I want to say the first was it the first page the first section definitely forget where I wrote it down from but it was here in the first part somewhere here it was on page 10 so you're not too far in the book and on page 10 she hits you right between the eyeballs and it says everything is raw material everything is relevant everything is usable everything feeds into my creativity isn't that a true enough statement if you're a true creative though every one of those statements should resonate with you oh my god they definitely did with me the whole book is filled with things like that a little farther in the book here's another quote from it it says she talks about periods with no distractions to creativity there's a whole section on distractions and I was reading the I was reading this section and I am let's see I don't know what section it was now because I just wrote that I just made notes I told you guys I already that anyway I wrote this down and I was just making notes because I read I've read a number of books I have anxiety disorder in case those of you don't know that I have anxiety disorder and I've read a number of books on eggs on anxiety disorder and also my therapist have they all recommend the same thing that you should try to it's helpful to your anxiety to just unplug just disassociate unplug turn the devices off turn the music off turn the TV off and just just yeah silence things silencing the physical noise around you helps silence the noise and anxiety in your head she talks about how that's true with creativity also to just silence the distractions some people work well with just distractions but a lot of us don't and just silencing them that's okay to do creating intentional periods where there's no distractions maybe if you can't even just taking a week and she talks about just going somewhere where there's you know no electronic devices and no music and no telephones and no nothing and just that sounds I like that idea it sounds good to me I don't well the no telephone I would like to just like put it away in case of emergency but not have ready access to it that would be handy but yeah as long as everybody's safe I like the idea a lot here's another one what is the one tool that feeds your creativity and is so essential that without it you feel make it an unprepared isn't that a great question I wasn't sure how to answer that she also has a creative auto auto blah blah blah creative autobiography questionnaire in here that's interesting to fill out and she also fills it out later on in the book and here and she shares with you her answers so that's an interesting thing to work through before you can think out of the box you have to start with a box isn't that the truth I'm always telling people who private message me you know how do I get better at drawing faces or doing this or doing that there's no shortcut you have to just practice and and she's right before you can think outside the box you have to work inside the box and you have to have a box so oh my gosh the whole book was like that for me I have a couple more here there's planning and over planning you never want the planning to inhibit the natural evolution of your work this is also something I've talked about many many times in regards to teaching I don't mind having a loose guide for say in my in the my year program this book review is for the my year 2017 program we'll talk about that in a minute we try to give loose guidelines to the teachers but I definitely don't want to be too specific because I really want to encourage them to go with their natural creative flow wherever that may lead them I tend to work best organically I don't mind having a rough direction and frequently I have a rough idea or a rough direction but I don't plan it out too much because if I plan it out too much then I just stifles my creativity she actually talks about that in this book I was I just the whole book I had bells going off in my head ding ding ding ding there's a whole chapter in the back page 136 I marked the page number now because there was just too much to make notes about page 136 how to be lucky be generous don't use that word lightly generosity is luck going in the opposite direction away from you if you're generous to someone if you do something to help him out you are in effect making him lucky this is important it's like inviting yourself into a community of good fortune she goes on like that for almost two whole pages if you do nothing else pick up this book borrow it from the library read that chapter oh my gosh I can't recommend this enough like I said earlier this book review is for the my year 2017 Facebook group and this is for the month of September I should have said that right at the beginning of the video but was so excited about the book if you're not part of that group and you want to see what other books review reviewed you can join the link is in the video in video description down below along with a link to a page that has all of my internet links on it social media links website links store links everything you can click on the one and get them all my happy mail address is down there and all that stuff so please go to the video description I look up this book by twilight tharp if you're on a limited budget go to your library I bet they have it if your library is like mine they probably have a website connected to all your local libraries and if they don't have it you're the one closest to your house they can get it from another library and then when it comes to your local one hold it for you mine does that all the time anyway I do recommend the book it's a fabulous book and I am definitely going to be adding it to my permanent library I can't even tell you and I'll probably be reading it again I did download it on my Kindle because I can guarantee you it's going to be one of those things that when I'm feeling down and out about the art and down and out about why I'm doing this as a creative hobby as a business what am I doing I made the wrong decision this is going to be a book that I'm going to go back to to refresh my creative soul and reaffirm why I'm doing what I'm doing it is a really good follow-up to the book I wrote these two books work very well together if you have this one you've liked this one you're going to love this one and if you have this one and love this one you should think about getting my book I mean you know help a starving artist out anyway I can't say enough good things about this book so I will be adding it to my book list in my journal this month that's it for today check out the video description like I mentioned don't forget to give this video a like please share and subscribe if you're not already a subscriber and that's it the most important thing is to go out and have a great day do something nice for yourself because you deserve it and I'll see you later bye guys


Hello everybody. My name is Mara Alida and I work with Thai Global. Thai is an international network of worker and union activists that operates in multiple countries including Brazil. Here in Brazil we work with two networks the Vida Viva Network which involves workers from different sectors and the Orange Juice Network. The Orange Juice Network organizes workers along the Orange Juice production chain. It has been existing for about five or six years. Here in Brazil we organize workers in the rural sector that is on orange plantations and in the industrial sector in the food processing industries. We also connect these workers with workers from the retail sector in Germany where we have a partnership with the Union Verdi. The work that we have been developing now for a few years already aims to promote effective change in the living health and working conditions of workers along the entire Orange Juice production chain. It is important to note that we are talking about a production chain that has a very high level of precariousness and especially in the rural sector on the orange plantations. Our activities in this sector aim especially to bring the workers closer to the unions so that they can together build actions and develop strategies to change their reality. To this end we have developed a capacity building process in which we collectively construct tools for workers and unionists to evaluate their own conditions and identify problems and develop demands and we promote international exchange on this. One of the tools that we work with are the workplace and health mappings. These mappings are a participatory research tool that allows workers to identify work-related problems that are affecting their health, to identify the causes of these problems and also to develop concrete demands based on their own experience and knowledge. In the rural sector here in Brazil it is very difficult to mobilize workers. Farms are often located in a distance of 300 to 500 kilometers from each other and hence workers are located far away from unions. For this reason we developed an app through which workers can send information about workplace problems directly to their union. This communication channel allows the union to get closer to workers, to be more present and to react more quickly when there are workplace problems and to find a solution. We also created a deductical game that touches up on various problem areas that workers face such as problems with agrotoxics or pesticides and precarious working conditions in general. In this way by playing the game and having fun, workers develop collective learnings and they discuss the problems that they are facing in the workplace mainly because of pesticides. We have also developed several tools in the network but the most important thing to highlight here is the participatory process that underpins all the tools that we use and develop. Our aim is to create collective spaces so that the workers themselves together with the unions can articulate demands based on their own experience and knowledge and use these demands to change their own reality for the better. This is a very important initiative. We are aiming to build a grassroots model where unions directly dialogue among themselves and that is not only in Brazil but internationally because we also try to build a south-north relationship in which workers in Brazil and Germany together evaluate their conditions and discuss proposals to change their own reality and conditions. I hope that I have given some insights into our work and that we will have the opportunity to answer any doubts or questions that you may have. Thank you very much for the invitation and I hope to be with you soon to be able to deepen this experience a little more.


Good afternoon, everybody. Thank you very much for this opportunity to address myself to all of you. Dear Deputy Secretary-General, bon tip. Good to see you again today. Distinguished Ambassadors, ASEAN member states, members of ASEAN secretariat, ASEAN sexual bodies, colleagues from the U-delegation, colleagues from Interpol, ladies and gentlemen. As new ambassador of the European Union for ASEAN, it is amazing to me, after arriving just five weeks ago, to see the level of cooperation that we are developing together between the ASEAN secretariat and the ASEAN member states and the European Union. I mean, this is border management and migration are extremely delicate, complex, sensitive issues. These are matters that can only be discussed among partners that share a level of trust necessary to start deeper conversations. I would like to think that with our first program a few years ago, we contribute, Ambassador, good afternoon, how are you? The European Union contributed today to the extent possible to develop that level of trust and partnership. Obviously, as European Union, we are confronted, we've been confronted for the last 40 years, on border management and migration. We have managed to develop a space of freedom of movement for goods, for capital, for people covering 500 million people, more or less, in a very wide geographic area. This has not been a very easy endeavor. It has taken several decades and right now, as we speak, it is a system that is itself under threat. It's a system that is confronting a very severe challenge to its integrity. That is also put into question the capacity of Europeans to actually raise up to the challenge and introduce the necessary technical and political modifications to continue enjoying from such a space of freedom of movement. It's with this very conscience and awareness about the difficulties that we are facing ourselves in Europe, that I talked to all of you to congratulate myself to see that you think that we still have a good expertise to share with all of you. I'm also very happy because being the second phase of a program, it means that during the first phase, there was a lot there that remained to be done together. If I understand well, we have one part of the program has to do more on operational aspects of border management. The other one has to do more with visas. Again, both of them are fields that are extremely relevant and interesting for ourselves in the European Union. I just trust that this seminar is as helpful as possible to all of you in ASEAN and to ourselves also in Europe. That's all I have to say. Thank you very much. Thank you very much for your excellency for the remarks. We would like to kindly invite his excellency, Siemela ...