I'm not going to take a quiz at the end, so don't worry. But let's get into it. I see quite a few faces over here that I haven't threatened to attend, so that's good news for me. There is a big section of the population that I went around and threatened and made them attend. So people who learned something in the last two days, I'm going to take pictures of whoever doesn't raise hands. There you go. OK, I hope that you will learn something more from my session, right? This is who I am. My name is Bajoia Tatiti. I work for Sony PlayStation. Another simple poll. Who knows about Sony PS4? There you go.  See? Love you guys. Love all of our customers. I have been working at Sony PlayStation for four years now, or so LinkedIn tells me. I live in San Francisco, not in the city, but in the suburbs of San Francisco with my family and my innumerable pets. And I have been passionate about UI automation for a long time. True story, I wanted to take out the number of years, and I forgot about it in the excitement of attending the conference. I did not want to date myself with the number of years I've been working, but let's just gloss over it, OK? So I am not going to get into the topic of manual versus automation, right? That is a topic that is a debate that is very near and dear to most of our hearts. Everybody, I think, in the QA community has a deep opinion about whether manual is a good versus automation is good. I am only going to talk about what worked in our company, in our environment. About four or four and a half years ago, we were trying to get into a software cadence from three months to bring it down to maybe once in every two weeks. We were trying to get to be able to repeat our promise to quality to our customers without fatigue. We really didn't have the resources to have the army that was needed to be able to go through the entirety of the manual regression. At that point, I think we had 10 applications running on the PS4. Each of them had thousands of test cases to grind through. And that's why it took us three months to be able to release one version of the software. And we really wanted to get into the habit of releasing faster, getting good quality code out faster to our customers. That was the value add that we wanted to bring in. And we had no way to do it with manual testing. We had to go the automation route. We realized that manual was not working for us. This is my favorite statement about automation. This is where my beliefs root in. When we started doing automation, in the beginning of when we started doing automation, we used to think it's auto magic. You write a script, you check it in, you start running it on Jenkins, boom. Everything happens. It should pass. Everything is good to go. What we realized through the journey, what we realized through the journey of maturity in UI automation is that it is not auto magic. It's simply automation. It's simply software code. Just like any other software code. This is also software code. And it needs the same kind of attention to quality and detail that any other software code would need. This is our, it's a little worked on the left hand corner is testability. So this is our personal experience with test automation stability. The tests are very stable if you have a very small suite. If you have five test cases, 10 test cases in your smoke suite and you're running them, they're very stable.  Very soon with our team of testers, we were grinding out, churning out thousands of test cases per application. And the stability of the test cases took a nosedive. It was pretty much unusable. Everything went into red. There was no predictability on what would pass, what would fail, but then we had a lot of automation. We had put in a lot of effort, created a huge suite. In reality, we were doing a lot of work, but it just wasn't giving us the return on investment. Now talking on return on investment, this is what our regression analysis showed us, right? The return on investment is that small green slice in the pizza, which is 3%. That is what regression was catching as the actual product defects. The rest of it, the big red part is where testers were going in and using wrong choice or bad choices for test development. I am guilty of using sleep sometimes in my code. I'm pretty sure most of us have done it at some point in our careers. There are many other things. We hard code stuff just to make it work. We put in incorrect weights. There are quite a few things. There is a range of test script issues that can happen. And that was the big chunk of what was happening in our regression suite. The other bigger chunks were environment issues and network issues. Things that we said we didn't have control on, right? We start running a test suite. It depends on a content or it depends on a product to show up on the page. It doesn't show up that somebody has gone in and changed that product or the content. The content of the page has changed. Somebody has kicked off a performance run and the network is completely clogged up. So our tests basically don't load anything. That is what was happening between the environment and the network issues. The result, of course, was ignoring the results, right?  Run a quick manual run through the bill and tell me whether it's good or not. Quickly just tell me, right? I got that request pretty much every time we were sending out a release. Every time I would come in and say, I have a regression run. Wait, give me three days to analyze the results. The release manager would tell me, forget about it. Just ask your team to run through it and tell me whether it's good or bad, right? That's what was happening. The entirety of the effort that we had put in to create automation was just down the tubes. It was just getting ignored. Nobody cared about it. We went in and analyzed what was wrong with automation. What, why wasn't it adding value to our software release cycle, right? And we realized that there were three primary problems with our regression suite. It needed a lot of effort for stabilization. The amount of effort that we were putting in writing the test code, we were putting the same amount, if not more, towards stabilizing the test code. We were also, it was obviously a high maintenance project. The number of people that we had writing test code was equal to the number of people who were trying to maintain the test code. And obviously, it took one day to run regression and three days to analyze results. So it wasn't really helping anyone. We worked out into why we were seeing such bad results. Why, what was going wrong and what the primary problems were. Remember that pizza that I showed you? And we realized that the three primary problems, the three biggest problems that we had was the badly written script, the environment issue and the network issue. And I'm going to keep on working on these, sorry. I got a popup and I knew that something wrong would go, something would go wrong during my presentation and it has. So let's talk about these three buckets. This is going to keep on coming up through my presentation. So it's a repetitive version that I have of these three buckets because these were my three biggest enemies during my automation journey. So what was the solution? We started a test run, we made small changes, we checked in the changes, it ran for some time, it started failing again, we pulled it out again, we made small changes again. I started looking like that or very close to that. That's where TSVS comes in. It's a little hard to get off your tongue, TSVS. I have colleagues who still say TVSS, TVS, something like that. It's a little hard. It's basically a service that tests the validation and the stability of your test suite. It's nothing more than a service that validates that your test suite is stable. And the two pillars that, and the primary things that TSVS relies on is the fact that it is self-contained. So whatever it needs to be able to successfully validate the testability, it has in its environment. It does not need to rely on something external. It increases automation reliability. I apologize for the bleeding out of the screen. It increases automation reliability. That's its primary problem. And it helped us achieve 100% automation. Now, again, 100% automation is, again, a very debate-worthy topic because as soon as I say 100% automation, there are quite a few people who say, what happens to those very corner cases that never get automated? Well, those are non-automatable test cases. Anything that can be automated should be automated and that's what I mean by 100% automation. Just reiterating what TSVS does, it is a service that integrates into your CI. It runs our TSVS service, runs as part of our Jenkins jobs. And I'll show you how it runs. It checks for the stability of the test suite and it continues to monitor the health of the test script. It just does not check it once, but it continues to monitor the health of the test script every time it runs, okay? And then if it finds that there is something wrong with it, it takes corrective actions. It takes automated corrective actions. These are the two pillars of TSVS. And I'm going to, my stand is that these are the two pillars that any software should be sending on, testing and maintenance. We would not dream of sending out dev code into production without testing. As a QA community, we wouldn't have a job if that were true. So why do we send out test code into production, which is regression runs without testing it? And why don't we factor in the maintenance that is required to maintain the test code? It's software, it's the same thing. It needs testing and it needs maintenance. So let's look at the testing part of it first, right? What happens during testing? This is where I need you to stay with me. This is what I meant when I said stay with me, right? There is a lot of information that I'm going to pack over here and this module of the service runs before the test gets merged in. So every time a PR comes in that has test code change in it, we write all our test code changes in Python. So every time a PR comes in that has got pi changes in it, this module will get kicked off in our CI. What it does is basically the first step is static code analysis. Most development code goes through static code analysis. So it's obvious that test code should go through static code analysis also, right? Static code analysis for those of you who are not very familiar with the term is basically analyzing the correctness of the code without executing it in a static format. And so we lint our code and make sure that there are no basic fundamental programming errors. That's the first step. The next step is runtime. And this basically checks whether your test case, the one that you've written, is granular enough or not. We don't want small test cases as small as unit tests. We also don't want test cases that run for like 15 minutes and go through eight different screens and 50 different assertions. It's bound to be unstable. So by checking that the runtime of the test case is at that sweet spot that is stable for your application, it tests that your test case is granular enough. It's not too small or too big. By default, in our environment, it is said to be too. The next one is failure rate. This is an obvious one. You don't want to check in test cases that are not passing even during testing. So before you check it in, run it a few times. By default, we run it five times, but run it as many times as you want to and check to see that it's not failing while you're testing it. Parallel runs executes the test case on multiple platforms. Remember those times when test cases failed because you only wrote it for Chrome? And then after you checked it in, it was supposed to run on IE, Firefox and Chrome. And the Chrome one passed, but then IE and Firefox failed. So this will make sure that that is not happening. That the tester has not inadvertently only written a test case for a particular platform. It will take the test case and run it across all platforms that the application supports and make sure that everything runs and passes. And then there is sequential run. So while you may have written a terrific test case that runs every time, that is perfectly granular, that runs every time and passes every time, runs on all platforms, you may have inadvertently done something that messes up the environment when your test case cleans up. During the tear down method of your test case, you could have deleted an account that other test cases rely on. So what this will do is insert your test case into a small set of other test cases and run that set to make sure that not only just your test case passes but everything else that runs after it passes also. It's basically making sure that the setup and the tear down of your test case has been correctly implemented. So all of these things need to pass. Every time a PR, every time a test PR is raised, all of these modules will run. Some of these modules can run in parallel and then everything needs to pass before the merge button is enabled. So if any of these modules fail, then the merge button is not enabled. You cannot check in if testing of your test has failed. It raises an error and the tester who's written the test case needs to go in and fix it. So we are done, right? What have we gained out of this exercise of testing our test case? We've obviously written well-written test cases. We've been forced to go out and make corrections to those small changes, small mistakes that we may have made in our test case. We've gained a well-written test case. It's granular. It's hit that sweet spot of granularity that your application needs. It has stability. We've run it multiple times. And the local environment, it passes on my local machine. I don't know why it doesn't pass on Jenkins. All of those things are taken care of. We've all gone through those motions of emotion. Written those, remember those three buckets. I'm gonna keep coming back to those three buckets because these are, these were my biggest enemies. It threw my automation journey. Those that badly written script environment issue and network issue, by the testing phase, we had taken care of the badly written script. Most of the normal errors of the badly written script were eradicated. We had done, right? We've written a good test case. It has passed. The testing phase we've merged is enabled, so we are happy. We get to go home. Again, I didn't look quite like that, but this is the best picture I could get of relief. This is how all of us felt when we could ultimately merge in our test cases. But this is reality. Even with all of that testing, the number of test cases that were passing in our regression suite increased dramatically. If there were, out of the 1,000, if there were 500 random failures earlier, the random failures had come down quite a bit, but it was still not generating the green bills for us. We were not being, we still couldn't get that 100% confidence. We were still wasting time in analyzing the regression results. The reality was that it still didn't do the entirety of the job for us. It had tested out test scripts, but it hadn't done everything that we needed it to do. Now comes the maintenance phase, right? We've tested our test case. We've merged it in, but we need to keep on maintaining that piece of software. We can't just let it go to the boons. We can't just let it go run wild and never look at it again. And we need to be able to automate the maintenance of that test suite as much as we can, because if we are burning human resources behind maintaining, then we might as well have gone back to that shampoo loop that we had of making small changes and merging in. So what does the maintenance phase of it do? It runs as part of the nightly regress, again, it's a CI integrated service. It integrates with the CI and runs as part of the regression, nightly regression runs, okay? It identifies fail, why a test case is failing. It identifies why it fails and then takes a decision of whether it needs to retry it or not. And then once it has analyzed the failure, analyzed why it failed, it will take a call of whether the test case is failing because it's a flaky test case or not, and then take corrective action towards a flaky test case, okay? So going into details of test maintenance, again, a lot packed into this slide, right? Sorry about that. First is the test execution. In our environment, at least what we realize is that since we had such a large suite, since we had 6,000 test cases running, if we let the entirety of the test suite run in one go, it took about 13 hours end-to-end test cases, 6,000 of them to run. If we let the entirety of it go, it would definitely, we would definitely start to see environment degradation at some point. So what we realize is that if we break up the test suite into smaller chunks, we call it chunking, very innovative. If we break up the test suite into smaller chunks and take corrective action in between those chunks, say reboot the machine, check to see that all the accounts that the test suite depends on are present, basically do a refresh of the environment, then there is a much better chance that the rest of the chunks will run and pass, okay? It also makes sure that if there is something that went wrong while a particular chunk was running, then only test cases in that chunk will fail. The chunk will eventually time out and then we refresh the environment in between chunks so the rest of the chunks will pass. It's not having a degradatory effect on the rest of the test suite. The next one is log analysis. This is important enough that I'm going to dedicate a separate slide for it. What we have done is basically create a library of all known errors, and obviously this library is a work in progress, right? We keep seeing new errors in our environment, errors that are coming back from a server, API that is unresponsive or not sending back the right results, something that's gone bad in the environment, some credit card that we are using in tests that has hit a rate limit, something like that. And we identify those errors and we keep adding it to the library and then during failure, we check the error logs to see if it is hitting a known error or not. If it is, then that test case is marked as an error as opposed to a failure. We know why it's erroring out and it's not really a failure. It's not a test case failure or an application failure. It's an error that is happening. The next is the retry. Once we've identified that a test case is erroring out, we've basically proven to ourselves that this is an environment issue and has more or less nothing to do with the application or the test case. So we will run it against mock services. We know that this can be, we can get over this hump by running it against a mock server, right? So anytime there is an error, the retry will automatically run it against a mock service. It will also update the test summary to say which one was an error, whether it ran and passed against a mock, et cetera. It will update all the test summaries and then it will retry the test scripts that are marked as not as an error, a failure. That could be an application failure or a test failure. It will retry those test cases but not against mock services. It also generates a heat map. So basically the heat map shows those areas of the application where test cases are more prone to be flaky or failing. So while we go through the retry logic, while we are retrying each test case, we are basically collecting all that information to see which part of the application has more propensity of test cases failing. We obviously need to put in some logic to see why that is happening. The heat map basically provides those heated areas in our application for us. When we've identified a flaky test case, a flaky test case is that where there is no way of predicting whether it's going to pass or fail. A failing test case, if it's an application defect and a regression that is introduced by development, will always fail. However, if it's not an environment issue, if it's not an error test case, it will fail sometimes and pass sometimes and that's a flaky test case. We can almost say that we don't know why it is failing. And so every time we identify a flaky test case, we will auto disable that test case and auto log a defect against it. So we will go write a bug against it in JIRA and put the same priority as the priority of the test case. So if a P1 test case got disabled, you'll get a critical defect against your application and it'll get assigned to the author of the test case. So the next day when the application team comes in and triages their defects, they have a critical waiting for them that needs attention. That also forces the application team to make sure that it is addressing each flaky test case. It's, you know, most of the time when we don't force this action, application teams know that there are flaky test cases and they keep on ignoring. So this is forcing the application team to take action. And then the last part is reporting. This is very important. You've gone through a lot of very complicated logic. In trying to maintain your test suite, you've done a lot, you've identified error versus failure versus flaky versus disabled test cases. There's a lot going on. You need to somehow summarize all of that information along with the heat map that you generated for your application, summarize all of that and put it in a dashboard for visualization which is easily consumable by the application team. Where the application team can come in, understand what is going on, take action where it can and then try to get an RCA of the things that are not easily understandable. My favorite three buckets again. The badly written script was already taken care of mostly when we were testing our test cases. The maintenance part of it takes care of the environment and the network issue. So my three buckets just got emptied. Summarizing the TSVS, the Testability Validation Service, it is an amalgamation of testing and maintaining your test code. Again, you would never not test or not maintain your development code. Test automation is just like any other software. It needs testing and it needs maintenance and you need to do the same thing with your automation code. And that's what TSVS does for us. Remember that pizza where the 3% was my ROI on all the automation that we had written. After we put in TSVS and after we'd gone through the motions of fine-tuning it, the pizza looked much better. The ROI looked much better, okay? Now, what did we realize? What are the things, what is the main value add that we got out of TSVS? Obviously the primary value add is stability. The number of automation runs that had now turned green was more than 85%. So we were actually seeing green bells. When there was a regression failure, it was taken seriously, it was all hands on deck. We would get developers get involved with what the regression failure was the night before. There was automation results that were not getting ignored, okay?  We were getting more done in less time. We had successfully downgraded our release window from three months to one week. We had actually outdone the ask. The ask was for two weeks and most of our applications were now going out in one week. That was simply because we had reliable automation that ran overnight when none of us were at work and then gave us reliable results the next day. There was very little manual intervention that was needed and obviously easier defect identification. We were not waiting till the last minute when most of your test cases and automation fail, you will and you ignore most of your automation results. You also tend to miss the regression defects, the critical regression defects that were introduced. So by making our automation stable, we had basically, I created a way where if there was any regression introduced, it was getting identified easier and faster and earlier in the cycle. It was definitely not leaking in into the customer environment. And we had maintainable code. We were not, I didn't look like that guy with purple eyes where I was just wasting my time maintaining code. Now, there are quite a few things that are still work in progress with the SVS. It's not done. There's always room for improvement. We are, remember that part where we were trying to check whether the test case that you're trying to merge in, where while it runs and passes, great. It is not messing up the environment by inserting it into a set of other test cases. That is a random choice. We basically go in and randomly choose five or 10 test cases out of our regression suite. What we want to do is intelligently choose that set, intelligently identify the test cases that will have the biggest impact by this test case getting merged in and then run this test case in that set, more intelligent picking up of the test cases that will run as part of that sequential execution. We also, when we identify a flaky test case, we disable the test case and log a JIRA. But then after that defect is resolved, that enabling that test case back is a manual process. The tester needs to come in and enable the test case back and merge it in. We want to do the reverse integration of that. Every time a defect is resolved, we want the test case to get enabled by default. We also want to eliminate chunking while it was good and it works. It also takes up a lot of time. When we are breaking up and refreshing environments between smaller chunks, it takes some time and increases the execution time of our run. So we want to eliminate that and we only want to refresh the environment when we have identified a problem that can be solved by an environment refresh. So we want to put in logic that identifies whether the environment needs a refresh and then refresh the environment. And of course we want to have zero variability threshold for flaky. We want to get to a point where we don't need retries to identify whether a test case is flaky or not. We want to completely eliminate that. Any time there is a failure, we want to get to a point where we have identified whether it's an error or a failure and whether it's a failure because of a regression introduced or a flaky test case. These are the improvements that we want in our service. Coming back to my mantra that I started off with, it's not automagic, it is automation. It's just like any other software development cycle. It needs testing, it needs maintenance, it needs a lot of attention from you and a lot of intelligent attention to be able to maintain and to be able to not just maintain the test code but have reliability on the test code. Okay, that's all I had. Questions? Thank you. You guys not only showed up without threatening, you also clapped at the end, so that's very good. Hi. How long it can take for a pull request like the one that we saw to be approved to run all the tests? So we try to make sure that the testing phase does not exceed 15 minutes. So we parallelize some of the modules that need to run and make sure that it does not exceed 15 minutes. So the amount of time that a pull request will wait for this module to finish is a maximum of 15 minutes. But in reality, a pull request waits for much longer than that to get code reviewed. No, we haven't. That's a good point. We don't triage defects by automation yet. We don't triage defects automatically yet. Triaging of defects is still a manual process that is team-wise. However, the defects logged out of this system are already grouped according to the severity of the test case that raises it. So if there is a P1 defect that gets raised, it will get attention. That is the error log analysis library that is different. So basically what we are doing is making a library of all the known error codes that the environment can throw while our test is executing. And every time there is a failure, we capture the logs and compare the error codes with any known error codes that we have. No, normally if you raise a bug, you might be seeing the same errors repeating in different builds, right? For example, a particular test case like a button is not clicked. So that particular failure you might have been seeing in across different features, right? But the failure would be the same, like the function is not working. So the error code on the API side will be the same. So in that case, why can't you try it automatically because you know the error code is happening again and again. So we do, we add that error code to the library, right? And then if we see that error code again, we know that this is already either has a defect associated with it or is an environment to show that the UI test, the client side really doesn't have control on. So we will mark the test cases error. And also like adding to your, this framework which was very good actually, and this change-based testing, have you heard about, right? No, I haven't. So it's like change-based testing, like every build whenever a build is being released, you are mentioning about reducing the chunks which we are doing, right? So you can implement this change-based testing where the priority test cases would be picked up based on the components. Understood, so you are, so I was not very sure about the term, but we do have something similar in our environment. We don't have it implemented yet. We are trying to implement it where we basically use tools like code analyzer and try to check what files got changed and then pick test cases based on which test cases are affected by those file changes. Actually, we are using that framework with the machine learning implemented. So we could able to achieve it very easily. So you can, at least if you want, you can use that kind of approach to reduce these chunks. That's very interesting. Absolutely, very interesting. Let's sync up after, okay? Thank you. After management on this flaky test, because even though you do whatever the things which you are doing, at least there would be a minimum of one percentage of issues will be there on this particular flakies. Sure, I would say the convincing was actually very easy because the amount of resources that we landed up wasting in just analyzing automation, we were at a point where the entirety of our effort towards automation was just throw away. We had a huge automation suite which nobody really paid any attention to. So it was very easy for us to convince that we needed to take a deep breath, stop writing new automation and make sure that we had a service and automated way of maintaining the code that we already had. And it was basically bringing back a much more return on investment for us. Okay, so I can understand if the product is coming from the long time. So if you are implementing it from the initial stages, it would be much more easier. But how can you give a call for the existing project if you wanted to bring on these things? See the biggest problem which we are facing is the existing test case is happening. Existing projects have 16,000 test cases. And every time you are getting the issues where we need to revamp the complete architecture or revamp the complete description. So actually this wasn't a new application for us. This was an existing application. You're right, it wasn't always easy to take a step back and revamp all the 16,000 test cases that you already have. What we did was we made sure that we were implementing a service like this and making sure that we were using it for all test cases going forward. So whatever damage is done in the 16,000 is done. Going forward, we are obviously writing more test cases and we were making sure that we were taking care of those new test cases. In the meantime, we were also picking out smaller chunks based on priority of the existing test cases and revamping them. So at some point, those two lines will merge and you will have a test suite that is stable. Great, and one last question. Sure. In the flow, I didn't seem like how we are deriving the coverage of the automation whether we have been covered. It was coming out of from the manual test cases and converting into the automation. That particular piece, I missed it. You may not see it, I'm late so that I might be missing that particular part. Sorry, I'm not sure if I get your point. So are you talking about code coverage? Automation coverage. Automation coverage. Test coverage with automation coverage. Right, so test coverage typically is done through unit testing or automation coverage. Code coverage is typically done through unit testing. These were all for the end-to-end tests that we had in our environment, the UI functional tests that we had in our environment. Okay, I will take off. Thank you. Great stuff, first of all. So this framework, you're only using it for the functional test and serenium test or also for the unit testing? Like the unit testing are not following the same kind of? No, the unit tests are not following. The primary hit on stability was for the end-to-end functional tests, especially UI automation tests. Something like this is hugely beneficial in that area. Unit tests, if they are badly written, may not be that stable. The entirety of the unit test suite is not prone to be that unstable as UI automation suites are. Any other questions? Thank you. All right, thanks, Vijaya.


