Welcome everyone to our Tech Tuesday webinar. Today, we're going to be talking about digital transformation. But we're going to take a slightly different perspective on things. I think you'll find people talk a lot about modernizing your apps and more recent times, it's been about the collaboration and maybe the enterprise. But we're going to talk about AppSec and why, when you're considering going through a digital transformation that you should be considering making updates to your application security platform or strategy. Just to introduce ourselves a little bit, my name is Andrew Horrigan. I'm a technical PMM at Deep Factor. I've been here for almost six months now, it's rounding up, but been here for a little bit, learning all about AppSec and helping spread the message around Deep Factor. I'm joined today by Karen. Karen, I'll let you introduce yourself. Hey guys, I'm Karen Cummings. I'm the founder CEO of Deep Factor. Addicted entrepreneur, lots of experience in the Cloud Native and other areas I was at to school before and the bug bit me and I started another company. This is an area that we feel is going through a lot of changes. Organizations are creating Cloud Native containerized applications, Kubernetes applications, etc. It's important to identify security just in these applications during the course of development as opposed to late in the game when the apps get rolled out into production. Hence a modern take on an application security platform. Yeah, absolutely. Just a little bit about Deep Factor. We were founded in 2019. We've got people from all over the technical sphere from infrastructure and Cloud Native guys like myself, all the way to security experts from QALIS and Citrix, etc. We've got a good well-rounded team in our mission ultimately is to help developers ship secure and compliant applications. If we could deliver one thing, that's what we want to deliver. Moving forward a little bit, I want to give Kieran an opportunity to talk a little bit about the apps that challenges and trends that we're seeing shape up the environment here. Yeah. As many of you guys probably are following or have been following the space quite a bit, which is probably what led you to attend this webinar, digital transformation has been happening for the last few years now. Ever since Cloud Native applications started becoming the way you build modern applications. That has resulted in, there's a couple of, we're sitting in the intersection of a few interesting trends. Number one is every organization when they're building new applications, they're looking to now think about, should I build a new application using containers? In fact, that's become the norm for any high-scale application with Kubernetes or containers or at the minimum maybe some serverless functions being thrown there. So application modernization, if you're starting application building from scratch, then Cloud Native icing your application seems like the way to go these days. But if you're a larger organization that already has a bunch of applications in place and you want to try to transform those applications and modernize those applications and make them Cloud Native, then that's another threat of initiatives that is happening in pretty much every large company that we've been talking to. So basically apps are getting more granular, they're moving at a faster pace because you want to ship them faster, you're putting them through your DevOps pipeline. At the same time, the number of security-related breaches, both in terms of the size of breach as well as the number of breaches have increased quite rapidly over the last few years, and that number we only see is going to continue to grow because the number of the applications are increasing quite heavily. So if you think about the concerns around security, you see stats from Stack Rocks adoption survey and some of the Red Hat state of Kubernetes security reports, they indicate that pretty much every Kubernetes deployment, 94 percent of Kubernetes deployments have experienced security incidents, or they've experienced security-related delays where issues were caught, but they were caught late in the game, which resulted in releases getting delayed because somebody had to come back in, the engineering team had to context-switch and fix those security issues, etc. Several of those issues are obsturated, but there's also several of those issues that are application or development-related. If it's an obsturated issue, the fix is to protect your perimeter or get your cloud security posture configured right. But if it's the application, then the best way is to make sure that you create a secure application to begin with. I was just attending another talk with somebody from Zscaler and they basically were saying, do you want to be a coconut or an avocado? Coconut being secure outside, but soft inside without much security inside. That's important because you still need to have some kind of perimeter protection, etc. However, it's becoming more and more important these days as apps become more granular and there's a lot more e-switch traffic to be for your organization security strategy to be an avocado, which is make sure that your application is secure in the middle because once your app is secure, then the rest of the things start mattering a little less. Some other interesting stats here is in terms of the number of developers versus security professionals out there. The number today is 26 million. I think today we have about 26 million developers and that number is supposed to get to 45 million by 2030 and the mind-blowing stat that I heard is that there's going to be 500 million cloud native applications by 2023. Come to think of it, cloud native and Kubernetes just got started five, six years ago. So this is like a massive amount of growth and proliferation in terms of number of applications being designed with cloud native in mind. At the same time, if you look at the number of security related people, the talent pool is very small and look at three and a half million plus unfulfilled cybersecurity jobs. So it's important to make sure that you automate a lot of these cybersecurity functions during the course of your dev or CI pipeline or in production so that you can make sure that you create secure applications to begin with. So what is driving? Now that we've taken a look at the macro landscape, let's dig a little bit deeper. What is driving app sec modernization? We talked about app modernization, meaning containers and Kubernetes and server less and all of these things that are creating that are that are enabling people to create secure applications. Now, how does that affect application security? Application security in this case being defined as the ability to identify all of your security and compliance risks during the course of your development. We've talked to over a hundred enterprises over the course of the last year, year and a half, and we've broken it down into five themes where these companies kind of come to us and say, this is the problem we're trying to solve and therefore we need a better app sec solution. Number one of that is app modernization, where somebody is creating an application or transitioning from a monolithic application into Kubernetes or some kind of microservices based application and they want an app sec platform that understands Kubernetes that is designed for Kubernetes. So they view this as an opportunity to say, now that I'm modernizing my application, I don't want to take all of the baggage of the older app sec tooling into this new world because I had put together a hot spot of five different app sec tools as part of my legacy application. I don't want to carry the same things forward. Is there a cloud native centric application security solution? Number two is dev sec ops adoption. I want to make sure that I add security early on in my CICP pipeline so that we can identify the risks in the application before they're widely deployed into production or even cannery rolled out into a smaller group into your production. The third one is around alert fatigue that results in release velocity that affects release velocity. It's my current app sec tools are giving me too many alerts and I don't know which ones of those I need to start fixing first because of that either we're fixing too many things which is affecting release velocity or my developers are just losing interest in work or the confidence in that tool. The fourth one we see is you know I have tools tool fatigue when there's there's just too many tools to use and all of them are important because security at the end of the day is a layers game but you know I don't I as an organization don't have the people or the budget in my organization to kind of put a SAS a software composition analysis a container image scanning a Dast and an IS so there's just too many tools out there like how do you how do you simplify this and lastly is there you know given the the importance of of observing an application at runtime especially for cloud native applications because imagine your app which was basically one thing was broken down into like maybe you know 10 plus containers now and all of these microservices are being orchestrated up and down in in your you know Kubernetes or other environments and you need visibility the true security posture and risk of your application cannot just be assessed by scanning your code or scanning your artifact of containers but you have to actually observe what your application is doing at runtime because maybe it has some it's passing some clear text secrets and you know at runtime or maybe there's an environment variable that has a key in it lots of interesting things that show up only at runtime that you cannot just get by looking at your your static code or or even your container image scanning so these are the five reasons why people reach out to us and why there's a need to rethink app sec and create a next generation application security platform you know and and that's basically the course of this discussion today Yep and and one of the things that we like to do when we give this presentation is kind of ask the audience you know where or you know what are the driving factors for them you know obviously I think for each of you there's going to be an individual reason why this you know this webinar was of interest to you and so we're you know just what do you a quick poll I think Virginia is going to go ahead and launch that in the background so you should see a pop up but you know let's just take a quick second to answer this and just to you know understand where you guys are coming from are you you know like Karen said are you looking to modernize your application and you realize you know maybe this is the right opportunity to reevaluate my app sec tooling are you concerned about release velocity and being able to allow developers to secure more quickly but also ship at the same rate you know just take a quick second to off to to make a selection I believe you can select more than one so I'm just curious to see you know what what you guys are saying and Virginia I know you're you're on mute and off camera but I think you'll see the results if you could maybe you know let one of us know what what seems to be trending more popular than the others that would be absolutely so as of right now it looks like 75% app app sec modern application modernization with a second runner up being unified app sec great thank you and that that kind of drives with I think the conversations that we have right it's it's your you're going through this modernization you're realizing that you're kind of toe in all the stuff behind you a lot of legacy maybe more traditional ways of doing app sec and you realize this is an opportunity to maybe reevaluate it and then obviously while you're reevaluating I think a lot of vendors in this space have have kind of started to consolidate and unify and and really bring together a lot of legacy app sec platform so you can kind of get that best of breed approach and so that kind of jives I don't care if you want to add anything else but that that kind of makes sense I think from our perspective yeah totally yes I mean people are frustrated with with a lot of tools that they have to put together because they want a good security comprehensive coverage at the same time without having to use too many tools number two is a tool that understands your modern application so I think I'm kind of pleased to see that both those are the two number one number two exactly exactly so before we get into you know the next generation of of app sec tools so to speak what what we wanted to talk about a little bit was just kind of define the landscape as it stands today and so you know these categories aren't you know they're not the categories right if you go look at a Gartner MQ they're gonna maybe kind of realign it a little bit differently but you know we kind of want to paint a picture of the current app sec landscape and how we view you know where these tools kind of fit best and and this is kind of like a little bit of a 101 you know 202 type level for people who maybe are a little bit new to app sec in general so on the left hand side you've got your your static code scanners so these are things that are going to be looking at at your code as you're writing them you know one of the more recently announced sort of capabilities is is infrastructure's code the rise of Terraform and Pulumi have given the you know a rise to a need to secure your your infrastructure code you know assess the static application security testers can be looking at the code that you write right so you're going to define best practices for your developers for your organization you're going to ensure that code is written to the sort of spec and quality and sort of a framework that that you expect within your organization the other type of static code or static scanners that we have out there are SCA so software composition analysis and container image scanning so an SCA is going to be like a like a sneak it's going to be observing or not rather not observing scanning your container images in your artifact repository this is something that like a JFrog might do as well and it's going to kind of help you understand all the potential vulnerabilities that that specific image might be susceptible to right so it's going to do some correlation some of them use their own you know their own databases some of them use like the the publicly available in this CVEs right but the idea here is to understand as you start to pull in packages and dependencies which of those are have pre existing disclosed CVEs same thing with container image scanning so the idea here is that we're going to give you not only the vulnerabilities but kind of a readout of all your dependencies and all the different packages that make up your your application that will be deployed in the dynamic category we've got DAST so DAST is dynamic application security testing there's a couple different DAST school DAST tools out in the market you know we at defector really like a WASC ZAP but the idea here is that you are scanning all the APIs for your application and you're checking things like the OWASP top 10 so cross-site scripting SQL injections buffer overloads etc those are all things that we're going to be scanning with using a DAST and then finally we've got the runtime category so what you see in runtime is interactive AST so you'll see I asked you'll hear people say I asked a lot this is a fairly older I'll say within the last two decades sort of technology it uses an agent most most commonly to observe the application as it's actually running so the agents generally are a little bit some developers we call them intrusive because you do have to actually compile them into your code but they understand the language intimately right so you might have a Java agent that's going to actually understand all the different calls and packages loads that your Java library is doing container security scanning or sorry container security as a new category that's also in runtime you'll often find these in production so you can think of like an aqua or a twist lock right these are going to be side cars that sit right next to your application in runtime and they're going to be observing sort of the network traffic that's going in and out the cluster in between the pods and it might do some sort of security analysis on that traffic it might be able to isolate the pod it might be able to give you insights and so what the what the application is doing and when we talk to customers about the adoption of these various tools what we have found is that there's four very clear stages when it comes to sort of DevSecOps maturity so as you start to move left as you start to shift the responsibility security from the app sec you know silo the app sec be you with the organization and you start to move it onto the developers we're finding that various different enterprises are in different stages so the first app sec stage unfortunately is actually a stage we have had conversations I went to I went to lunch with a nonprofit in a nonprofit doesn't do any app sec right so they just release their code they do some functionality testing and they release it into the wild they're very early stage they've only got a couple of employees so they don't really have the resources of the bandwidth to do app sec right so they haven't implemented any tools more often than not what we find so a lot of customers aren't a sort of like reactive app sec stage where they are not really doing anything in the pipeline they're not really securing their apps there but what they are doing is once you know the app goes into production maybe once every month or once every quarter they do some sort of pen test right they they contract out to our organization that specializes in app sec and they go ahead and they do some you know some testing there now obviously the issue here is if you don't catch any of the security sort of you know risks in the application until you've already gotten a prod well so can the bad actors right the bad actors have an opportunity to interface with your app just as much as the pen tester does the other stage that we do see a lot of the larger enterprises for sure and are that that sort of proactive app sec so they realize that you can't just wait once a quarter to go ahead and do you know a pen test but what you can do is every time I build an image I'm going to do a container image scan every single time I you know maybe once a quarter once a month once a release I'm going to do a dash scan to check my API security right so it's it's proactive at a minimum it's I'm not going to wait until something goes wrong I'm not going to not do anything but I'm going to go ahead and do some of the stacks scannings I might have like a container security product in play so I might go into production and you know the ops team that the the SREs the DevOps team who are actually in charge of the environment they might actually be doing some of the app sec responsive abilities but you know not it's not really in the developer world yet so the stage three is kind of the very beginning stage where you think okay in order for me to actually mitigate this stuff getting further into the pipeline why don't I you know have my developers start securing and observing the application before it gets put into production and so that's what we call called cloud native app sex and the idea here is that your developers are you know as they're writing their code they're doing their functionality tests they're checking for security risks they're checking for runtime behavior they're doing their scans all as part of that development process so that you don't necessarily need to go through stages one two and three in order to secure your application and what we kind of advocate to customers is don't think that you have to go stage one stage two stage three stage four you know when I was having that conversation with the with a nonprofit you know I'm not going to advise that they slowly ramp up their app set capabilities I'm gonna say like no you should be looking at tools are going to get you immediately from stage one all the way to stage four right without having to go through those sort of baby steps to get into a you know a more secure posture so with that being said what I wanted to do again is ask a second poll and just kind of get a feel in a room for where people are in their app sec journey you know in their dev sec adoption journey you know are you someone who maybe doesn't take app sec very seriously today or are you doing some out of band tests do you have static scanners you know are you more in a stage three sort of category or do you really feel like you've gone the full mile and you're doing cloud native app sec and you've you've got dev sec ops you know ready to go so we'll take a couple seconds there and Virginia I'll ask you to speak up once again once once you get some good responses or stage one is definitely in the lead at 42 percent but stage three is coming up as a close second runner up so yeah stage one and stage three seem to be the most popular ones huh I think that's we've done this a couple of times I really feel like we usually get stage two and three stage one is surprising I want to say shame but that would be a little too judgmental for this audience but so thank you thank you Virginia so you know Karen I know you wanted to talk a little bit now about what is the ideal app sec tool yeah cool so you know we've established the fact you know over the last you know 20 minutes of this conversation we've we've talked about what the need for cloud native applications and a new breed of app sec tooling now let's talk about what is that next gen app sec tool looks like what is an ideal next gen app sec tool and I think given the context of cloud native applications the number one important thing is that this app sec tool should be easy to insert into your cloud native workloads and it should observe both your running containers as well as your static container artifacts so a cloud native first application security tool that is easy to drop into your cool environments or other environments it could even be like managed Kubernetes like it could be AWS Fargate or even your your own renter clusters for example or and it should be able to watch both the static aspect of your container images as well as the runtime aspect of your container images very easy number two is the number of alerts that you currently see with some of these legacy tools should be drastically reduced in order for your developers to take the output of these tools seriously and one of the important ways to reduce that is by correlating some of your findings with what your application is actually doing at runtime for example an example is if you if your application has you know a hundred vulnerable components that have CDs in them based on your software composition analysis or container image scan findings can you look at which of those are actually used by your application at runtime and by looking at that you know you can reduce the number of alerts because you only focus on the libraries of the dependencies that have been loaded and used by your application therefore your hundred might come down to 25 the other thing is lack of runtime visibility today is a problem and a an apps like platform that that understands not just the static artifact scanning aspect but also runtime like I talked about the third one is the unified part you know which you guys chosen the poll is one of the problems which is you know I don't want to be using too many tools this one you know or a handful of apps like tools should be very easy to kind of drop into my environment and it should get the various security insights in a simple pane of glass or integrated even better as part of my CI pipeline like if I'm using Jenkins you know I should just be able to go you know do my standard bills and at the end of the build it should show me you know all of the things that matter with respect to a bit of materials and the changes that have happened across releases all of the things that matter with respect to security posture of the application both static and runtime and compliance insights and if that can all happen as part of my CI pipeline that would be awesome so that would be in you know that is the definition of what a next generation ideal app sector should look like and there is an important aspect that of technology that is emerged over the last few years which is observability and that is that is basically enabled us to observe running cloud native applications very deeply so you know there are technologies like EVPF there's sidecar technologies there's also you know library loading technologies that allow you to get deep visibility into your application behavior and I want to make sure that we spend one slide talking about what observability is and how it is involved and why it is relevant to app sec and why it is important it's an important fabric of creating the next generation app sec platform so what is observability observability is the method of evaluating running applications so that you can reach meaningful conclusions about their health or performance or in our case application security so far all of these the first generation of observability products like honeycomb elastic and all of that they've focused quite a bit on using observability for logs metrics tracing like performance related insights but observability is just beginning to be used now to get application security insights and you know tools like aqua or sysdig or de-factor you know these are these are some of the companies that are using observability to observe application behavior and then correlate that into security related behavior so what is it why is it important for app sec because it allows you to watch an application or a cloud native application at runtime and then coordinate or correlate the behavior of the application with what is acceptable what is not like a simple example could be your developer brought in some third party code they did not know that the third party code was making an outbound connection to a certain geography that you didn't want but let's just for example say let's say Antarctica like it was making an outbound connection to Antarctica and you did not know and they did not know either because they thought it was a third party component that was already that didn't show any CVEs in the scan so many times runtime behaviors that bypass your scan your CVE list because it's just you know the it was not known vulnerability it's just bad runtime behavior those are things that I think need to be caught and there's several examples of what bad runtime behavior could be including not just network activity that I just gave an example of but it could be files that are being touched in slash 10 for libraries being loaded from some from unwanted folder structures in your in your operating system so on and so forth so risky behaviors can happen both in your code as well as you in your dependencies code like if your developers are bringing in third party OSS components into your code and they could be having risky behaviors and it's runtime observability is important for apps to not just to identify these risky behaviors runtime but also to correlate with the findings of your static scanners so that you can prioritize which of the findings of the static scanners are actually being observed by your application at runtime so that you can figure out which ones to fix fast so it'll help you reduce the alert volume as well as increased coverage of your application security faster now why is observability a must have for cloud native applications because cloud native applications increase the order of complexity quite a bit come to think of it the moment you've granularized your application and divided that into a bunch of microservices a lot of these microservices in many organizations and managed by different teams so they may have different base operating system images one could be using Alpine one could be using Ubuntu and Red Hat and so on and so forth the not only the base images but the languages used by these application for these each of these microservices might be different one could be written in Golang one could be written in Java or no JS so there's a larger surface area of risk and therefore you need to make sure that you observe each of these running containers while they're in action as opposed to just scanning your container image repository so just the quick scan of your reposes insufficient you need to make sure that you look at it at runtime so now that we've established what observability is and why it's an emerging technology trend let's talk about what observability can do to the list of APSEC findings that Andrew laid out before so this was a slide that Andrew laid out that basically says these are the tools that exist in the market today and there's probably one tool for each of these you know boxes that you might be using in your organization now the question is obviously we don't want to use all of that we want to make sure that we have a unified view and what is that unifies you know some of these things it's observability is a fantastic candidate to unify that so if you overly observability on top of these tools whether that's whether you use multiple tools or whether you use one tool like a deep factor that that incorporates observability along with some of these other modules so that you get that unified experience it's it's a way to augment both runtime dynamic and static finding so here's how here's what it can do for you on the runtime side observability will give you visibility into your application's behavior by looking inside the app while it is running there's several ways to incorporate observability if you use you know tools like you know sysdig it's an agent that you put on the host if you use a tool like aqua it's a sidecar that you install in your kubernetes environment if you use a tool like deep factor it's a library that you drop into using a kubernetes plugin so all of them have their own place and pluses and minuses and on the operator side tools like sysdig and aqua are probably the better fit if you are using production rollouts and you want your goal is to secure your production environment but on the development side tools like deepfactor are the better fit because you need your goal is to identify runtime behavior that's happening in every thread every process every container in every pod of your kubernetes deployment for example so you need something that watches each of these processes as opposed to a sidecar that is observing it from the outside so observability depending on how it's delivered can give you great visibility into runtime of the application but also make sure that you pick a tool that that condenses all of these insights into a small number of actionable items as opposed to just overwhelming you with a ton of telemetry because that's not what you what you want in is you don't want yet another tool that spits out that ton of alerts you want a tool that reduces and detects anomalies based on these alerts and reduces them into a handful of actionable items the second advantage that you get a second thing that a good observability platform can do for you is to augment your DAST a lot of the times DAST is kind of like a standalone thing that you run you know once a week or once a month or sometimes and mostly in pre prod sometimes even in prod to poke the application from the outside and then detect vulnerabilities like the OWASP top 10 type vulnerabilities and examples of DAST tools are OWASP ZAP which is what we use integrated entity factor but we also see a lot of the you know Burp Suite and Acunetics and Neuralegion and Stackhawk and all of these companies that are that that provide DAST tools the beauty of combining observability with DAST in fact I just gave a talk on Friday at the OWASP OWASP conference on specifically that topic is how do you enrich your DAST by combining it with observability using just to shorten it a bit the by by using the ability to observe an app from the inside you actually can get to detect things like hey my app was listening on web services XYZ and you can use that information to pass back along to your ZAP scanner so that your your DAST scanner can can therefore scan these new interfaces you can also identify which changes have happened between releases so that you know your DAST scanner is not now going and scanning every endpoint or crawling every API of your application and scanning it by going through your swagger document only scans the the list of changes which reduces the scan times for for DAST which is one of the biggest pain points that ZAP scans or DAST scans in general take a lot of time so lots of benefits by combining observability with a DAST product now let's come all the way to the left which is what can observability do in the context of your software composition analysis or your artifact scanners again I may have touched upon two slides ago which is the ability to prioritize your insights by that your SCA tools or your container and the scanning tools provide you by correlating it with runtime context is something that observability can do so in a nutshell there's so many different tools out there a good way to think about it is unify them but you can't just unification is not just throwing all these tools into one pane of glass it is actually combining it with a technology such as observability to give you deep insights and help you augment your existing tooling and reduce the number of things that your developers have to fix at the end of the day so we talked about the evolution of appsec apps into cloud native work cloud native workloads we talked about the that resulting in a the need for a modern appsec platform but let's take a step back and in a kind of unvendor related way talk about what is the right thing to do when you're planning for your appsec strategy so let's start with the first thing that you know we typically recommend you know any organization to do that's a marking upon this journey of hey I want to put appsec in place is understand your business driver you know is the need for my for my appsec journey a digital transformation is it application modernization or do I just want something in the CI pipeline or am I just trying to get some compliance boxes checked you know with Biden's executive order around the materials as well and so forth once you understand that then you understand you know what who is going to be using the tool I mean do we have resources a dedicated appsec team that is going to be doing this task in which case they will be doing the tool selection and embedding into the CI pipeline and then the developers are going to be consuming it or do I it doesn't have to be done as part of the engineering organization if so identify a resource some you know essentially you need a resource to put the tool in place you need a process and a resource for that for the alerts to be regularly triaged because without an understanding of the proper process that program is going to not be successful so you want to make sure that you give some thought to it then you figure out what you're before you pick the right tool you know understand what your technology requirements are if your app is a monolithic application that is written in .net you know you may want to use an older kind of I asked to a couple with maybe some DAST and maybe some code scanners but if you're building a modern cloud native application then consider a cloud native application security tool if you're building a mobile application then you need some you know a mobile you know security tools like Massacure and stuff like that are good for that and once you've done that then you understand you know what budgets and timelines you know make sense for you the beautiful thing about picking tools that offer more than one functionality into one unified experience is that you save a lot on money as well as the time it takes to set up these tools so pay attention to that as part of your budget and then make sure that you dedicate a certain amount of time there are certain tools that take a long time to to put in place it's not just the aspect of making the tool and it's it's the aspect of getting your engineering team to kind of work with your security person or the APSEC team to get the the triaging process kind of nail down completely so that takes a little bit of time to do maybe a trial trial run with a couple of your sprints and then you know get that incorporated in the long term as well. Great great great summary there Karen so so you know just as we go ahead and close out this webinar you know I wanted to bring you guys attention to some resources that you can follow up with if you want to learn a little bit more about observability and DevSec DevSec maturity we do have a couple of blogs that we've written I think Karen wrote maybe both of these actually so so they're a couple of good blogs about what is observability a little bit more on why it matters for APSEC and then a whole another blog on DevSec Ops maturity and what sort of decision points and sort of things that enterprises need to consider as they sort of make their way through that DevSec Ops maturity you know staged step ladder that we talked about earlier we also you know if you're interested in learning more about deep factor we do have some some case studies that have been done by some of our customers so feel free to visit our YouTube page and watch that it's pretty pretty helpful if anything not just for the deep factor angle it's it's actually kind of cool to see peers that are going through the same sort of challenges that you might be going through and and and their thought process to why they might have evaluated you know an alternative APSEC tool or or decided to do something versus you know another decision so that's always a great video to watch and then finally if you do want to see more about deep factor and you would like to see a demo please feel free to to reach out to us and and we would love to get on a call with you and and and kind of walk you through through the product so you know unless unless Karen you have anything else to add or Virginia we missed anything I think we're we're kind of at the top of the hour here and we maybe have one time for one question so this this seems like a good one so Karen could you touch a little bit more on on why existing APSEC tools might not work for a cloud native development I know we kind of talked about a little bit but it seems there's two questions in here that seems to be indicating like well I have all these tools I'm confused you know why I need another one yeah yeah no so the question is not needing another one the question is as you move from your traditional applications into this new world of cloud native now is actually you know it's a it's a problem to be solved but it's actually an opportunity to kind of rethink your tool set and so it's a good time for you to reimagine what your APSEC tools that should look like for this new world so instead of taking you have two choices I mean we have the choice number one is to take the existing APSEC tools that we've been using all along it's like four or five different tools and put them all in this new world or choice two is you know re you know leapfrog it and go pick a pick a tool that understands cloud native that is designed to understand both the runtime aspects of your containers as well as your static aspects of your containers therefore you can kill two birds with one shot yeah absolutely you know that was I think it's a great way to end I think I was ultimately what we were trying to advocate for when we started this presentation an hour ago so thank you Karen for your time thank you Virginia for helping facilitate and thank you to all of you for tuning in and listening to to us talk a little bit about abstract modernization