The article proposes a method using seven indicators and principle component analysis, PCA, to forecast the transition from endemic to epidemic phases in contagious diseases, specifically COVID-19, and applies it to retro predicting endemic slash epidemic transitions of COVID-19 outbreaks in seven countries. This article was authored by Jules Waku, K.O.D. Ashinubi, Umar Mohammed Adam, and others.


Yn ystafell, rydyn ni i gael ei hunain ar y cymdeithasau cymdeithasol. Rydyn ni'n gweithio gyda Jim Gannon, CEO o'r Fathgrifedd Cymdeithasol Llywodraeth Cymdeithasol, yn ddifigio ar y cymdeithasol, o'r cymdeithasol, o'r ffordd cymdeithasol o'r cymdeithasol, ac mae'n ddifigio ar y cymdeithasol o'r cyfrifedd cymdeithasol. Rydyn ni'n ddifigio ar gyfer y dyfodol o'r cyfanydd yn ydych chi'n meddwl Ier everywhere we will be having an extremely stimulating and wide-ranging presentation and discussion. A couple of practical things first. Please switch off your phones. Jim's address will be on the record and the slides will be available afterwards. Okay, and then we'll have a Q&A session afterwards which will follow Chatham House rules. Rwy'n mynd i'n hyn o'r gweithio, mae'n gweithio bod allan o'r gweithio'r gweithio ar y clyw yng Nghymru a Llywodraeth Cymru. Y 28 ym Mhwng, mae'n gweithio'r gweithio'r gweithio ar gyfer Caroline Westblom. Mae'n gyfnod Cann-Netwg Europe. Mae'n gweithio ar y cyfle cyffredinol gyda'r gweithio'r gweithio gyda'r gweithio'r gweithio ar gyfer Cann-Netwg. Mae'n gweithio'r gweithio cyffredinol cyffredinol gyda'r gweithio peirio cyffredinol gyda'r gyfer Cann-Netwg Europea. Mae'n gweithio'r 16 o dillun, mae'n cyfrifio'r gweithio'r gweithio'r 2018 EISB, EISB Llector Series, a'u gyllideb i'r EISB. Mae'r gychwyn i'r Prifeseir Jean-Michel Glachon, gyda'r Ysgol dros am Ysgol yng Nghymru, gan swyddi'r llwyllio arall, ychydigau a chyfnogau, ac mae'n ffnwyr dros yng Nghymru, ac mae'n mynd i ddim yn gwneud i gydigiau a phabwysig. Felly, mae'n gweithio ar draws gwahaniaeth. Yn y ymgyrch, mae'n rhoi bod oherwydd mae'n gweithio ar y cyfnod. Mae'r gweithio cyhoedd ymgyrchol yma, yr SAI, yn ysgol maen nhw yw 2016.  Ddweud am ymddangos i'n gwrthoddiadau. Mae hi fyddwn i'n ni gwybod, mae'n ffrwg cyfnodol i'r byw, ac mae'n ddweud ymddangos i'n gwybod ymddiadol. Rwy'n gweithio yn ysgrif iawn, mae'n gweithio'r lleolau lleolau, yn cyfweld i'r mewn cyfweld, ac oedd yn cyfweld i'n cyfweld i'r lleolau. Mae'n gweithio'n gyfweld i'r lleolau perthynas o'r gwybodaeth yma. SAI's experience over the past number of years and our desire to increase social awareness, social acceptance perhaps, and then also in terms of specific decisions and interventions, increasing the application of behavioural economics and related sciences to the policy making process. I won't dwell on SAI, I believe most of you will know who we are, if not please visit our website. I'm going to briefly introduce where we are today with regard to our energy targets. Mention CO2, I'll speak to 2020 projections and also our 2030 challenges now that they are becoming clearer. And in that I will speak to the cultural relationship we have or do not have with infrastructure generally in Ireland. I'll move then on to behavioural economics, how SAI saw a need to educate ourselves better on that and to provide advice to our policy makers on that topic and then a couple of final closing thoughts. In terms of renewable energy in Ireland in 2017, and these are provisional figures, we had a relatively successful year. It was a good wind year in terms of capacity installation. With regard to transport we had an increase in the level of substitution of fuels. And with regard to heat there was a small level of decarbonisation but a lot of that might have been related to oil price and people's behaviour. And again oil price and people's behaviour is an important anchor point to have. In terms of CO2 briefly, decoupling can happen. I have a sense sometimes that there's a risk that Ireland will talk ourselves into failure. At the Project 2040 launch, Apologies last week, one of the contributors said that Martin Luther King didn't start a speech by saying, I have a nightmare and try to drive people towards change. He started by saying I have a dream and started leading people towards change with positive motivation, positive impact, positive interventions. So we have some good news stories in Ireland. In 2013 and 2014, despite strong economic growth, we reduced the CO2 intensity of our emissions from energy. In the next year, 2014 to 2015 and 2015 to 2016, our emissions increased but not at the same rate of economic increase. And last year, despite 4% modified domestic demand growth, which extracts aircraft leasing and IP transfers, again, our energy-related CO2 reduced by 2% or a little bit above. Our CO2 intensity in electricity reduced by over 9% in last year. So policy and private sector activity in tandem can have a material impact and does have a material impact. But a lot more to do. So in terms of our 2020 scenarios, last year SEAI would have seen us landing somewhere around 13.2% against a target of 16% overarching. This year we produced a number of analyses and that's due to the fact that our initial calculations would have started in October of last year for our projections this year prior to the announcement of the Capital Development Plan, which will see some impact on the ground prior to 2020 and also prior to a distinct change in oil price and the signal that that sends to consumers of oil, whether it be in your car or in Ireland in particular in your domestic heating. And these will have an influence. The net impact is that we still see ourselves reaching somewhere between 13% and 14% depending on some policy interventions that are made. In terms of 2030, you can take a number of different views. I think important to me is that Europe agreed a 32% level of renewables in energy about a week and a half ago. What that means for Ireland if you look at the 20% European target versus the 16% target we arrived at for 2020, it could see Ireland with an ask of about 26 or 27% of renewables by 2030. If that's the scale of ask, then we need significant activity across all sectors and the current methods we are using in a business as usual case likely may not reach the target. So we need new methods of decarbonisation. We need new methods of incentivising renewable electricity in this country. That said, I think it's very important to make the point that our expectation should not be that the national development plan and the Exchequer funding described in that is the limit of our ambitions. One thing that is true around the world and being realised by many, not just as a challenge but as a business opportunity, is that private sector finance and our organisation Sustainable Nation Ireland would speak to that quite well is required and at scale. And we're now working, I'm going to the Banking Federation of Ireland after this meeting. We are speaking to the EIB, private sector finance providers as well, on how we engage that finance. What is the regulatory planning, licensing and consenting framework that needs to be in place to attract private sector investment to decarbonisation? And that's with regards to large scale infrastructure but also importantly with regard to smaller scale interventions. How do we efficiently aggregate small scale interventions like domestic retrofit or SME energy efficiency? Where the amount of finance in each packet required is quite small but if we can bring them together it becomes attractive to institutional investors. In terms of global clean energy investment, again I suppose the prevailing wind is quite positive towards it. Lots of sustainable energy technologies are on mainstream. The value proposition around energy efficiency in large industry certainly is well recognised. In certain segments, even here in Ireland, lighting is seen to be an area where activity can increase and lots of new business models have come into Ireland in the past year and a half that provide people an ability to execute an energy efficiency project where they don't necessarily have the means to finance it themselves. I do think that there is a very obvious increased interest in international banks, structural funds and private sector funds over the last two years both in terms of infrastructure and in terms of on the ground investment in aggregate project types. So to my mind a positive out of this is that clean energy and energy efficiency isn't just an environmental fad anymore it's just a good use of capital in many cases. It is a good investment to make. It's a matter of looking to see where market failures are between good uses of capital in specific projects and the finance that may become available to those projects. And again, this is the type of activity that ourselves and also the people in Ireland are heavily involved in at the moment. I'm going to focus on renewable electricity for a minute to bring it down to a point around social acceptance and awareness. The cost curves for renewable electricity technologies are coming down quite quickly. And there is an opportunity there for Ireland to capitalize on this, taking the learnings from other jurisdictions as they deployed themselves renewable electricity. We are the sustainable energy authority of Ireland, not the renewable energy authority of Ireland. I think it's an important point to make in that our modelling exercises see Ireland using gas in particular for a number of years yet to come. It will take us a long time to decarbonise fully. Many of the international modelling exercises also see a requirement to use natural gas on a long-term pathway to decarbonising as it balances some of the intermittent generation we see coming down the line. Some of the challenges here for renewable electricity generation are obvious and they're spoken about quite a bit. We're on planning and consenting, market regulation and policy consistency and certainty. Also I think something that we don't speak to often is the scale of market in Ireland. Ireland, for a lot of the major international developers, is small scale. And the type of individual project you see in Ireland due to our spatial development pattern are smaller scale projects. So that large scale project where you can deploy lower cost finance, it's harder to find in Ireland. I think even if you imagine that you resolve some of these challenges and constraints, you are faced with that social challenge, that social acceptance challenge. And at the core of this is where we have a gap between society and its valuing of infrastructure. And I believe that this is across transport infrastructure, water infrastructure, energy infrastructure, you name it. For most people they don't engage or consciously think about infrastructure unless something goes wrong with it and there is a fault or unless new infrastructure is required and it's perceived as an imposition. That day-to-day salience or value of infrastructure and the value it provides you is at the core of a lot of our challenges. And I think it's quite important because people in a room like this can influence political will but political will is derived from voters and people on the ground. And one of our activities more recently, the Sustainable Energy Communities Network, provides mentors and support to communities whereby they develop their own master plan for their community to decarbonise. And we are finding certainly at a qualitative level, we're going to perform quantitative analysis on it in parallel, that attitudes are shifting and that those people involved in determining their own transition to a low-carbon economy become more aware of the fact that we need some of this infrastructure. There will be challenging projects in certain locations but they become aware that we may need pylons. We may need wind turbines but this has to go somewhere at some point in time. I think creating that link, creating that salience will become far more important as we increase our ambitions and the ask of Ireland is increased over the next number of years. So what do people in Ireland think? At a high level it's relatively positive. This is a Euro barometer survey, not a survey by anyone in Ireland or an NGO necessarily. So this asked a representative sample size what do you think about climate? 68% said climate was a very serious problem. Interestingly an additional 25% said that it was a fairly serious problem, fairly serious being a particularly Irish expression but it's on their radar nonetheless. 34% said that business and industry play a key role. Just behind the role they felt that the government and policy makers play. And then finally that fighting climate change can boost the economy. This is very important for businesses because as a business you supply a product or a service to a consumer and consumers are led by what is on the forecourt, what is in the shop and by their professional advisers. And separately you employ these people and the influence you have on these people and the type of person you want to attract can be heavily influenced by the signal you give. I think with this underlying belief and this underlying importance in people's minds we have started asking ourselves the question how does that impact us in SEAI and our day-to-day delivery of our activities? If this is underpinning people's beliefs how do we get them to interact more with our better energy homes scheme? How do we increase electric vehicle uptake? How do we get them to look at their oil boiler and consider alternatives? Whether it be a less carbon intensive fossil fuel or a transition to heat pump or other electric alternatives? I think something around this is quite important as well in that the Irish society and society generally is more interactive, is taking more control and there's an appetite here for change. I think that's being matched by technology cost where you see the cost of photovoltaic panels coming down the cost of technologies coming down that will allow a consumer to interact more with the system and interestingly this technology price curve is matching policy direction from Europe where Europe has started stating things like the clean energy package that they would like to see people with a right to generate in their home a right to export and a right to a market price. Now it's left to determine whether or not that falls down into local legislation, local SIs but that is the general direction of travel and to my mind there's an interesting point of divergence here where you'll have some people who want to be very engaged they want to have an app where they respond to a price signal from a market and they tell their dishwasher or their fridge or something else to switch on and switch off but the likelihood is that we will again be a consumer led market and someone could come along and say we already give you your telephony your broadband, your television channels we will add the energy service to your bill and we'll deal with the rest we'll deal with the controls, we'll deal with that headache don't worry about it, you can trust us and that's where trust becomes very important in that if we're accepting these technologies in this level of sophisticated control into our homes and we're giving that to someone else to control it in our home you need to trust and want the service that they will provide and this will be a challenge we face particularly as we start rolling out smart meters over the next number of years what is the value proposition for the human in their home as we look to place smart meters into that infrastructure so in terms of behavioural change activities that SEI is engaged in that led us to this front of wisdom would have been just trying to influence people and businesses so to reduce energy use, to install sustainable energy generation where it's cost effective, where it's sustainable to purchase energy efficient products, appliances looking at the energy labelling schemes and market surveillance authority role installing energy efficiency upgrades so this is the building envelope, the heavier pieces of kit and then again creating that link and understanding the value of sustainable energy in your home, in your business, in society on a day to day basis so our activity today runs across some of these programmes I mentioned an example earlier for our fuel poverty directed scheme we used to issue a letter that said would you like a free energy upgrade to your home that is worth and we insert the number and there's now a value suddenly to that energy upgrade to the home similarly across a couple of other programmes we're using smaller interventions at different points along with their decision making process to tie them to it so someone who applies for an initial building energy rating or not building energy rating, better energy homes grant to upgrade their home there is a drop out rate between that person who applies and the person who actually delivers down the line so we're trying to see how do we widen that sales pipeline for someone who becomes interested and signs up to a grant at the start making sure that we get a higher percentage of execution and delivery down the bottom end now it's key to us around this consumer choices making it easy for people so how do we increase awareness how do you make it understandable and just easier to execute separately how do we engage them at the right time so we're aware from our research that once every seven years people will generally decide to invest in their home it could be a small investment, could be a heavy investment but you have that one time in seven years to really engage with them and bring them towards deeper retrofit bring them towards a more decarbonised position how do you know when that's coming up how do you position yourself to make that timely I suppose finally you need to make it attractive they need to want to do it is it through a financial incentive is it through showing them that other people in their housing estate have already done it and that for that housing estate where your home is exactly like your neighbour's home you should be able to do this and cost effectively and finally how do you make it social which speaks to this second piece how do you let them know that other people just like them are doing it that this is what people are doing now and bring them down that road and bring them down that road of peer awareness and not necessarily peer pressure and this speaks to one of the frameworks that underpins behavioural economics which is the east framework how you make things easy, attractive, social and timely and SEAI had started looking at some of these aspects although not by design up to a couple of years ago a year and a half ago we determined that we wanted to get more involved in behavioural economics as a science and also determining how we could bring that value to our policy design role so for our department for all the departments notably housing planning and local government we assist in the policy optioneering space where a demand for policy is outlined whether through a European directive or from the political class and from the department we engage in that data and analysis piece that underpins the ultimate decision that is made in the department what became more important to us is that where these interventions approach a homeowner or a consumer or a small business in particular behavioural sciences had a lot to add the analysis and the empirical evidence that can be brought from behavioural tests can inform that policy decision making piece and again at a very simplistic level we started looking at economics should we continue on the path of grants to the mass market or should we start looking at different methods of incentivisation in certain cases should it be looking at low cost finance should it be a tax rebate in certain cases maybe an economic incentive isn't required at all it's a different method of incentivisation in terms of psychology how could we increase the salience of comfort and benefits in the home how do we reduce hassle factors how do we increase trust in the advice we give and also framing how do we provide that framework within someone's mind that leads them to the right decision and then finally making it social how do we use the activity of neighbours the activity of people just like you to encourage you to bring it on that path making the right decision I won't go into a list of behavioural interventions I suppose what happened was that we started reading papers about behavioural science and behavioural economics and realised that there was an awful lot more under the bonnet than we realised as a result we put together a behavioural economics team that examines economics, psychology and sociology I think what's important is that there are a wide range of potential interventions and varied impacts from all of them I think what's important from our perspective is keeping an open mind similar to the technologies we will have to use to decarbonise Ireland over the next number of years there is no single solution there is no single intervention in certain cases we might not know the specific pieces of an intervention that really had an impact the plastic bag lovely was cited earlier and it can be hard to disentangle whether that was a social framework and people felt almost pressurised because people weren't using plastic bags anymore or was it the personal decision whether it was the actual cost or the principle of paying 5 cent was the motivating factor in either case it worked and in effect might be harder to link I think we also need to recognise fairly clearly that there are differences in local economic and social conditions and as we conducted our review that we are publishing next month this became more and more apparent just because a behavioural economic intervention worked in a particular jurisdiction doesn't mean it will necessarily work here in Ireland where we could have different social economic or other underpinning I suppose environmental conditions briefly an insight into our review we reviewed nearly two and a half thousand papers we took that down to an abstract level and determined which could be of most value to our review we brought that down to 175 papers then which we looked at in detail and these were papers which described empirical tests that we felt were delivered in a robust way of behavioural economic interventions it was not lab-scale testing it was in the field testing in each case of interventions that may or may not have worked in terms of reporting apologies, in terms of reporting outcomes we'll publish in July it will be very open in terms of its publication we'll be inviting people to engage with us to ask questions on the case studies that we're looking at and also at the end of the report we do come forward with recommendations the range of different interventions that are there that you could look at is staggering and it will be important that we prioritise and we approach it in a timely way and that there are some interventions where we feel you could have an impact in a short space of time so let's go ahead and try those now in other cases we'll work with either policy delivery or we'll work with private sector entities such as energy supply companies right now to see what can we build in over a longer period of time some of the reporting outcomes were that there's too much emphasis being placed on the residential sector there's very little being placed on the commercial sector and although industry makes decisions in a different framework small, medium enterprise does have a decision making paradigm that is similar to the residential sector so we think there are more learnings and more tests that can be put in place there there's a very small focus on what works for encouraging energy efficient measures as distinct from other behavioural measures so behavioural change in terms of someone leaving a room and switching on or off a light at the right time or changing the setting on their thermostat quite a bit of focus on that less focus on what incentivises someone to purchase something that is more energy efficient or make that installation choice where they will pay a premium for upgrading their building, their business and and there was a very low focus on the actual energy saving associated with the programmes so for SCAI we are focused on the outcome, the real impact of this intervention so to our mind and I'll cite a couple of examples later what we want to know is that for years one, three and five that the intervention made had an impact that stuck and again reflecting back on this piece trying to get someone to change their behaviour in terms of switching on and off lights there can be quite a bit of rebound there whereas if you convince someone to make a purchasing decision that changes their decision from applying a B-rated appliance to an A-rated appliance that appliance will be in place performing that function over a period of time if you can change their behaviour where they want to upgrade their home to include aspects of energy efficiency or decarbonisation in particular that will stand the test of time so again for us we really want to focus on impact, how do you lead people to decisions that have a lasting impact as opposed to a short term change of their mentality one interesting area for us that highlighted something more general was we don't need to necessarily develop new routes to market in each of these cases so in some cases we need to look at how we communicate more efficient driving or improving your car's performance from energy efficiency and safety perspective by going with a better tyre to people so instead of trying to develop a new route and broad brush advertising let's look at the NCT where many people sit every year worried about the performance of their car can we engage them at that point in time everyone gets a tax certificate and mostly people get an insurance certificate every year can we use that point of contact that point of concern to deliver a message there I've already mentioned the warmer homes the warmer homes proposition around value one other case is with the generic energy bill that people receive some electronically, some on hard copy and there are cases internationally where you can bring a lot more value to the customer through the energy bill one example is where they started showing people how they performed against homes that were just like theirs and there has been an impact a lasting impact from that sort of communication this is something where we can interact with energy supply companies on this front and in quite a short period of time two other specific examples one was O Power on Honeywell where people were given a more sophisticated control over their energy use in the States and also they were given one of these home energy reports that was intended to engage them in that peer effect how am I doing against my peers against homes that are more like my own this is a suggestion of savings of between 2% and 5% a separate one in Germany was on defaulting and defaulting is analogous to some other examples such as pensions if you were defaulted into a pension and that is your starting point some may choose to come out of a pension if you were defaulted into being a donor of organs more people will stay with that default position than will choose not to be is the non-participating most people will stick with that so in Germany they defaulted 150,000 electricity consumers to a green tariff these consumers were told that the green tariff was more expensive than the alternative tariff which would have been conventional energy yet over 90% of people stayed with that green tariff our challenge to this study was the after two months or to my mind it comes back to this frequency of decision making and within that two month period how many were likely to change their energy supplier in that period in any case so my interest is in if they were defaulted to that how long did that stick for is it one, is it two, is it three years down the line but nevertheless it shows the power of defaulting and that is one of the areas we feel that early activity could benefit us in terms of what next in SCAI we have an upgraded BER advisory report coming out so the building energy rating in Ireland was of its time it required an update in terms of the sophistication of assessment and also the sophistication of how we communicate that to the homeowner and we have intentionally involved our behavioural economics unit in the design of that report using priesthood and other jurisdictions so when you get a building energy report that previously wouldn't have gone into specific detail about your home as much as it might the new report which will come out in August will go into very specific detail about how your type of home with the condition it's in can be upgraded along a certain pathway and again we've used different types of signalling here up the top is loss aversion instead of saying if you invest this much you can save this much it's saying you are currently losing this amount of money for not having made a certain decision we're also using benchmarking against houses of a similar type and we're also using an approach around meaningful benefits trying to make it tangible to people how their home could benefit and how they could benefit in their lives I think another aspect that's important in this is tying the behavioural economics piece to that value in the consumer's mind it is something that we are looking at and will continue looking at in SEAI whether we would continue providing grants for measures so you provide a grant for insulation you provide a grant for heating controls we need to have a more informed and a more engaged consumer if we want to move to a paradigm where we're saying your house is at D2 if you move it to C1 or B2 or A2 the amount of grant funding that is available so your funding performance as opposed to funding specific measures this sort of gap well this sort of gap around awareness and understanding could help be filled by the communications aspects I suppose and targeting of behavioural economics finally and apologies for the ramble although focused on individual decisions and we do expect to take a pragmatic approach on this there might be percentage changes here or there you have exceptional cases like the plastic bag levy where there was a huge return and a huge response to the incentive that was put in place but our expectation is a rational one where we expect small incremental change in the decisions of home owners over a period of time so 2%, 5%, 10% here in SMEs a 2% change a 5% change, a 10% change here we don't expect that this will solve the problem in and of itself it is just another value adding lens through which policy should be viewed particularly in the development stages separately the report that we are producing should be considered just a starting point it will be very important after the publication of the report that we prioritise that we work with people in the public sector and the private sector to say which interventions should we look at first where will value be derived and how do we communicate that to consumers, to business owners and to those who will be involved in the development of the intervention and finally we do have a true belief that informing and empowering and motivating the individual can have an influence not just on their smaller scale decisions but also on how they perceive large scale infrastructure projects and technology adoption and I think we are about to see analogues of social acceptance to large scale infrastructure around some of the smaller scale but high aggregation infrastructures that are coming into place the first by illustration will be around smart meters it is not a single piece of infrastructure a single pylon, a single substation a single wind farm it is a large scale aggregation of small interventions where societal thought will coalesce around it how do you make people value that infrastructure, accept it want to interact with it and be around electric vehicles or around electrification or other uses or other I suppose options for heating so again I think linking the small to the large is quite important we have seen evidence of it in our Sustainable Energy Community Network and we will continue to drive things in that direction that is the end of the formal presentation piece again sorry for the slightly inchoate nature is a topic that is new to us