Have you ever? Hey, this sounds strange. Snails with garlic. Have you ever eaten snails? Yes, I have. I had them here just last week. Did you like them? Yes, I did. They were delicious. Why don't you try some? No, I don't think so.  Yes, I'll have a small order of the snails, please. And you, sir? I think I'll have the fried brains. Fried brains? I've never heard of that. It sounds scary.


Hey, welcome back to the channel. So in this video, I'm gonna let you steal my weekly email marketing schedule. So whether you're writing for yourself or you're writing for a client, you can use this schedule, you can model it for yourself or your business or a client's business, and you'll never have to guess what theme or topic to write about each day. So I've been using this for a little over a year now, this schedule that I'm about to show you, and it just makes my life a lot easier. I never have to think about what to write about, and I know exactly what the theme is gonna be for each day. So I'm gonna hop into my computer in a second, but before we do, make sure you hit the subscribe button and hit the bell icon so you never miss any of my future videos. Doing that lets me know that you're enjoying the content, helps to show it to other people who can benefit. And it also motivates me to continue creating content because this does take a bit of time to do. So make sure you hit the subscribe button, hit the bell icon if you're enjoying the content so you don't miss any future updates. And with that said, let's hop over to my computer. I'm just gonna walk this over with you very casually, and you can steal this exact schedule if you want for yourself as well. So let's hop into my computer right now. Okay, so I have my schedule up here on the screen, and I'm just gonna walk you through each of these email types and what's being done, and I'm just gonna show you last week's emails so you can see exactly how this rolled out on my own email list. If you guys wanna join my email list as well, just go to email rainmaker.com. You can join my free Facebook group. There's gonna be a question to enter your email address for a free report, and you'll be able to see these emails for yourself as soon as you join the list. So let's walk through each of these days right now, right? So I send out an email usually Monday through Saturday. If I'm doing a promotion, I'll send out an email once or twice a day, and I do those once per month. I'll talk about what that is as well. But let's just walk through each of these emails from last week so you can see what these look like. So on Mondays, Mondays and Wednesdays, I am creating a YouTube video for my channel as you're watching right now. And on Mondays and Wednesdays, it's very easy for me to write an email because all I'm doing is linking to the video. So here's an example here, right? And the way that I do this is I just build a little bit of context or some excitement, right? I get them pumped up about what they're gonna learn. So this is the 100K challenge where I wanna help Jackie pay off for her student loans from pharmacy school. And I talk about how I'm gonna do it with new income streams. So I'm building curiosity and building excitement. Ooh, what is this challenge about? And I'm gonna click to this video and this goes to my YouTube channel. And it's not gonna do that here because I'm in active campaign. But that's all I'm doing on Mondays and Wednesdays is I'm just writing a bit, a short introduction of why they should watch my YouTube video that I'm linking to it. There's no direct offer in here. But I do wanna show you this at the bottom. I learned this from a guy named Dean Jackson. I think he calls it a super signature. And it's kind of like a choose your own journey thing, right? So you're gonna notice here, I'm not actually making an offer. The offer is to click on this video. But you can see down here, if they want to follow me on Twitter or they wanna join my group or they wanna get one of my paid offerings here, they can do that. So it's like a choose your own journey based on where they're at in their journey. So this is the Monday email, right? And this is the link into the YouTube video. So that's day one, real simple and short, not much to that. Now on Tuesdays, I don't have a YouTube video. So I'm writing about whatever I'm feeling at the time and I have a note doc on my iPhone that helps me to plan this out. But it could be a story, an opinion on something, a lesson, an insight, or I could be doing a promotion at the time or getting warmed up for a promotion. So here is an example right here. Let me X this out. This is about, I was testing an offer, a potential offer I'm rolling out for Facebook groups. And I did that by writing a bit of a story here. So I talked about one of my mentors who pulled out 730K in coaching sales from a small Facebook group with 634 members. So I'm building up the excitement.  And then I talked about my Facebook group, email marketing rain makers and the results I've generated from that. So I talk about that and how it's worked over the last year. And at the end, I say, would you like to join us? I'm gonna be helping people do the same thing with their Facebook groups, right? So this is a bit of an offer and a story mix, but I'm usually writing about one of these things here, right? Like a story, an opinion on something. You know, when politics were going on, the whole election thing, I had some opinion emails that went out around that. If I learned a really important lesson or something happens in my life, right? Like when I got COVID, I wrote about that. So whatever's going on at the time and whatever I'm feeling, that's what I write about on Tuesdays. Now Wednesdays is the same thing as Monday. I go here to this one here. You can see again, LinkedIn messaging strategy I'm using to get clients. So I'm building excitement.  Hey, I just jumped on LinkedIn again after 18 months. I optimized my LinkedIn profile. Now I'm reaching out to people to get them as clients. Here's the messaging strategy that I'm using, okay? So I get them excited. I then tell them, hey, don't copy and paste, but it's gonna work for you. It's gonna work for you if you use this basic framework of what I talked about in this video. And it links to the YouTube video here. So very similar to the Monday email. So that is Wednesday, Thursday, same thing. Whatever I'm feeling at the time, story, opinion, lesson, insight, or promo. My email here from last Thursday was about an OnlyFans agency owner who made internet pimps as way to 100K a month. So I talked about a two-hour conversation I had with this guy who runs an OnlyFans agency that brought it to 100K a month in four months. And I had a bit of a Q and A here of questions that I was asking him that gave some insight on what he was doing with his agency. So this is a bit of a story email or like a, I guess you can call it a story email and a lessons email from talking to this guy and learning more about his business model. And at the end here, I segue into my own product, right? So I link to my product here, the Super Fast Sales Email Challenge. By the way, if you guys wanna check this out, there's a link in the description below. And the way that I segmented to this is I said, this guy that I talked to, he uses a lot of email to help his models make money on OnlyFans. So I talk about this is a money-making skill. If he were to stop doing OnlyFans and he were to just move into another business, he would still crush it because he has the skill of writing emails and running paid advertising. So I talk about that in this email here, right? So it's a bit of a story and a lessons fusion with a promotion here or a link to a direct offer. Okay, so that is Thursday. So Monday through Thursday, I'm kinda just alternating between YouTube video, story, opinion lesson, insight promo, and another YouTube video and the same thing on Thursday. Friday is where it gets a little different. So Friday, what I do, and I love this, it's been very, it's working very well for as long as I've done it. Every Friday, I send out this newsletter called Friday Fire. And what this does is it helps to, it does a few things. It helps to redistribute any content that my audience might have missed, right? They might have missed the YouTube video and maybe they see this newsletter and they're like, oh shoot, I gotta watch this. I haven't watched this yet. So it helps to get more views and reach out of my existing content. And it also helps to share wins from my students and customers in my different paid offering. So it gets them excited to want to join if they didn't already join and get one of my products. And it also helps to build the bond and relationship with me and the people on my list, right? So I share thoughts and I also share an intro story here, right? Of something I learned during the week. So I have a separate video specifically on this newsletter and how to create a newsletter for yourself. I'm gonna link to that below so you can watch that if you want. But the basic format that I'm using right now is I start this off with a story or a lesson or learning from the week, right? So at this time I was talking about the only fans agency owner guy and how attention is paying attention equals money. And then I go into my content from the week that they might have missed. I go into wins from the week for my customers. And then I go into two thoughts from the week. And then I cap it off with, hey, what's your biggest growth challenge? And I tell them how if they want extra help or they want to work directly with me, they can click on this link and see how I can help them. Okay, so I love this newsletter. It's been very well or very good for getting people into my offerings and showing them wins from customers and students and also helping to build a stronger bond with people. These get pretty good response rates of people just saying, hey, I didn't think about that. Or that's a pretty interesting story that you talk to a guy who runs an only fans agency, right? So this gets really good response and reply rates from people on my list and also pretty good sales. So this is my Friday fire newsletter. It's like a weekly roundup of my content and student wins and customer wins and also a promotion at the same time, right? If they want to check out all the ways I can help them, they can click on this. So that is Friday. And the last one here is Saturday. And this is called, I just recently started doing this. It's called Saturday's story time.  So I recently started doing this a couple of weeks back and this one, the recent email that I sent out is how I turned down a potential 750K a year offer because it didn't align with my values which is creative freedom, ownership and autonomy, right? They were trying to basically put me in a nine to five type of role.  I included proof from the story, like the number breakdown from the guy I was talking to. And I talked about why I turned it down and some things that I learned and things to think about in your own life, right? So this really helped to shift my beliefs. This happened actually earlier this year in April and helped to change my way of thinking actually motivated me to do better in my own business. So these are typically longer emails. They go into the actual story breakdown of all the details that happened. And again, these are things, these are stories that helped to change my behavior or completely shifted my beliefs. So there's no offer in this email but there is the super signature. So if someone wants to buy and if I remember right, this did pretty well in sales for my super fast sales email challenge after I sent this out, even though I'm not promoting it. And this is the last day of the week where I'm writing an email Saturday and this is Saturday story time here. So that is my full schedule, my weekly schedule, Monday through Saturday. So if you are selling digital products and you create a lot of content, this is a perfect schedule for you to use here. Now what I also do and what I'm in the middle of right now is I call it the lazy launch and these are 10 to 14 day campaigns where I spend a day or two and I write up a bunch of emails and I schedule it across email, my Facebook group, my YouTube channel, you guys might have seen this on my email side hustle program which is going on right now, the enrollment. And these are 10 to 14 day campaigns where I schedule everything out and they just watch sales and conversations rolling in. So these are typically for higher ticket offers. So I'll just show you an example of what this looks like. I have one going on right now for my email side hustle program. This is scheduled to go out on the fifth and the sixth. This is also scheduled across my Facebook group and my YouTube community tab. You guys might have seen these posts and I have to create a few more to last the week up to the 12th but these are all scheduled out like I usually spend a day or two writing the emails in the post and scheduling it out. And I'll just show you what one of these looks like here. This is like a testimonial style email and this one is like a problem solution style email. So what if I picked your niche for you? I talk about how I've been running this program for four months, everyone gets stuck on picking a niche. So what if I helped you pick a niche? Tell you what to offer them, what to say to get them interested and how to deliver on what you offer them. Would that help you? Would you be interested? Would that make your life easier, right? If you're interested, I have this program which can help you do that where I'm gonna help folks do that. Click here and send me the word niche in a message and I'll tell you the details of the program, okay? So that is an example of one of the emails. There's usually one to two emails going out every day and it lasts 10 to 14 days. So it can be anywhere from like 20 to 28 or 30 emails over that time period, right? But I love these lazy launches. I do it once a month. Every time I do it, it's at least five, multiple, five figures in sales.  I schedule it out. Then I just watch as the sales come in. And I did this when I had COVID earlier, like a month ago. I had no energy. I had no brain power. Luckily, I had scheduled all these emails and these posts the day before and I didn't have to worry about that. All I had to do was respond to people who had questions and just look at the messages coming in the sales coming in. So this is my entire schedule, my weekly email schedule here. And then once per month, I'm doing a lazy launch. And it doesn't really need to be more complicated than that, right? If you are creating content, you create digital products. You can use this exact schedule here. And if you want to add a promotion where you're selling a high ticket offer as well, you can do a once per month lazy launch like I do here. So that was my weekly and monthly email marketing schedule and strategy. Feel free to steal that schedule for yourself and copy after it. Do not copy my emails word for word, please. No one likes a hack, but you can copy that schedule as much as you want. Copy the themes and model after that for yourself. Now, if you want to get on my email list and see these emails and the schedule in action, all you got to do is go to emailraymaker.com. That's going to take you to my Facebook group where you can join both my Facebook group community and also my email list for free and learn more about that. But anyway, that's it for this video. Hope you guys got value out of this. Give it a like if you did. And I'll see you in the next one. Take it easy.


There's this enormous problem in the world today and that's the fact that out of 7 billion people on this planet More than a billion people have never ever switched on a light bulb So what's unique about OMC is that we're bringing electricity to places where there's no electric grid And we're doing it as an entirely commercial operation with an industrial approach We call it micro power small-scale local and renewable energy Now in our home market of India, there are over 400 million people who go about their daily lives without electricity And in the mobile industry there are about a hundred and fifty thousand towers which don't have power Now the only source of power for people and companies in these places is kerosene diesel and other dirty fuels Now we're changing that by building small-scale local micro power plants that extract energy from renewable sources mainly from the sun and then we supply this renewable energy to both Rural communities and mobile networks We're already supplying power to two of India's largest telecom companies into more than 30,000 people in just a few years We'll reach several million people Now in the process, we've also redesigned the way electricity is supplied. We've cut the cord We've cut the wire entirely and made power portable and we deliver packaged power to the doorsteps of our customers That's how we're unique Innovation is all about solving problems, ideally very large ones. To me the simplest definition of innovation is to take two Existing things and combine them and by doing so solving a problem We've taken energy and we've made it local. We've made it portable. We've taken power and we've made it small micro power We're a young company, but we still supply energy to some of India's largest telecom companies And to some of the world's poorest people So we're combining industrial power with residential power now. It's difficult to exactly define an innovator, but I think Just in way of the Sierra Club nailed it when he said the world is full of great ideas But empty of people who can make them happen Now that's a pretty good definition. An innovator is someone with a great idea That also has the belief, the tenacity and the ability to make it happen The interesting thing with OMC is that while we're a commercial company You could also look at us as a very profitable CSR initiative OMC positively affects the environment It impacts the bottom line of telecom giants as well as rural people's health and wallets We have produced carbon emissions by many thousands of tons by eliminating the need for fossil fuel We help telecom companies to operate profitably And we finally give the transformative power of reliable energy access to the people who need it the most our customers and rural communities and They actually spend less money today on OMC and energy from OMC than what they do on on dirty fuels like kerosene and diesel More than anything else what drives us is to see this amazing socio-economic transformation that energy access brings Children finally able to read at night do their homework businesses that stay open longer The hope and prosperity of all our local employees. It's very very encouraging and positive to see but it's also great business for everyone involved Now we're at a point in history where we're seeing a large-scale shift from fossil fuel to renewable energy Now we're also seeing a shift from centralized power production to smart and distributed power generation and distribution Now the future of energy is clearly Decentralized and we're very happy and fortunate to both shape and be part of the micro power movement