Hi everyone, this is Jason Zak from Nathaniel School of Music. In this tutorial, I'm going to give you a few suggestions or steps or guidelines if you will over my years of experience towards what I call the future proof piano accompaniment goals which you need to have or a future proof piano accompaniment flow chart or algorithm which you might need to develop in order to play not only the song which you want to play right now immediately. Maybe you have a list of one or two or maybe five songs but you want the fourth or the fifth song to be radically easier than when you first started. You want it to be exponentially easier so to speak. So it may have taken you about two weeks to do a song but then the next song should take you one week. The song after that should take you two or three days and then you should be able to figure out or finish off an entire song in a very very short time compared to where you started. So the idea here is to follow the learning process in a set of steps and as I tell you the steps you just take a song which you're working on. In the intro video you heard me playing somewhere over the rainbow which is a great American Broadway theme song from the movie Wizard of Oz you must have seen. So it's a great movie. So using that song and maybe a couple of others organically I'll try and guide you towards how you can end up with that with the melody, the harmony, a rhythm pattern and the like and so on and so forth on your piano. So before we get started all of my handwritten notes will be available on Patreon for this lesson as well as stuff we've done in the past and what we are going to do in the future and all these lessons will include my handwritten notes, backing tracks to help you practice, MIDI files to help you import into other players to watch and learn with all the technology gadgets out there and you'll also get staff notation for a lot of the other lessons too. And it'll be awesome if you could hit that subscribe and the bell icon for regular notifications. Let's get cracking. So the first future proof step towards piano solo arrangements would be accompaniment. Now you may think hey I want to play the tune on the piano but why are you telling me to accompany? Who am I going to accompany? So accompaniment means you're going to decide the rhythm pattern of your song for the purpose of accompanying the melody done by either yourself with your voice or done by a friend who's singing with you.  So in a sense you're still accompanying the melody but you are only playing the melody. So solo piano is you are doing everything including the melody while accompaniment you're still doing everything except the melody where someone else is doing the melody. So only that one part is not there the melody. So if you take somewhere over the rainbow you can first figure out the chords and sing over that chord progression. Let's just take one line. So I'm trying to get acquainted with my chords and when the changes occur with respect to the tune. So you need to get the chord changes first with the song you know. Let's do that again. Somewhere over the rainbow way. Get that minor in if you wish. The plagal minor which is the four minor land that I heard once in a lullaby. And when I'm accompanying myself I first try to just kind of broadly think of my song as ballad or groovy. You know those are two simple words which come to mind. If it's a ballad you can just kind of keep your chords like this. Just play the chords as blocks and just pump it down you know. Or also look at ballad arpeggios. So it's just a simple low middle high middle arpeggio going on. So if it's a ballad you should probably decide do I want to play if it's an Adele song for all you know you'll probably be playing arpeggios. Stuff like that or you know a lot of the Adele songs have arpeggios in them. However if it's somewhere over the rainbow and it's a very kind of it's almost you could call it a jazz standard in the sense so many have covered it so many have given their interpretations and their improvisations over it. You can decide what pattern you want and what I'm trying to point out in this step is it's a lot of fun and it's not very stressful on your mind and body because if you have to put in all the parts together at one go you're going to think very robotically and very mechanically it'll just be oh where do I get the sheet music maybe I'll google it or and then how how do you trust google there'll be thousands of sheet music available for let's say somewhere over the rainbow. Then what do you do who do you trust you may watch a youtube video but then you can you trust that as well you know you someone or the other might have everyone has their own interpretations of the same thing so you'd rather have your own rather than follow everyone around you and start with the accompaniment so you write down your chord charts keep that ready where the chord changes occur is very very important does simple things like somewhere see I changed from a flat to f minor the two tonic chords the major tonic and the minor tonic I changed it after two beats I didn't change it after four beats even though it's a four by four song you can expect those chords to change every four counts so somewhere over the rainbow now over the rainbow what's happening is over the rainbow you can get that secondary dominant going which is the five of the four way up high that's an a flat over C played four times so you have to know when the chord changes occur what are the chords how to play the chords what is the shape you would prefer and then you can figure out how to bring the melody into this whole ecosystem and one common thing to do is you take your right hand let's say you're playing a ballad and you just play the chords in the right hand as a ballad and you sing okay I'll just stick with that now here's what you do you're looking at the right hand and it's doing block chords so why not take the same function of the right hand and bring that to the left hand so as you just saw I've transferred my right hand to the left hand and I'm continuing to sing so if you like the arpeggio line well and good if you want a faster arpeggio now in hindsight maybe quite like this so if you like that busy kind of arpeggio maybe you want to create a folk version of the song so whatever it may be try and test it out with the vocal and now your job will be to bring that to the left hand you may not like this but you get the idea you could have a folk interpretation of it you can even do a rock interpretation which I may not recommend for the the faint hearted even I don't like it actually so let's forget the rock version but you get the idea so you maybe a reggae version with a little bit of swing right so you set that at the very top level and then you commit to the arrangement you want so a solo piano arrangement the word arrangement also is important there right you have to arrange it in a way which brings out your personality or serves your interpretation of the song best and if you commit to the time feel and if you say I just want to do it straight I don't even want to consider swing then what was in your mind your vision will be lost also if what I just showed you the reggae version or the folk version that you need to set at the top level and it becomes very tough when once you have the melody printed in front of you and ready to go you'll always play it in that one way so this is not that's why I call this future proof because you're testing different genres you're testing different time feels you may even want to play it in different meters in different time signatures you you want to do seven or whatever these top level decisions you need to take before you start playing the melody you see I haven't yet played the melody I'm still singing so the song also needs to be in your head the basics are obvious you need to have heard the song enough and more times and then it's running you know permanently in your head and you're trying to latch on to different things which you which suits your whims and fancy so to speak so moving forward we've covered two processes in the flow chart first of all make an accompaniment version decide your style your genre your pattern a b it do it alongside your singing over the chord progression figure out the changes and all the basics of the chord movement then transfer that pattern somehow using your skills using your technique to the left hand practice that continue singing and now organically continue singing but bring the melody because you freed the right hand now the right hand doesn't get to do anything somewhere you put the whole pattern to the left hand so now it's your chance to bring the melody there and what I will say is all of these all of the work starts with the brain the brain sends a message to different muscles different parts of the body to do certain actions so if the brain is able to send a message to your vocal cords to sing the song the same information believe it or not it's quite obvious actually is going to your hands as well so also going to your legs it's going everywhere if you wanted to the brain will just pass that data through the network to reach another body part it is easily reaching your voice your vocal cords because that's what we do in nature with language and speech right you want to get something out it's the quickest way to do so is with your voice and the gestures as well so the brain now needs to send it to the the hand and you the best way to do that is you're already singing it so align your singing with your piano you know and somehow try and get that this is where you may want to maybe read the sheet music no problem but don't stop singing and then slowly but surely bring back that left hand pattern which you committed to and play it together and with singing what's nice from a future proof perspective and also from an improvisation perspective it's easiest to come up with changes in the melody like if i wanted to do you know that's a vocal thing now to do that on the piano it would not have been your your instinct to do that but it's very easy to come up with that with your voice maybe make a quick recording of it on your cell phone voice memos so that you don't forget and then try and work that try to muscle that into your practice see i try to get what i just sang so all that came from my voice you know i would have never come up with that on the piano i feel it it's just come from the voice instead of the usual the word of all the words can be sung with so much of color you see what's happening here i'm not getting it in instantly wrong so take some time to match that at all you could even stick with the original get that going and work on different left hand patterns alongside the a more normal the the correct melody of the song so to speak so maybe you can ab compares in arpeggios with something groovy something groovy like that or maybe something laid back so change your left hand accordingly according to whatever genre you want and the advantage of doing all this i think the last thing i wanted to point out in this lesson would be now your left hand has been given a solid workout because you've tried to check so many rhythm patterns against so many genres with this song that it's now going to give you the confidence or the skill to play other songs maybe you can decide do i want to do a mash up maybe or do i i i thought of doing somewhere over the rainbow and reggae but i don't think it just it works for my rendition but maybe i can do another reggae song with this reggae thing which i learned and maybe that'll be on a much easier scale that'll be on maybe g major or c major you know so you can think about a very think about the future this has to be a future proof strategy and any future proof strategy is not going to come to us instantly we have to wait for things to grow so it will always be an exponential growth curve where it'll start with something which appears to be a struggle which is exactly why i said sing from the beginning because you're not going to get annoyed with the effort or the job singing is always fun so keep your singing into play keep your chord changes get the basics and one one thing i may not have mentioned in the beginning or stressed on enough in the beginning was don't forget the basics of what you're playing the pulse of the song how you move to the speed or the tempo the meter don't take that for granted is it a 4-4 is it a 6-8 is it a 3-4 or something like that decide the cycle length how long is each phrase for define your chord changes which i already told you and the time feel is it swinging is it straight is it a triplet feel or whatever else it might be right guys so do consider heading over to our patreon page as well which will equip you with some of the handwritten notes for this lesson and so many other lessons which we've been doing over the years and what we'll continue to do of course and there's a subscribe button right next to the video which you're watching you can kindly hit that on there's also a bell which you can ring don't worry it won't make a noise just press it and you'll get notifications whenever we release a new lesson or a riff which we do daily on our channel thanks a ton for watching the video cheers catch you in the next one