Hey Matt, just want to check in with you to see how the off season is going and how you are, you know, adjusting and working with Arthur Smith and as a, you know, first play time as a head coach with a play caller and Dave we're going so far. How's that going for you. It's been going well. You know, I think obviously transition requires a lot of effort and a lot of work to learn the new system to make sure that you know you're as comfortable as you possibly can be with the terminology and and you know what they expect from you there's always differences nuance between, you know, different schemes and what, you know, certain coaches, you know how they like certain things and so I've been working really hard to try and get on the same page with them and been excited that we're able to start and get out on the field this week and you know just start to get guys lined up moving around and making steps in the right direction but Damon and Arthur have been great and I'm excited about, you know, the future and hopefully winning a bunch of games. Yep. And, you know, I know others will ask about Kyle Pitts and Julio, but opting out you all voted some guys voted not to come and some are coming how y'all doing attendance wise with the guys that are deciding to work out and come during the pandemic and the, you know, phase two of the program. Yeah, I think, you know, we collectively bargain for it to be optional and voluntary a couple of years ago, and I fully support guys making whatever decision they want to make, whatever they think is best for them to get themselves ready to go and so I think, you know, attendance wise, you know, I'm fired up to be here. For me, I feel like it gives me the best, you know, opportunity to be successful but I think for all guys they've got to make whatever decisions are best for them. And, you know, that's kind of been the case throughout my entire career. To be honest with you, there's been guys that have been here there's been guys that haven't, but you trust the guys that are doing it on their own or doing a great job of getting themselves ready to go and in shape and I have a lot of, you know, belief and trust that those guys will be ready to rock and it's time to go in in July. Tori. Hey Matt happy belated birthday did you do anything fun yesterday. Thank you Tori. We took the kids out for an early dinner they got some chicken fingers and chilled out so that that was kind of it but a nice day spent with my family and you know, they're more fun when you're in your 20s you know fun having those birthdays when you're in your 20s It was a good day. Thank you. You're welcome. Getting into my actual questions now. How much did you actually know about Arthur Smith prior to getting to know him now that he's come in and you've been able to work with him now. Did you know much about him before he came in. Just just from a distance having watched what what they did in Tennessee you know I have a bunch of coaches that I have played for have worked with him and all all of them speak really highly, you know of him and who he is as a person who is you know as a football coach. You know so he comes you know highly highly recommended from from a lot of people that I trust. But you know, didn't know him personally, but but certainly you know knew him professionally and watch what they did and they had a lot of success in Tennessee did a great job there. Wanted to go back a couple weeks to the lead up of the draft at what point did you did you know that they that Cal pits was the guy did what did you have a heads up at all, or where are you kind of waiting around like the rest of us. Yeah, no that's that's those are not my calls right and not under my job description so you know I leave that to the folks upstairs and I was just excited you know found out at pick for you know that he was coming here and you know he's he's worked really hard the first couple of weeks. I really enjoyed getting to know him but I was excited that night as well. Michael rusting. Hi Matt, how are you. I'm curious about kind of with the draft. The fact that Atlanta didn't take a quarterback at all. Did that give you any sort of level of confidence or any sort of level of maybe comfort with where your future might be in Atlanta. It didn't really change my, you know, my confidence level or my approach in any way. I think that, you know, I always prepare, you know, every year as hard as I possibly can to give myself, you know, the best chance to be successful but you know I've always felt that people inside the building have a great amount of belief in me and I have a great amount of belief in myself but you know you never know how these things are going to shake out in the draft you never know what players are there what players were high on their board those kind of things you can't worry about it you know to me it's it's one of those things you just have to you know stay focused and keep your mindset on the things that are actually going to help you you know play well in the fall and that's what I try and do. Any conversations with with Arthur or Terry kind of about your status before the draft at all were any of those things discussed were you given any sort of idea. No I mean they, they, you know their job, you know as as GM as as head coach is to try and find the people that they feel are going to best help us win games and that's exactly what they said. And so, you know I had a lot of belief that I feel like I am that person that's going to help us win a lot of games. But no, no, not much more than that. Charles, just to hey thanks for doing this by the way. Just follow up on that, even even while you you believe that the leadership has confidence in you you understand I'm sure you heard that there was a lot of public debate as to what maybe those outside the team felt about the future at quarterback and whether it was time to to make plans for a different long term future. You've always been very pragmatic about things like that and accepting that certain things come with with with with age. But did that disrupt you at all did that upset you at all to hear all that debate and going on leading up to the draft. You know, not not really I think that you know in one respect you understand that if you play well for long enough these are the conversations that are going to come up. You know I understand I'm not going to play forever but I also you know have the mindset that I'm still playing really well and and have you know a lot of good football in front of me. But the most important thing to me is it comes from the belief in the building the people who are actually making decisions, the people who you know are with you day to day. And so that's kind of where I try and keep it it's harder now than ever to avoid the noise certainly easier earlier in my career just there was less of it there were less ways to get it but I found that you know if you're going to search for it.  It's going to affect you in a certain way and the same thing if you're going to search for it in negative ways and I try and just, you know, stay down the middle keep keep my mindset on, you know, day to day daily improvement trying to be the best that I can be, and not really worrying about what other people say. With no disrespect to the tight ends who have followed Tony Gonzalez. Are there times that you still look back at the special gifts that he brought to the offense and now you see the comparisons that everybody's putting on call pets is it exciting to you to think that this might be somebody who can be compared to that kind of player. Yeah, I mean Tony, obviously first out Hall of Famer and you know arguably the best ever do it in his position. Certainly, you know it was the first guy to really change the position into what it is now. And so that's a lot to live up to and I wouldn't want to put that kind of pressure on anybody I think for Kyle, you know the biggest thing is is to just worry about getting better and you know learning the offense trying to get a little better every day. He's got great potential great, you know, upside but you know he's got to focus on daily improvement and trying to learn the offense as best he can.  And so that's one of the biggest things I learned from being around Tony is that there's really no shortcut to be in the best at it. You know, you have to work at it and I think if he can do that, that'll set him off in the right direction. Justin Talbot. Hey Matt, we're only a little bit into the offseason program so there's a lot to figure out between now and when you guys get on the field but what is an offense with Julio Jones, Kyle Fitz, Calvin Ridley, all the other playmakers you guys have. What does that look like in your mind? Man, we're really at the beginning of this. So, you know, we're working on making sure we can get lined up in our formations, making sure that we understand, you know, what routes we have on certain concepts. I'm excited about the guys we have in the building for sure and, you know, feel like there's guys that are highly competitive that one-on-one football game. So I'm excited about that standpoint but we have a long way to go. And kind of going back to what Charles was asking about and then, you know, business decisions that come with the territory. There's also been speculation about Julio's future with the Falcons, how a move of him could affect the salary cap situation.  How's he handling all of that and any insight on that situation? Yeah, I mean, listen, I love who.  I don't get involved in this side of it, you know, from a teammate, from a player standpoint. He's my teammate, you know, he's my guy and you let the other side of it shake out how it is. But I know this, he's always ready to go. He's an incredible competitor and one of the best to ever do it at his position. So he'll have himself ready to go. There's no question about that. Kelsey Conway. Hey Matt, ever since Arthur Smith's introductory press conference, he really stressed that he's about bringing accountability to the Falcons and he said he's going to make the best players accountable. I know you've only been on the field with him a little bit, but through the meetings, have you been able to get a sense that that's kind of the message he's going to bring throughout the building? Oh yeah, for sure. You know, you get on the meetings, on the Zoom calls, and he's asking everybody questions, firing off questions, making sure that guys are on top of what's being installed. And if they're not, making sure that they know that it's our job as professionals to find a way to learn this information and make sure we know it. And I think guys have responded well to that, but I certainly think he's made that felt from the beginning. Andrew, you talked about a little bit of the differences and challenges about learning a new scheme, but just how different is this scheme and what are some of the biggest things that you're going to have to adjust to? I know you said it's the language, but I'm sure there's a lot more. Yeah, I think, you know, from a language standpoint, I think, you know, I've played a number of different systems now, so it's like, you know, a combination of a couple of them. And so I go back, the formations are really similar to West Coast formations, which I played in for a number of years. Protections, you know, very similar. The concepts are similar as well. It's different names, so it's just kind of making sure that you have the right word association and, you know, you're speaking the right language. I think the biggest, you know, difference comes from getting a flavor for, you know, how the coaching staff is going to game plan, you know, what the week is going to look like, how they're going to call plays, situationally what we want to do. Try to get on the same page as fast as you can there, I think is probably the most important part. Zach Klein? Matt, it seems like the other 65 offensive coordinators you've had with the Falcons always talk about balance. But last year you threw nearly 200 more times than you did your rookie year in your 13th year. Is that just an evolution of the game? Can there really be a balance between passing and running in 2021 NFL football? You know, I think there can. I think in one of the organizations that was extremely balanced was Tennessee, and we've got a head coach that is coming in from that system. And so obviously they've had a different skill set of players there, different guys, but you know, I don't know what it looked like. My job is to try and operate whatever play is called. If it's 200 more passes than it is runs, we've got to find a way to make it work. You know, but I think, you know, most of the time teams are at the best when, you know, they make defenses to defend everything. Run pass, play action pass on the move, you know, just a ton of different things to tap to handle.  You don't know how injuries are going to go. You don't know how the season is going to go.  And what is a 36 year old Matt Ryan is 14th year appreciate more about the game than he did maybe as a rookie? I think, you know, you realize how hard it is, you know, at this age and so you appreciate the success, probably more now, you know, I've never, I've never really been motivated. You know, you want to win but I really hate it losing more than I love winning, you know, it would eat at you more.  And I probably appreciate the opportunity more now, knowing that, you know, I'm not in the first quarter or first half of my career.  Steve Wysh. Hey Matt. Hey, I just want to talk to you like I got a bigger picture, you know, you see a lot more of these, you know, quarterbacks, Aaron Rodgers, Russell Wilson, the world kind of be becoming more empowered, but you're not really out there, you know, speaking about your contract situation or how much longer you want to be with your team. When you look around and see what's, you know, going on with some of those guys, how comfortable is it to kind of be in the situation at your end, like you said, having people in the building believe in you. Yeah, I think everybody's, everybody's situation is different. I think they're, you know, I think you're correct. I think there's been a shift, for sure.  And, you know, I think that's a good thing from a player standpoint is, is, is you want some of that you want your voice to be heard. I feel like, you know, within our organization, you know, within the building that I've been in, I've been in a really fortunate spot where my voice has been heard. And I've always felt that way and always felt appreciated, but, you know, so I can't speak for other people's situations. I just feel fortunate that mine has been you know, as solid as it has been for, for the better part of 14 years. And now you just talked about also because, you know, you say there are limited opportunities because of your age coming up. How do you think this organization, you know, again, with this new leadership change has positioned you or the rest of your team to get you or is positioned in a team to kind of get you to the promised land, so to speak, on that limited window that you just mentioned? Well, it's not that limited, you know, I know I feel pretty good.  So, you know, I still feel pretty good. I just understand it's not the first half, you know, we're probably into the second half a little bit more. To answer your question, I feel like we're in a good place and, you know, we've got to improve, we've got to get better. There's no question about that, but I feel like we've got really good people in leadership positions with, you know, with a mindset and, you know, a clear vision for what they want to do.  But I feel, you know, I feel like I'm in a good place. Mark Bradley? Matt, if Terry Fontenot and Arthur Smith had come to you back in the early part of spring and said, we really have a rare opportunity to take a quarterback at number four. This isn't a reflection on you, but we think that planning our future, franchise future, this would be the way to go. What would have been your reaction to that? I don't know.  It gets magnified at the quarterback position because everything does, but, you know, this happens to guys every year, every week in our league. People are brought in to try and replace you that are cheaper, that are younger, you know, and it's your, you know, responsibility as a player to try and not make that happen. And so I don't know what I would have done, but, you know, maybe that'll happen at some point in the future, but it hasn't happened yet. I know that obviously you've enjoyed the total backing of this organization since the moment you were drafted. Did you have a little talk with yourself with the new coach and the new GM and say, you know, maybe they won't like me as much as the other guys did. Did you prepare yourself for that in any way? Yeah, I think you always do. I think you never know when there's transition, you know, what's going to happen. You have to go prove it with the way you work, prove it on the field, earn their respect. And I'm still, you know, for sure in the process of doing that, I'm in a fortunate position where they've got a body of work to be able to look at, but, you know, I still have to do that every day.  You know, I was told at a young age from some veteran players that in that locker room, you don't own the locker, you just, you rent it. And so, you know, I try and pay my rent on time all the time and do the best I can do to stay in that spot. Alex Glaze. Hey, Matt. So obviously just kind of in a way to piggyback off what Steve was asking you really about other quarterbacks around the league. You know, a lot of quarterbacks have issues with their front office, not bringing in enough weapons for them to have at their disposal. Just when the Falcons are picking it for was there ever a question in your mind, whether they were going to go quarterback or provide you with another weapon. And when they you saw the direction that they went, just what does that tell you about kind of how they view you and your future with with the organization? Well, first, you never know how it's going to go. The longer you play in this league, you just there are no there are no givens there are no certainties. And so, you know, I didn't I didn't know which direction it was going to go at that point. But, you know, obviously I'm excited when you see a guy like Kyle get drafted and the potential that he has in the production that he had in college.    You know, the thing I've been impressed with from him is just, you know, his his humility and his ability to want to work in the first couple of weeks. I think that's, you know, genuine, you know, and I would encourage him to continue to stay that way. Because to me, you know, when you're constantly trying to get better and improve, that's that's the way you get to where you want to go. And he's certainly off to a good start.  Just what does a Falcons offense without Julio Jones look like? You know, I don't know. He's been such a cornerstone of what we've done for a long time.  But he's just been he's been such a great player.  I love him. And, you know, we'll see how things shake out. But he's probably impacted my career more significantly than any other player. And, you know, I've been really fortunate to be around him for as long as I have.


Hey folks today. We have something to talk about that. I didn't want to have to talk about And that's because I'm sitting here finishing up our coverage at Nintendo Prime of All the news that came out in the Nintendo Direct last night It was a jam-packed Nintendo Direct trying to make all my plans for our podcast recording We got going out tonight. That's right folks. The podcast is coming back after I don't know what it's been a month I don't know. It's been a while still This came across my desks. I instantly got it up on Nintendo Prime.net But I wanted to talk about it some more here on the YouTube channel because It really it's one of those it really grinds my gears kind of moment from Nintendo and This is the kind of thing Nintendo does that continues to frustrate consumers So if you haven't heard yet Nintendo is discontinuing the NES classic edition in North America Here's exactly what Nintendo had to say to IGN Throughout April NOA territories will receive the last shipments of Nintendo Entertainment system NES classic edition systems for this year We encourage anyone interested in obtaining this system to check with retail outlets regarding availability We understand that it has been difficult for many consumers to find a system And for that we apologize We have paid close attention to consumer feedback and we greatly appreciate the incredible level of consumer interest and support for this product NES classic edition wasn't intended to be an ongoing long-term product However, due to high demand, we did add extra shipments to our original plans And then IGN goes on to say that the company has no plans to produce more NES classic systems for North America And this announcement includes the discontinuation of the NES classic controller as for third party accessories Nintendo said the decision whether or not to continue production of the accessories will be up to each individual manufacturer Basically third parties can decide to do whatever they want with NES classic peripherals What what's going on? What's Nintendo doing? Okay, so they go on to say that the NES classic edition has incredible demand And they understand that it has been difficult for many consumers to find the system. So here's our solution. We're gonna stop making it What what is Nintendo doing? This is probably the most upset you guys have seen me get on this channel in a long time Maybe since such a water died and even then that was a different kind of upset then I was sad today I am angry I don't understand what Nintendo is thinking here now I get that the NES classic edition was probably meant to be a limited Holiday run right like so they've been producing it for an extra few months But it doesn't feel like they've been producing it for an extra few months They even admit that it's been difficult for people to find it. So I It's so frustrating that Nintendo does these kind of things it was frustrating that they under You know, they didn't understand what the demand was going to be for the system before launch Despite the fact that there was clearly high demand for the system before it ever hit store shelves How hard is it to gauge consumer interest in a product that people clearly have been demanding from you for years? Oh, it's so frustrating and I'm not just saying this because I don't have an NES classic edition Right. I didn't plan to buy an NES classic edition At least not now I was hoping to maybe get one in a few years Down the road once I had some of our live streaming stuff going at a regular pace And I'm not just sitting there live streaming Breath of the Wild which yes, I know a lot of you folks Are wondering when am I going to live stream Breath of the Wild again? My answer is I don't know maybe this weekend I I don't know right now but What I do know is that This is an extremely stupid move by Nintendo and they are literally leaving money on the table I don't get it and this is Coming off the fact that we also don't know anything about virtual console games on the Nintendo switch Nintendo's brand new system. We don't know what they're doing with virtual console But whatever they're doing, it's probably not going to be $60 for 30 NES games 30 of the best NES games That's not going to happen And it's not going to be Layed out in the same way that this system was the save states as an example. That was a huge thing I I just don't know what Nintendo is doing You know, I'm not saying the NES classic was perfect The controller came with had too short of a chord and yes, I know there was extensions and there was third-party controllers that had longer chords but reality is that Nintendo is just Irritating consumers What feels like for no reason right the only reason I could come up with Them needing to cancel the NES classic edition in North America, mind you They have not announced cancellation in any other territory. So Europe you might still be getting the NES classic edition The the Famicom classic edition in Japan's probably still being made But for some reason in the United States, we need to cancel the the thing that no one's been able to find and buy Conveniently at all at any retailer. It's not all we're going to pull it from retailers and sell it on our online store ourselves For future sales. No, it's we're just pulling the unit. I I'm so frustrated that Nintendo is making this kind of decision And if anything the NES classic editions, you know Popularity should drive future plans, right? Like they should have an SNES classic edition in the works and then say four years from now or or so They should have the n64 classic edition and heck we haven't even gotten into the gameboy line There could be a gameboy classic edition But it makes me not want to buy future classic editions Because they're not going to allow all the consumers that wanted to actually buy the thing, right? And I know some are saying oh, this supports scalper mentality. I don't think that's what Nintendo is trying to do I think they're subtly saying hey, we only meant for this thing to be on sale for a month But the man was so high. You should just be happy that we've you know made more units over four months But I'm not happy Because they never met consumer demand one time If you're going to just say hey look our plan is to be done with this system By the end of summer that's fine That gives you four or five months to flood store shelves with this product Before maybe you have the SNES classic edition coming out the end of the year or before you have the big holiday push for switch I I just don't understand it's not like any s classic edition is taking away sales of the Nintendo switch You can't run the Nintendo switch anywhere either, right? We're a month and a half out We're a couple weeks away from the next big Nintendo switch game hitting and you still cannot find Nintendo switch units on store shelves So what is Nintendo doing? That that's what I don't understand. What are they doing? They're not making anymore any s classic editions They couldn't even keep up with the man of it in the first place. They're not making enough Nintendo switch units I just don't get it Can one of you guys explain this to me? What is Nintendo thinking, right? I'm working at Nintendo. I have this massively high selling probably low profit margin, but High selling classic system out here and we're like, yeah, let's just put that on the chopping block. Heck They could raise the price of the thing 10 bucks and still sell it and it would still sell out Nintendo switch is a whole nother story, right? Because we're still in that launch window and you know They've had new units hitting but it doesn't feel like enough and it's hard to know like consumer demand for the switch It's hard to gauge right now It's obviously in high demand But I don't know how many units they're they're putting out there and we'll find out, you know on april 24th or 27th or 28th They have some sort of investors meeting for the end of the year end of the fiscal year And we'll find out then like maybe they have been sending out a ton of switch units Maybe we'll find out they've moved four plus million units Which would be insane and if that's the case it's hard for me to complain that the the nintendo switch hasn't been available easily Because that's a lot of units Well the nes classic edition. I don't even know if there's four million of them period That have been made and it feels like the nes classic edition just in the united states could have sold four million It's a missed opportunity. I hope nintendo learns from it Like if they do do an snes classic edition someday I hope they realize you need to put out like three million of those things at launch in the united states alone Um because you're gonna sell throughout every single one of those units if not at launch You're gonna sell them out within a couple months I I'm just beyond frustrated. I can't believe nintendo is doing this Uh, if you can come up with some logical reason down in the comments on why nintendo is cutting You know cutting the nes classic at a time. It's still in high demand Be my guest and let me know because I don't see any logical reason in this Uh, even if they want to push virtual console this summer, I I don't know I can't believe nintendo did this This isn't a tiny ruffle chance from nintendo prime signing out