Everybody forced here ripping 22 23 Revolution basketball hobby 16 bucks full case number three tiered you can find the results anytime elite in sports cards.com Let's see what we got here. Good luck everybody. It's just like revolution saw her revolution I see the couple of the black Empire Prop probably Kyle Yeah, you get it SSB's to work tech screen astro Wiggins for the Warriors Jovich rookie guy fractal rookie revolution Jabari spit Junior Rock. It's Harding got ejected Really That's Steph Curry shockwave rookie groove Malachi random spurs Ben Kara rookie for the magic and a cubic Knicks Julius Randall number to 50 there you go Knicks 7 to 50 I would do all numbered cards lift off Levine. We got Astro Gordon Hayward AJ Griffin groove Michael Porter, Jr. Nice Justin. Good luck. Yeah, pal. It would be awesome Tyrese Halliburton vortex We got Astro down of a Mitchell calves as a mobilee rookie with a rookie astro Blake Wesley for the spurs Shockwave Devin Booker Vortex James Harden cosmic to 99 you go for the for the Sixers there Paloban Kara rookie base group Jimmy Butler Shad Holmgren rookie revolution groove rookie Blake Wesley spurs AJ Griffin got Astro Ricky Kenneth often junior for the Grizzlies Portex Palo Astro John Marant Grizzlies Rookie is ammo believe vortex fractal is a Kauai Leonard for the Clippers LeBron James supernova got our first auto coming up after Astro Kevin Porter, Jr. And it is a Pelicans auto CJ McCollum Kendall Brown Cosmic Kyle Kuzma Kyle Kuzma cosmic 78 of 99 wizards Alliteration right imprisonment next Thursday Thursday Monster Jam Just the Clippers just the Clippers in expensive There might already be Monster Jam cards, what a great digger card Don't we all? Monster Jam rookie revolution shade on sharp with the Blazers fractal clay Thompson for the worst used to be a Monster Jam parallel Monster trucks in the back monster trucks and like pyrotechnics Every right next hi-tie Washington fractal vortex Kevin Durant's Board of Nets Shockwave down of a Mitchell with an Astro Chris Middleton for the Bucks Mark Williams. You've got a future frame rookie for the Clippers. Moussity about a 15 of 60 Vortex the honest groove rookie Andrew Nemmard for the Pacers Mike, what's up, man? Sixer stink dude Benedict Matthew and rookie for the Pacers groove John Collins for the Hawks Sixer stink that's why they're up to nothing in the series Anthony Edwards super Nova then Astro Andrew Wiggins Warriors Best player in the Warriors chat home green Ricky No Rookie Astro Dale and Terry for the Bulls.  He's so many got Astro Evan Mobley Zambobley groove Jalen Green Rockets Dyson Daniels Shockwave Astro Middleton for the Bucks Three one after two. That's pretty good. It seems like they're just gonna roll the Devils rookie Astro Malachi Brandon for the Spurs Devils ain't ready for playoff hockey Keegan Murray Vortex Kings rookie Fractal Kyle Kuzma Kennedy Chandler. We've got a fractal Shockwave Jane and Ivy pistons Lift off Jalen Green. We've got an Astro Andrew Wiggins and an auto Evan Mobley on card Cavaliers There we go cash congrats on that one Car so so far all I've seen is him and Luca on guard. I don't know if there's any more Wesley got a Michael Porter Jr. Future frame 43 of 60 for Denver Yeah, Vaughan. They're cooked. They can't handle the Kings. They can't handle him vortex jaw Astro Jalen Suggs They're blinded by the purple beam got bow champ. We got supernova fractal. Yana Sons of the Coomble for the Bucks Keegan Murray Rookie Revolution for the Kings and Astro Jalen Green Rockets So Vaughan I got some crumble yesterday Got a rookie Cosmic who's Manjang to 99 for the Thunder Oreo the Oreo birthday cake is pretty good. The best one is the shortbread caramel at the Twix one the best That's that's easily the best one Shockwave Lamello. We've got a Zion Williamson lift off Cosmic Number to 99 for the Pelicans now Easily over got a groove heavenmobile for the Cavs Do the Twix one is this it's seriously really good. The other ones are kind of mad. The Oreo ones are right the The peanut butter muddy buddy ones is fine. It's okay Yeah, rookie groove gala Houston for the magic So One of your Saturday the close Sunday menu switch Rookie Asher Marge on Bo champ for the Bucks Little pricey it's probably five bucks cookie They will they will they will make good for your soul Rookie Revolution Tara Eason groove rookie Matherin Pacers Klaxon ejected J. Dubb got groove Tyrese Maxie Sixers He's gonna have to carry him everyone's gonna jacket Shockwave Dyson Daniels with an astro Andrew Wiggins again other astro Wiggins Marge on Bo champ astro rookie Christian Brown Denver Vortex King and Murray Kings astro Gordon Hayward Vince Williams jr. Vortex fractal Trey young Atlanta Come on now Jalen Green lift off for the Rockets with an astro Donovan Mitchell Cavs and a rookie auto for the Spurs Malachi Brannum Malachi Brannum third auto so far. So we should have one more in one of the next two boxes. That's good Patrick Baldwin jr. Demona Sabonis Kings future frame 50 of 60 Kings Abyss Doma my last two of the first intercase He can Murray shockwave for the Kings with a vortex cosmic Damian Lillard Blazers It's a 99 Think it was 33 of 99. I think Dylan Terry groove Jaren Jackson jr. Defense to play of the year DePoy as they call it Lift off John Morant groove Lakers rookie Scottie Pippin jr He's got a no-tip and Pippin Williams there astro Vince Williams jr. Rocky for the Grizzlies That was a bright thing Vortex so Han we've got an astro Lamello ball for the Hornets He actually is a notoriously not good tipper as well so it makes sense for Scottie Pippin That's dead fractal shockwave the honest undercouple Bucks Donny versus the top loaders Wow great defense on a jewel and bead there math or in Ricky revolution within astro Kelvin Johnson spurs and a vortex Galactic the call Kauai Leonard clippers About one a case on the galactic short print congrats clips we'll get this one mag for you Clippers a second tier two for Tyler F. Congrats Tyler Oh Galactic Yo, bitch. We've got a cosmic John Moran Grizzlies numbered 59 of 99 in jar galactic How did that shot rim out? I don't understand that Wow What is happening right now? God dude, what is happening in this game shockwave John Moran astro Brogdon for the Celtics Christian Brown groove Anthony Edwards T-Wolves Guys are Marlon. Sorry that happens. I'm gonna forward the email now to shipping and I'll get back with you tomorrow at some point Got vortex Steph Curry got an astro Bogdanovitch for the Pistons Ty Ty Washington astro rookie Jalen Doran Pistons supernova Tatum a fractal Clay Thompson for the Warriors Mark Williams a fractal vortex to bars by the junior Rockets rookie who could dodge it Vortex astro Rudy go bear and an auto carlick in the town's T-wolves Eagle, Minnesota That movie probably is still fake Victor. Jasper's not that cheap back then But it's math Iran. It's like the same prices. It is now honestly got impact Bogdanovitch to 149 for the Pistons Maybe a little higher currently, but like it's not much different this week. It's been expensive. Yeah By Samford's like Like few months ago I was still like just above three that's not that crazy. All right, here we go Second half everybody already hit the galactic. I don't I don't think we've seen two from two in any master case so far You'll to see one but uh Can still hit some other SSPs and obviously some big cards, so let's do that Let's see the next prism is sold out very nice on Number 42 There's nine to go So we'll get you guys link for that one It's quite a few teams all of them are on sale to Celtics Nets Hornets Rockets Clippers Sixer Suns Kings and Wizards, so some good teams left some cheaper teams left as well. Let's keep it going Yeah, so if you have the Celtics and Hornets in this break Then you'll get all the cards from this one because all the cards ship in this break Yeah, next vehicle I get is gonna be electric got Kyrie got a groove rookie AJ Griffin for the Hawks Definitely EV is the next way out next next way I go Jane Hardy rookie you've got a rookie a show Marjane Bochamp for the Bucks like you get electric vehicle and You live in an apartment complex. They're don't have any charging Mine does lift off Anthony Edwards got Astro City Bay the Pistons prime time performers Short print Shet Holmgren Thunder SSP those are tough pulls right there congrats. Okay, see So what we're looking for John V congrats That one mag for you. Oh nice first time got an impact Kendall Brown rookie for the Pacers that one's number to 149 Vortex Sohan Astro Terry was here for the Hornets Jabaris with a junior rookie for the Rockets Groove Chris Paul Sons Donnie out figured out We're just move But the EV thing well me I'll be able rookie fractal Malachi brand of spurs. What's up? Think my apartment complex has a couple spots like that. I don't know though Walker Kessel rookie. Oh Like that one 18 a 75 Sunburst rookie magic Palo Ben caro Just an S with the magic getting a mag for you Angle it's hard to even on camera Yeah Now Donnie's mad Disappointed I think it's more the word Cosmic Christian Wood to 99 for the Mavericks Well Kyle, which is it the chat or the Palo whisperer for Tex Levine Astro City Bay Pistons Rollins groove John Marant Grizzlies. He's just the revolution lift off Zion rookie fractal Kendall Brown for the Pacers Shade on sharp Astro rookie Peyton Watson, that would be the worst break of all time, right? That would be the worst break of all time shockwave Edwards Astro Terry was here Dale and Terry with a vortex fractal Kevin Durant Nets Vortex Tatum grew Peyton Watson rookie nuggets and a Hawks auto Lenny Wilkins I'm gonna run out of space for these in all these cards Yeah, I could have three Kings Brother Supernova Jabari Smith, Jr. We've got a fractal bam out of bioheat Jibari Smith and Jibari says junior rookie groove Luca Vortex Lillard Astro Devon Vasell Walker Kessel rookie for the jazz Astro Coloco rookie Raptors Sohan rookie revolution spurs groove rookie Coloco Raptors Mike is that for the Rangers? Yeah Fractal rookie revolution for the Grizzlies Jake Laravia and that was gonna get sweat Not about this life Shockwave Luca Astro Porzingis and a jazz auto Collins sexton fractal 27 100 For the devils Yeah, if we get if we can get there Carl Get past a stomach virus rookie groove Johnny Davis for the wizards Benedict Mather and rookie fractal vortex James Harden Sixers You're on a supernova astro Steph Curry Got a Chet rookie cubic Jared Jackson jr. Grizzlies the 50 16 to 50 deploy that's what they call them Depot a defensive player of the year Shockwave Jaden IV astro DeMar DeRozan. Oh shag bhaji rookie. You've got a group Desmond Bay and Grizzlies a j griffin rookie revolution fractal rookie break Blake Wesley for the spurs Sohan rookie spurs astro Ricky Liddell for the Hornets. Sorry pelicans pelicans There's four boxes left here Got All right guys we got a couple of prism four boxers with teams on sale coming up Spectra and illusions is down to ten four box mixer for football. There's just what three teams left now or I'm a sorry for teams left for I'm a they're on sale though It's Falcons Jets Titans and Washington Falcons Jets Titans Washington, and then we have six series later on as well Another spot just came in for prism Or no, yeah Shaggill this Alexander thunder groove rookie Caleb Houston magic Mark Williams fractal vortex James Hardin for the Sixers I'm not sure Peeley. I don't remember any I don't remember any Celtics or Hornets hits yet You honest supernova astro Bamba to bio the heat Like I think you can do either or Neither frozen our rookie chat Holmgren for the thunder Sunburst rookie Hawkes Tyrese Maxie number 55 out of 75. Sorry Tyrese Martin reading chat and Read this at the same time. I Have a zero illegal. I don't have that kind of money Shockwave J and IV we got astro Darius Garland O'Shaig Bajie groove Desmond Bain for the Grizzlies Yeah, pop starts in the freezer Rookie Revolution AJ Griffin rookie fractal Tyrese and Rockets They'll have them hot or cold not room temp though Jeremy Sohan astro rookie Ejila Dell for the pelicans So if I have to choose either room temp or toast it, it's toasted. I'll say that That's fine. I mean if there's a pop-tar and I really want a pop-tar. I'll just eat it Say what we prefer. Yeah, nothing wrong with room time rookie groove. Josh may not for the T-wolves I've been a room temp before I see them room temp all the time and like Something you grab on your way out the door really Shade on sharp rookie Blazers fractal vortex Damie Lillard Blazers Exactly exactly Debuck vortex. You've got astro Lillard Blazers. She drank coca-cola for breakfast sounds like sounds like Like Donnie drinking Celsius Dylan Terry got Christian Brown rookie impact for the Nuggets numbered 137 of 149 Shockwave Tatum astro koaland and Clippers Jalen Williams groove Kelden Johnson spurs Rookie Revolution Dice Daniels rookie fractal Patrick Baldwin junior Warriors Kind of left in junior. We got rookie Astro Kennedy Chandler for the Grizzlies Yeah, I don't follow any examples. I like one meal a day now Jabari spent junior rookie Rockets rookie Sunburst Jabari Walker 60 is 75 for the Blazers Lift off LeBron James Lakers rookie groove Matt Scottie Pippin junior rookie for the Lakers Walker Kessler rookie rookie astro Josh may not T-wolves Vortex Zion astro Davia Mitchell Kings rookie Otto Pacers Benedict Matherin There we go Pacers Tyrese Martin impact Chris Haps for Zingas Wizards numbered 80 of 149 Jalen Williams, rookie Revolution for the Thunder astro Giddy Thunder Yeah, they all knew people growing up that like I had friends I would ring like Mount Dew in the morning groove John Morant for the Grizzlies Probably have it someone got shockwave LeBron James fractal Scottie Pippin junior rookie for the for the Lakers Bajie rookie you've got Jalen Brunson Nick's impact to 149 Vortex Paloban caro magic with an astro of Jordan pool for the Warriors So on group Jordan Clarkson jazz. I mean drinking soda is never a good choice Supernova LeBron James astro Luka Donchich Mavericks Theoretically it isn't your name are an astro Jaden Hardy rookie for the Mavericks Vortex Trey young fractal Desuma bulls Ricky Keegan Murray with a fractal vortex Benedict Matherin Pacers rookie Shockwave Durant's astro John Morant for the Grizzlies and rookie Otto bulls Daylan Terry. Okay, that will do it. Give me a sec everybody. We'll do a recap Three solid case Big parallels Well, yeah, well, I guess if you drink your coffee like that. Yeah, there's not a whole lot a lot of difference Yeah, I was not guaranteed Shane. They're about one every One every two boxes on average. So usually you get eight per master case for per case We did get eight so all of our numbered cards We had Jalen Brunson Christoph's for zingas Jabari Walker Christian Brown Terry smarten jaren Jackson jr. Demonte Sabonis Christian wood Kendall Brown Bojan Bogdanovich John Morant Damian Lillard Demona Sabonis Usman a jang Michael Porter jr. Wussidia Bate Kyle kuzma James Harden Julius Randall autos of Daylan Terry Matherin Sexed into 100 for the jazz Lenny Wilkins carol Anthony Towns Malachi Brannum Evan Mobley on card and CJ McCollum We had a galactic vortex Kawhi Leonard Clippers Primetime performers short print insert Chet Holmgren for the thunder and Rookie Sunburst Palo Ben caro magic Was number 18 out of 75 nice card. Thanks again everybody pre-soled case there. We're on to prism