So next up, we're going to pull two of our, hopefully, CMAC. Is CMAC here? Yes, yes, there you are hiding in the back. Two of our product managers from the OpenShift team, CMAC, and Daniel. And we're going to get you to use these guys. And we are sort of running on time. We're running ahead of time, and behind time, and all other things, so you. And there you go. All right, without further ado, here's OpenShift 4. Thanks, Dan. Hey, everyone. Good morning. Hope you found your way through the traffic in this morning. My name is Daniel Messer. I'm product manager in the OpenShift BU. And I'm here today with my colleague Simac. I'm just going to get up. I'm product manager for Developer Experience for OpenShift. And we want to talk you through some of the changes that are coming in the upcoming release of OpenShift and also give you an overview of, to use Diane's metaphor where the pocket is going, where we were aiming throughout the year. And we're going to start with Daniel, walk you through some of the areas, and then I'll take over and focus a little more on the Developer Experience and what we have for developers in the upcoming release. Yeah, right. So today we're going to talk about how OpenShift 4 enables the next generation of cloud-native application platforms, and specifically Kubernetes-native applications. So there are three key themes here that we are going to walk through. First is how we are going to continue to deliver on the promise of actually delivering an enterprise-ready production grade Kubernetes distribution. We are then going to show you how we enable basically cloud-like self-service management experience on cluster, on all supported footprints. And then Simac is going to dive into the Developer Experience and how we basically give developers all the tools they need in order to iterate faster and essentially forget about the underlying platform. So when I joined Red Hat in 2014, OpenShift 3 was actually just in the works, although it wouldn't be until a year later when we would actually release 3.0. And it was quite astonishing at the time because nobody really was using that thing called Kubernetes at the time, right? So it wasn't even 1.0 yet. Yet Red Hat internally was very busy in essentially rebasing OpenShift 2 entirely onto Kubernetes, right? Coming from a very different container-based management system that we had developed on our own before, completely shifting towards that thing called Kubernetes that wasn't even 1.0 yet. So we're here today, five years later. We are with OpenShift 4. And we are making similar big bets, which is basically saying OpenShift 4 is going to be a self-sufficient platform that is enabled and featured by Kubernetes operators. And what this means is, while operators play into several parts of the ecosystem, what this means for OpenShift is that there is one big win, which is getting the system self-aware and self-managing. In OpenShift 4, we basically manage the entire stack, also what's underneath of OpenShift, including the operating system and, optionally, including the infrastructure. So we move away from these two maintenance window model where you have a maintenance window for your rel, you patch CVS there, and then you have a maintenance window for OpenShift 4, or OpenShift, where you have other CVS and enhancement and bug fixes. This is going to be one cohesive thing that you update as a unit. And we basically extend control by the use of Kubernetes operators all the way down to the infrastructure, which means that every service that makes up OpenShift and that makes up this Kubernetes API and all the artifacts below that make this happen on the hardware infrastructure there are exposed as Kubernetes objects. So this is the premise of an operator. You basically put some software on your cluster. You put all the smarts and SRE principles in that software. And you surface a very lightweight API to the outside so users can actually consume the service. And that's how we model everything that makes up OpenShift. Everything is an operator. We actually wrote 42 operators to control the entire platform. And 42, I think, is a legit number for this use case. So this allows us to pull off some nifty tricks when it comes to installing. We have completely revamped the installation experience. We have actually separated the tool that we use for the installation from the technology stack that we use for the upgrades, which gives us much more control over the upgrade process. So the installer basically lets you provision in a fully automated way an entire stack that makes up OpenShift 4, including the infrastructure from cloud or hardware providers underneath. That's what we call full state automated install. So if you have nothing else to go, you can get a fully featured production ready OpenShift 4 cluster up in just about 30 minutes. So from the complete green field in terms of hardware or cloud instances all the way up to the console. If you have existing hardware or you want to have more control over customizing the operating system, we also support that. There's an installer mode that works with existing infrastructure. And then next to that, we have a completely managed offering from Red Hat, where we basically stand up the cluster for you, we manage the cluster for you, and you just get to consume its services and worry about your apps on that cluster. This is OpenShift dedicated, which will lower out on OpenShift 4 pretty soon as well. Now, we've started supporting a variety of infrastructure providers, both on-premise and off-premise for OpenShift. And we will continue to broaden that support. We basically here differentiate between installer provided infrastructure and user provided infrastructure on the right-hand side. Installer provided means that you basically give us access to the infrastructure API. So that's your AWS account. That's your OpenStack credentials. That's your GCP credentials. And we will basically let the installer create all the necessary infrastructure artifacts to install OpenShift. We also have another mode, which is called user provided infrastructure, or UPI. That is basically you providing the infrastructure, right? You setting up the network, the storage, the compute resources, and you also get to have a say in the operating system of the worker nodes. The only thing that retains or remains under the control of the installer is actually the control plan. And that's very important because this is how we basically give you the abilities to apply updates in a very consistent and very stable manner. So updates on this thing are going to be a breeze. Because we entirely control the entire cluster state with operators, exposing it entirely through YAML, we basically have very deep insight into what's going on in the system and how it is configured, and can basically make very smart decisions around how we upgrade. When we upgrade such a system, it basically comes down to updating the operators that control the various components. And then the operator in turn knows exactly how to update the domain it is under, which is under its control, right? So essentially, you get the updates from a Red Hat online service, and they are simply applied from DUI. And this is a process that every junior administrator can do. We want updates to be so simple and casual for you like updating your apps on your mobile device, right? It should be something that you can basically do confidently during the day in production, right? And that's why we will basically release on a much more frequent basis updates to the platform. And we are feeling so confident about that that we will give you the option to basically opt into automatic upgrades in the background, right? We also introduced a notion of update channels. So you basically have the ability, like in your browser, to change to a beta channel, or a nightly channel, or a cannery channel, and get updates much faster than you would on a stable channel. But basically, this is something that the cluster is now orchestrating itself, because the logic that does all of this is sitting inside the cluster. It's not an external thing anymore that imposes itself on the system. We have complete control of the system on a continuous basis because the operators watch the state continuously. One thing that allows us to do is the base operating system, which is Rail Core S. This is basically a combination of both of the best of both sites, which is Fedora Atomic and Container Linux from Core S, which makes up a very small Linux distribution running the Rail kernel. So this is Rail, right? It runs the Rail-8 kernel, and it inherits the entire hardware and software certification ecosystem as a result of that. But it's packaged a little bit differently, right? It's an immutable base image that you are not supposed to directly access or configure. Now, that's where some people usually get afraid and say, oh, you take away control from my beloved operating system, how I'm going to install my monitoring or my favorite metering agent there or logging agent. That's all taken care of on top of the cluster, right? So in this kind of new world, we basically install agents or drivers with operators. And we've actually done so in OpenShift 4 already. We support NVIDIA drivers, GPU drivers as an operator. We support system monitoring agents as an operator, which you can install directly from the operator hub in OpenShift, right? But this is your base, and Rail Core S is always going to be used for the masters, right? So this is where we retain some tighter control on the control plane. But in the user-provided infrastructure mode, you can also use well-regulated Enterprise Linux 8 as the base for the worker nodes. So here's one of these platform operators that I have been speaking about earlier. So the Kubernetes machine operator, for instance, is a very interesting prospect. What it allows you to do is basically model the underlying infrastructure from a provider perspective into the cluster. So this operator knows how to talk to the AWS API, for instance, or knows how to talk to the OpenStack API. It knows how to talk to GCP and Azure. So it is able to surface some core concepts of these compute platforms into the cluster. And all of a sudden, we have a new object in Kubernetes called a machine. A machine is basically representing a compute node in the system that either hosts a master or a worker. So it's an actual Kubernetes object, very similar to a pod or a service, right? You can look at its YAML. You can edit the YAML. When the edit is allowed and valid, the operator will detect it immediately and start to change the machine's configuration so that it matches what you put in the spec section of that object. It's normal Kubernetes tuning. There's no additional commands required. You could continue to use Coup Control. And very similar to basically how replication controllers control fleets of pods, there's a machine set controller controlling sets of machines. So if I wanted to scale my cluster, I basically go edit the machine set object. I increase the counter from three to four. And then the machine set operator in the background starts to talk to the infrastructure API and provisions in the machine. And like two minutes later, I have a new node joining my cluster, right? This is as easy as it gets when it comes to running a Kubernetes cluster these days. And I haven't seen any other Kubernetes distribution that does this today at this very core. So essentially, you can see where this is going, right? You can take the same concept as horizontal pod autoscalers and apply to machines. And we have done so. We have actually a cluster autoscaler that watches CPU memory and network utilization in the system. And you can set up events so that it basically starts to increase machine sets and scale your cluster on demand, both up and down, obviously, right? So this is how powerful it gets with operators. And this is all accessible from within the cluster, right? You still are editing cube objects. Now, let's talk a little bit about how these operators enable cloud-like self-service experience on the cluster. So the first step to make this feel like a cloud offering is providing a central control plane, a central management pane to the users so they can see all the OpenShift clusters that they've deployed. Something I didn't tell you before when we talked about the installer is that whenever you install an OpenShift cluster, there's an anonymized telemetry sent back to Red Hat. And the unified hybrid cloud console on cloud.redhat.com is the place where this ends up. So you have a list of all the clusters you've deployed across all the footprints, either on-premise or off-premise. And you can see some very basic data, like which version they are running, how utilized they are, how many nodes they have, and if there's an upgrade available. So that's the central point where you can get the single source of truth of all your OpenShift deployments. And that's also where you basically manage the subscription of your commercial OpenShift container platform distribution. Next is the operator framework. This is actually something we've launched a year ago. And it's an open-source project aimed at the wider Kubernetes community. So like Diane said earlier, everything we do in OpenShift eventually flows back to the community. The machine set operator and machine API operator that I told you before is actually part of a SICK. It's called cluster API. It's very active. People are very enthusiastic about this because Kubernetes gains control of the underlying infrastructure. And the same is with operator framework. It's an open-source project aiming at the wider Kubernetes community trying to force the ecosystem of operators by making it on the one hand easier to actually get started in writing an operator. There's an SDK component that allows you to write an operator in Go. Also use Ansible templates to write an operator or convert an existing Helm chart into an operator. And then there are also on-cluster components like the operator lifecycle manager, which basically help the cluster admin provide a safe route for the operators onto the cluster. Now, how do operators play into the perspective of running and getting managed services on the cluster? If you think about how you would get a database running for a local developer example, everybody can basically launch and containerized Postgres database, for instance. But this doesn't really give you anything. You're still in charge of actually maintaining that. All you've basically done is you launched the Postgres daemon with some fancy flags that tell the operating system to create the impression to Postgres that it is alone in the system. But that's all you did. There is no further operational logic to that. Now, the next step that developers usually take is using one of those managed services you find in many of the cloud providers, where you basically get, in this case, a Postgres daemon or a service as a service. You get to basically say, I want to have a Postgres database. And five minutes later, you get the endpoint you can connect to. You get to do some very basic admin capabilities or activities on that instance. But all the rest of it is managed by the cloud provider. So these are usually virtual machines that you're being built for and then some extra money on top for the service. But that's it. Basically, the cloud provider has all the logic or all the operational responsibility for that service. And it usually fulfills that with an SRE-like organization. So that is something that is very easy to stand up for, but effectively, it's somehow hard to get onto the cluster, because it's still sitting outside. It's using a different user authentication mechanism. It's a different tooling and different UI that you need to use. So this is where operators come in. Operators basically take these SRE best practices that cloud providers are using to provide managed service in the back end and codify this in software. And this software is running on the Kubernetes cluster. And it's basically exposing native Kubernetes APIs for you to interact with and request services. So very much like before, I can now say I want to have a Postgres database. But all I basically do is I create a new object on my cluster called Postgres database. And it's a YAML format. And it has a spec section. And in the spec section, there's probably a version tag. And the amount of read-only slave replicas and stuff like that. I control the complete configuration of the database from that one particular object. And that basically runs as a workload in my cluster. And therefore, it's available wherever my cluster is available, which is my local workstation, my staging environment on Cloud Provider A, or my production environment on-premise or Cloud Provider B. It doesn't matter. You don't need to learn anything new. You basically only interact with that operator's API. And that's your contract. To foster this ecosystem, like Diane showed earlier, we have launched a so-called public registry for operators called operatorhub.io. This is where the community can gather around posting their operators and sharing them with the wider community. And we also have an embedded version of that operatorhub in OpenShift, which also includes the certified operators of our partners. So we are working with a lot of partners these days, like Crunchy Data, Cystic, Redis, Couchbase, and many more to basically certify operators on OpenShift and support them together. That means if you have a problem with your operator or your workload, you can file a ticket with Red Hat, and we will basically triage the support in the background with the vendor. And we basically make sure that this operator stays comfortable as OpenShift 4 moves through its relief cycle. Operators are also first-class citizens. So we have talked about platform operators before, which enable OpenShift to take control of the underlying platform and its own infrastructure. But it's also a concept for these back-end services, like your favorite database, your favorite message queue, your distributed tracing framework. So we want operators to basically provide these back-ends as a service, and therefore, operators are treated as a first-class citizen on OpenShift. When you think about an operator's nothing else than a pod running in the deployment on your Kubernetes cluster. With probably a good amount of white permissions, usually cluster-wide permissions, and it's going to be a long-running workload as well. So we want to take extra care of that operator and not just have people fling them in via Ham charts or basic Kubernetes manifests. So basically, when you package an operator for operator lifecycle manager, the lifecycle manager essentially instantiates all the things that make up the operator for you on the cluster. So the deployment, all the RBAC, the Custom Resource Definition, and so on. And it keeps maintaining this as the operator gets updated, because this is another concept that we want to establish. We think software should be as up-to-date as possible, right? It should be as easy to update the software as you update software on your phone when you see that little badge icon light up. We basically enable you to think of operators as some software that comes from a catalog that you can attach to operator lifecycle manager, and you can essentially express a subscription against one of those operators. The subscription is essentially an intent to say, I want to install this operator on my cluster, and I want you to keep it updated as soon as updates come in via the catalog. That means either automatic or with manual approval from the cluster admin, you can get new operator versions automatically installed on your cluster and potentially be able to manage newer versions of the application stack and automatically update the already existing instances of the managed application to a newer version to protect you from CDEs, bugs, and all these other things. Last but not least, from a developer perspective, all of which I've shown you so far up until this point is essentially cluster admin territory, right? The user doesn't see this.  So the operator essentially introduces custom resource definitions, which essentially are API extensions to Kubernetes. So they introduce new objects into the cluster, which we surface as part of the developer catalog. So next to my all existing templates, run times, programming languages, I can now see new services offered by, for instance, in this case, the MongoDB operator. I have a new object called MongoDB cluster, which I can instantiate. And poof, 16 seconds later, I have a MongoDB cluster up and running. This cluster is still made up out of pods and services and secrets, config maps, persistent volume claims, and what have you. But you don't need to manage this. You don't even need to be aware that this exists, just as you are probably not aware what exists behind the managed Postgres database on AWS RDS, for instance. But you, as a developer directly from the catalog, just consume this service. Speaking of developers, I think it's time to dive into what else we have in the back for those guys. All right, so now let's talk a little about what we offer developers in the upcoming version. All of this is really interesting, but the point of that is really to be able to build more applications faster, easier. That's really the ultimate goal. For developer, for application developer teams, the result of that is that they have a more cloud-like experience. They can create stuff on demand faster. If they need a cluster, they can get it up really quick without having to go through operation. Myself, in the last six months, I have installed as many OpenShift clusters as I did the last four years. That's simple. It becomes for a developer like myself. But what are we doing for developers? The first thing is that we have invested in a CLI that focuses more on developer scenarios. So Cube, CDL, and OC, they are really useful tools, but they focus on Kubernetes objects. So there is a translation to be made, which is usually in the mind of a developer itself, himself or herself, how an application, with whatever definition I have for my application, maps to these objects. So through the CLI, we try to abstract away some of this aspect, make it a lot simpler to have a Git push experience essentially on OpenShift. You create your app, it ought to create. You push the existing directory, being that the source code of your app, the Java, Maven app, or Node.js or something else, pack it up and send it to OpenShift and create the objects and get deployed. All of that happened behind the scene. And the most important piece is the third part, the watch functionality, that you can ask the tool to watch the changes that you're making in your local workspace and sync it automatically to a pod running on OpenShift. So I can iterate on my code the exact same way that I do locally. If I have a Spring Boot app running and I run it in the Dev mode so I can modify my classes, it automatically reloads, recompiles and reloads the class. I can test it in the browser immediately. We're aiming for the exact same experience but on OpenShift so that it can take advantage of the other services that are also deployed on OpenShift. You don't have to run them locally. If you're using a Postgres database that's running on OpenShift and you deploy your pod with your Spring Boot app, iterate, make a change in the code, deploy automatically through the watch, and test it on the platform so that it's consistent stack, the same version of JDK, the same version of Spring Boot. You have the exact same stack that the application would use when it's deployed in the staging environment or production environment. This was released last week as beta so I definitely encourage everyone to give it a go, give it a try, and provide feedback how it's working for your scenarios. The next thing we are doing is that we are taking a step back and while we love the Kubernetes objects and the interface to interact with them through OpenShift console, but we don't want to leave the application concepts behind either. So we have created a new console that focuses specifically on developers and applications. And the application concept is a king there. So everything is around the application concept, grouping the objects, how they relate to each other to make sense of it for an application that a developer team defines. That gives an overview, a topology of how objects are related to each other for a specific app. It brings more of an app-related capability like CICD pipelines and other aspects that are coming along as we go forward. So in every release, we add a little more of the developer scenarios into this Dev Console so that they have both personas, both type of users, covered really, for someone that wants to be deep into Kubernetes, directly interact with bare-boned Kubernetes objects. That's what OpenShift console provides. And for Dev teams that they want to be a little, this stands from Kubernetes objects to be abstracted away and focused on the applications that have the developer console that gives them that capability. The next area is that we are working on a cloud-native CICD that is coming as a preview on OpenShift 4.1 and coming with more scenarios afterwards. We have historically had Jenkins, shipped Jenkins on OpenShift, and we will continue to do so as we go forward. But let me just take a little test. How many of you, in some form in your organization, are using Jenkins? Great majority. How many of you love Jenkins? All right, so I don't need to explain why we did this. So we are working on a bit upstream on a project called Tecton Pipelines, which aims to standardize the terminology, the CRDs, the concept, the building blocks for creating CICD on Kubernetes. It's designed for Kubernetes environment. It runs in containers. And it's designed for cloud-native apps. What does that mean? You can use cloud-native apps in any sentence these days. What it specifically means is that we are walking away from that Jenkins model of there is a central place that owns the configuration, that owns the plugins, that owns pretty much everything to know about CICD. And everyone else is just a client of that central thing. We are moving away from that model to be a central thing that is just responsible for running stuff, like spinning pod and do whatever the team has defined. So teams can own their pipelines. What exactly want them to happen in it? What plugins they want to use? Every aspect of the pipeline can be owned by separate teams. And when you create that pipeline, Openshift or Openshift Pipeline, generally, it would just execute that. So we remove that central ownership of the pipeline and distribute it to the teams themselves. The consequence of that is that there is no central thing to manage. There is no babysitting a central CICD solution. There is no scaling issue because it's a pipeline running in separate pods. You don't have that central master to be in control of everything. And we, of course, distributed through Operator Hub. So in a few weeks, when you will have this appear in the Operator Hub, you can install it and start using the pipeline through the Tecton CRD. So it's a bunch of CRDs that you define your pipeline similar to the rest of Kubernetes objects that you would use for deploying your applications. Another area we have invested and focusing a lot is serverless scenarios. So Knative has been a very popular project since inception upstream. And Red Hat has been heavily involved in it with Google and other contributors in the space. So we're bringing Knative and Openshift distributed through Operators that allows you to run a serverless application. Essentially, turn any application into a serverless scenario based on a container. What does that mean? That you deploy your application. Your application automatically scales through zero. A request comes, an event comes, application wakes up, serves it. When there is nothing to happen, it's going to go back to zero again. So it enables functions as a service scenario, serverless scenarios. We already have a partnership with Azure that it enables you to run Azure Functions on Openshift. Anywhere that Openshift installed, through Openshift serverless, through the Knative constructs and Openshift. And we are pursuing that partnership with other fast providers as well that gives you the serverless base, essentially, to run a function as a service or any service application that you need on Openshift regardless of when, where it is deployed. The next area is the service mesh. Service mesh is also an up and coming area in application development. We could call it also in the network space. It is a network that is dedicated to services.  There are a lot of talk about packets and routing. Service mesh is a network that is designed at a service level. So it's very aware of how services are talking to each other, which service is talking, to which service, how traffic is flowing between them. Having that type of network allows us to define rules at a whole different level, how traffic should flow between services, which services allow to talk to which service. Or look at it the way around. Like looking at this network, we can also extract how services are talking to each other. This is one of the most valuable piece of information that every developer team I've talked to, they've been asking me that. If you can look at, I don't know, most developer teams, if they have a big application, they don't know the exact architecture of the application. They know the piece of it, but they don't know exactly how traffic is flowing between everything. A service mesh gives you that view. That you just look at the application, and you extract that from how applications are talking to each other. And most important of all is that it provides this for any application deployed as a container. So we have had some pieces of this functionality before when people were building new cloud native application. When you were using Spring Boot, people could add some libraries in it and integrate it into JGear, or Zipkin for open tracing, or add other libraries that does smart load balancing, or traffic control. So it was possible before with using extra libraries for each programming language or framework that you used to get some of this capability, but that was only limited for the new applications that you build. The OpenShift service mesh, you get that for any pod deployed on the application. You don't have to touch your application code. You just get that out of the box because it sits around the application. It doesn't intrude inside the application. The next area is a series of tools you release under the CodeReady brand. CodeReady WorkSpaces is one of which. It gives you a web-based IDE. It gets deployed on OpenShift. And every developer can log in and create a workspace for himself with a stack of tools, like your Java developer. You want a workspace that supports Java 11 with Maven. So you get a stack for that within the browser. You can code in it. It's a very similar experience to Visual Studio Code. It's actually compatible in the new version, the plugin system with VS Code. So you can use a good portion of the same plugins there. And having this browser race gives you the capability that, well, on any machine I go home, I have the exact same workspace as I had at work. I can code on it. Or even better, I want to share my workspace with a colleague because I'm stuck on a specific problem I'm solving in my code. I want him to take a look at it. Well, in the old wars, when all of us were in the same office, I could just go grab him. But now my colleague is sitting in Atlanta. I just could send a link to him that opens the exact same workspace that I have on my machine. It opens it for him. He can directly code. I can watch as he is coding. So it gives me a new level of collaboration that I can have with my colleagues developing on the same code reactor within the browser. And with that, I'm going to wrap up our talk today. So the message here is that we're working really hard across all these themes to give you a cloud-like experience across the services that you consume on OpenShift. And also, for the day-to-operation itself, give you a cloud-like experience for installing OpenShift and managing OpenShift. We try to optimize as much as possible all the way to the operating system down. And on every release, on our quarterly releases, we're going to make this deeper, better integrated, expand it to other areas. And the same goes for the developer tools. We focus a lot on looking at the gaps where the frictions are and try to plan on every release to make it better. So come talk to us after the session. Give us feedback. What you're missing. That's exactly what we need going forward. Thank you very much. Thanks. That was really good. Thanks, D-Mac. It's always wonderful to see you. Thank you.


April 19th, 1775, the day marksmanship made history and our heritage began. This year on the weekend of April 20th and 21st, Project Apple Seed will be holding nearly 100 history and marksmanship clinics nationwide, each celebrating the liberties and freedoms that motivated our founding generation to begin our war for independence. Come join with thousands of patriotic Americans and stand on the firing line of freedom, celebrating the shot heard round the world and the freedoms that it purchased. Featuring guest speakers and certified marksmanship instructors, these events present a fun yet challenging atmosphere that the whole family can enjoy. Attendees will spend their time learning rifle safety, the fundamentals of marksmanship, and we'll hear the true stories and events of America's first day. April 19th, 1775, space is limited and events fill quickly. To learn more and to reserve your spot on the firing line, please visit our website appleseedinfo.org. That's appleseedinfo.org.


Thank you for joining me on Think Takawaii. I am Shayna Park, your host for Money Talks. Every October for the last 90 years, breast cancer awareness man called Pink October has been celebrated as people all over the world wear pink and also display a pink ribbon to raise awareness about the importance of prevention and routine screening for early diagnosis of rents to cancer. Globally, this is now the most commonly diagnosed cancer.  She is here today to share her journey with you. Hi, Helen. Welcome to the show. Hi, Shayna. Thanks for having me. Thank you for being on. Please tell us a little more about yourself. Let's see. I was diagnosed with breast cancer almost like 13 years ago. And currently, I live in San Francisco. I have lots of roots in Hawaii. For my job, I live and I'm a teacher.  And I also teach about breast and ovarian cancer health to college kids, to moms, basically anyone who will listen. And I would say that education is primarily my passion. So I'm grateful to be able to, especially this month, to be able to talk to you about something I'm really passionate about. And I'm grateful for you to be on the show and educate me and myself and the viewers because, personally, I don't know much about preventing breast cancer and all the steps to take. So I'm very grateful that you're here to share your story and what we can do to routine visits. So what are your ties to Hawaii? I know you said that you have a lot of ties here. And I know you're here for long periods of time. So what are your ties? Yeah. Well, I think in college, I met one of my dear friends and she is from Hawaii. And so I've been coming to Hawaii ever since I was 20. And then since then, I've met partners. I've met like dear, dear friends. And since then, it's become kind of like my family or my home away from home. So every chance I get, I come out to Hawaii and I stay with my friends for months on end. Luckily during COVID, I was able to actually live in Hawaii for quite some time and teach and just live the Aloha dream. And I loved every minute of it. And I'm always like, when can I go back? So it feels just like the islands have welcomed me and I'm very grateful for that. Yes. And do you plan on returning anytime soon? I always have tickets to Hawaii on my Google flights watch. So I'm not sure. Maybe in March. Okay. I'm so excited to see you again. I hope you come sooner than that. But going back to this month and the importance of October, can you tell us when you were diagnosed with breast cancer and what stage were you? Yeah. I was living in Beijing at the time I was diagnosed. I was working for an international nonprofit and I felt a lump and I don't have any cancer in my family. And this lump, I thought was nothing and I was just going to do nothing about it. But my mom actually made me go and get it checked out. And just on a 10 day visit back to California, I discovered that it actually, this lump that had felt different than the other lumps in my breast was actually breast cancer. And since then I had to kind of change my whole life. I was diagnosed at stage one. I did a lot. I was 27 and so they thought it was serious because oftentimes breast cancer is more aggressive in young women. And so they got me in pretty quickly. I was able to do an ultrasound and a mammogram followed up with the MRI and a biopsy. And after all of that testing, that generally takes months to kind of unpeel. It actually was pretty quick because they knew I wanted to go back to China where I had my job, my apartment, and my whole community, family, friends, like partner at the time. And so I was diagnosed kind of within a week. And again, it was stage one.  But again, the treatment protocols vary depending on age, family history, kind of pathology. And all of that stuff took kind of months to uncover. Wow. So you were very young when you were diagnosed. And with your whole entire process when you first went to the doctors and first being diagnosed, what were your thoughts? How did you... It was one of those things where you kind of like, because I had a flight out on Wednesday and I went to the doctors on Tuesday. And I thought it was just going to be like, check the box and then go take my flight because I had to go back to work. In China. And it was not that way. And I remember the doctor calling me. And everything at that moment goes quiet.  And again, everything just kind of quieted. And I just like, I remember I was in a parking lot after lunch with my friend. And I just kind of crumbled to the floor. And I didn't know what to do or where to go. And it, and again, just kind of moving forward took a lot of strength. And I, you know, at that moment, I definitely didn't actually feel like I had any strength. So. Wow. I can't even imagine because you were going home for a seven day vacation, you said? Yeah, 10 day vacation. Yeah, for a wedding. And your whole life changed within those 10 days? Yes. And I was never able to go back to China. I had to go into treatment right away, which comprised of a lumpectomy, which is where they remove the tumor, they spare your breast. And then, and then followed up seven weeks of radiation. And then five years of hormone treatment where I took a pill every day and I had to go into the doctors and get a shot in my stomach every month, which would bruise me. So my whole stomach was bruised. And that basically put me into chemically induced menopause. So I had all the menopausal symptoms of someone that was 58 plus, which included hot flashes, vaginal dryness, kind of mood shifts. I gained like 20 pounds.  Yeah. Wow. And I know there's some photos that popped up.  Because it appears that you're about to have a CT or MRI. And you have a smile on your face. So do you remember what you're thinking at the time? How you're feeling? Yeah. So I have to do MRIs. That's that machine on the left is the one of the machines I have to do every year, actually, as routine screening. MRIs are a lot more sensitive than mammograms. And because I'm at high risk, once you have cancer, it's kind of likely to get it again. And so MRI turns out to be the most sensitive for young, young people over a mammogram and ultrasound. It's quite costly. And so you kind of have to prove to insurance that you need it because I'm high risk. I get that every year. But then I also have a twin sister who then also qualifies to get high risk screening. And so that's actually key why education is so important.  But because my twin sister, you know, we were both 27 when I was diagnosed, well, now she doesn't have to wait 13 years to get a mammogram as routine. Everyone gets a mammogram at 40, but she gets to be screened more closely with annual MRI starting at the age of 27. So those are the little pieces of information that are really, really helpful. And we're just kind of understanding education, understanding advocacy and what you have to do for your own health really helps. But that, yeah, so that machine, you know, is really, really loud. It's kind of can feel really claustrophobic. And they basically like look at, they look at your breasts from different angles.  So that's just kind of a surgery picture. But that was during my lumpectomy. And how did you feel? I mean, it's a little scary kind of going into one of those things, right?  And I always, you know, dress kind of in a way that makes me feel good about myself. And then I also always have a plan afterwards of like going to a fun lunch spot with my friend or something so I can like have a reason to like something to look forward to to celebrate because your body and your mind goes through this like an hour long procedure where it's just like, can feel claustrophobic that it's in your ears and it's really loud.  You can't move. And then, you know, your mind can kind of freak out. So you're trying to do everything to kind of like calm your system down. They give you aromatherapy. They try to put on music that you like to hear. But it's also just a practice for me of like, I have to go into kind of a meditative state to kind of endure the process. So it can be challenging, but there's tools and things that you can utilize as well. Wow. It seems very extensive and I can understand why. And I know you mentioned earlier about the types of treatments you did, but could you go further into that and how long were you receiving treatments? Yeah, sure. So right after I was diagnosed, you know, they send your sample, kind of they do a biopsy. They take your tumor sample and they test it. And depending on how the testing goes, they determine whether or not you need chemo. I had four oncologists look at my tissue and then they basically can do some testing to see whether or not your tumor's going to actually respond to chemo or not. And so I had two oncologists say yes to chemo, two oncologists say no, but then finally I did what's called an oncotype test which determines that like the likelihood of chemo actually helping me have a, you know, better chances is actually slam and kind of some of the after effects can be worse. And so my oncologist that I ended up choosing said, you don't need to do chemo. It looks like you're not going to benefit that much and you're going to put your body through a lot, you know, and like you lose hair and different, and you can actually be at risk for different complications. So I chose to do a lumpectomy.   But because my tumor was small and operable, I was able to kind of spare my breast with no compromise to kind of reoccurrence and risk. So I did a lumpectomy and then you heal from that and then you do seven weeks of radiation. So it's going in for appointments Monday through Friday. And you're sitting under that kind of machine and they're basically radiating your, kind of like this part right here of your breast. And that is kind of, you know, it's kind of just, it basically helps prevent cancer from coming back. And then because the way that tumors work and the way that my tumor, not to get too much in the weeds, but my tumors ERP are positive. And that means that my tumor is actually fed by hormones that my body naturally creates for my ovaries and my uterus. So that's estrogen. So my pill that I have to take every day and the shots in my stomach that I had to do was to suppress the estrogen. And so it's essentially when a woman is going into menopause, their slow, their body slowly has a chance to kind of deeply estrogen. And that's the natural process. But when you have something that feeds off of the estrogen, they want to actually do everything they can to remove all the estrogen in your body. And they do it for a certain amount of time until they think that there's no more benefit. And so that's what they did. And so essentially puts me into chemically induced menopause, meaning it's not natural, but by the medicine I'm taking, I'm depleting my body of estrogen, therefore going into menopause. So I didn't get my periods for five years, which is probably the added benefit of this treatment. But it was a long time, it was five years. Yeah. And it sounds like very extensive treatment. You mentioning the shots as well as the pill daily that you had to take. So I can imagine you had a lot of financial responsibilities. So what were some of your financial responsibilities and what were some of your financial burdens? Well, insurance is a huge thing. My insurance actually denied my coverage because I had international health insurance. And in small print, they basically said, well, because your cancer, your cancer actually must have been growing before you bought the insurance, even though I had this insurance for eight months, they essentially found a way out to not pay for any of my treatment. But I didn't know that at the time. And when I went to the doctor's, I would give my insurance card and I got all the treatment I wanted. But then I got stuck with these bills that were actually way more stressful to think about because I didn't have a job in the U.S. My job was in China. And so when you get a bill for $250,000 from your hospital that says you owe this money for radiation, you're like, well, I guess I need to stop radiation because I can't afford this. And of course my parents were like, no way, you have to kind of continue on. And so I wrote financial applications and essentially I had one hospital, the main one kind of right off my cost because I have zero income and I can prove that in the States. But I had other hospitals actually say, no, you still owe this money. And I actually had to... It doesn't ruin your credit. At least it didn't ruin mine for medical. But I had to actually... I had collection people call me and try to get the thousands of dollars it takes to get diagnosed and MRIs and all that kind of stuff. And eventually it kind of got cleared, but involved kind of getting a lawyer to help me understand like how can my insurance didn't pay for it? Like do I owe this money? Is it going to affect my credit? And I would say it was the financial burden of cancer is so... is extraordinary. And it's really something that people don't talk about or even think about. And we shouldn't have to think about it really if we're just trying to take care of our body. But unfortunately the system in America is such that it's hard not to. Wow. I had no idea that not only did you go through your whole entire experience with breast cancer, but the financial aspect was very, very, very overwhelming. Very overwhelming. And I know you just mentioned too that you were unable to work during the course of your cancer and loss of income of course because your job was in China. You're going from being employed, having a constant paycheck to now having cancer and no income at all. Yep. I wouldn't... I wouldn't... I would be homeless if I didn't have my parents to help me. I didn't have a car. I didn't have any income. I didn't have anything. Wow. And I know when we had a conversation earlier you mentioned that not only is it medical costs but there's a lot of other things that come along with having cancer such as buying wigs or other things that'll make you look and feel good. So could you mention some of those other costs that no one takes into account? Yeah, people have to change, right? Like they, you know, their bodies change and so they have to adapt to it. They might have to buy new clothes. They might have to, you know, buy wigs. They might, you know, their hair is different after chemo.  And so your diet also has to change. You have to learn how to kind of cook differently. You might be, you might not be able to exercise as much as you do or even walk. And so there's just different arrangements that you have to make in order to kind of do a lot of times your daily tasks, showers after surgery, right? Drain, clothes that can actually fit drains and that kind of stuff, bras. Now you have no breasts or maybe your breast is lopsided or you need to find padding or you need to find prosthetics to actually with your body. So there's a lot of these kinds of costs that people don't talk about getting to and from the hospital for treatment. Those, you know, again, if you don't have support and it's hard, it's really hard. And clearly these are all things that health insurance wouldn't cover either. No. That's right, right? Wow. So it's just incredible your entire story and what you're sharing because of your experience and dealing with a terminal illness and conquering it and also dealing with a big financial burden. And I know on one of the slides, it says be brave. You're holding a be brave sign. So can you please share what's going on in that photo? Yeah, so that's at Pride and those are San Francisco Pride and those are my Bay Area Young Survivors sisters, I call them. And we're carrying a be brave sign with our friend Janet who's no longer here with us. And Janet was one of the most brave people that I've ever met. She was a doctor herself. She was diagnosed. And, you know, similar to mine got diagnosed again with reoccurrence. And we were training to actually climb Mount Whitney to celebrate our five-year cancer anniversary. And during the training process, she got sick again and she was never able to kind of climb it with us. But we held and we printed out photos and we actually kind of took her with us on our backpacks with a picture of Janet. And she was, you know, again, she was just one of the most one of the first people I met as a young survivor. And then she, you know, after she passed, we still our community is still just forever touched by her. She would do things like throw.  Like she knew that she didn't have that much time so she would throw like a half birthday. So she's like, I'm turning 39 and a half. So let's all come together.  And so that's what that story is about or that poster is about. Wow. And that's just a great reminder to you that I feel we take life for granted at times. Just the small things that we don't even realize like the sun rising on time daily. That's something to be grateful for. I mean, can we imagine if the sun didn't rise in the morning? That's, that's something insane.  And even for me, you sharing that story just a constant reminder to lift. Yes. And in the other photo, you know, your smile is contagious. So what was captured in that moment with you and your pink boa feathers? I think it was just like that was my cancer bursary. So that's another reason to celebrate. I was in the hospital for my birthday. And so instead of being able to celebrate my birthday, I've turned all my birthdays now into cancer bursaries because for me, it's a celebration of, yes, one year around the sun again, but another year that I've survived breast cancer. And so that was my friends throwing me a cancer bursary. It was one year past my, you know, being cancer free. And so every year I've celebrated 12 cancer bursaries and I do it to celebrate, again, not all my birthday, but my life because it's like, like you said, it's not guaranteed. And I've lost a lot of friends along the way. So it's a constant reminder to celebrate life. Wow, I love that. I love that whole transition to the birthdays, cancer bursary. That's beautiful. And I know on one of the other photos that we have, you're holding the certificate.  Oh, those are my radiation therapists. And every day they would see me and they would put me on the table and give me radiation. And by the end of it, you kind of graduate from that treatment and you move on to another one. And so that was the last day of my graduation, basically seven weeks of finishing radiation. And I was able to continue on to go to hormone treatment. How did you feel graduating from your radiation?   And then after you kind of stop, you kind of graduate, which is a great thing. But then you kind of, there can be fear that creeps in. Like, am I going to be okay if I don't see them every day? Because they're used to check, they check up on me. Yeah. That's great. And what is First Descent fundraiser? First Descent is an organization that I got involved in that takes young cancer survivors on adventures to get them in their body. As you can imagine, people kind of feel betrayed by their body.  And so they overcome that or they help us get more into our body by having our body do things that we didn't think that we could do. So taking people on three either you can choose whitewater kayaking, surfing or rock climbing. And those are pretty extreme sports and they help us celebrate kind of the fact that we can go down that rapid or we can climb that wall or we can catch a wave. And then we, you know, essentially they provide a week long free experience and help us kind of emotionally feel more comfortable back in our body, emotionally feel more brave in our body. If we can go down that rapid, maybe we can face the doctors again and that kind of thing. So First Descent is an organization that's dear to me because I was transformed after a week of whitewater kayaking and now I love whitewater kayaking. And how often are these events with First Descent? So they do a fundraiser every year and then because it's national they have small little fundraisers locally. And so I actually had the privilege of hosting your mom and it was a fundraiser a few years ago. And we raise money to hopefully bring this week to other cancer young cancer survivors. Wow, that's so awesome. So you're heavily involved in that organization. Yes, that's great. And what are some of your feelings about your recovery and being a survivor? You know, I was going to mention another organization I'm really involved in which is the Rivkin Center. And with that, you know, I get to I teach Rivkin Center breast cancer and ovarian cancer educational parties at workplaces, at college sororities, tabling, all sorts of different places just to get the word out. And we do it for free and we educate. And that's kind of how I use my survivorship to actually empower people to understand that if you know your body, then you know when something's different. Because I actually felt that lump, I diagnosed myself essentially. And if I can give the education and knowledge and tools to someone else to understand, okay, where is breast tissue start? How do I know my body? What does cancer feel like? What are the symptoms of ovarian cancer or the symptoms of breast cancer? Then I can, you know, use those tools to actually to educate basically and and maybe get an early detection because because I actually felt my cancer myself and didn't wait for the medical system to diagnose me, it would have been too late. I would have had to wait 13 years to get a mammogram if I didn't actually feel it myself, right? And by that time, I might have gotten stage four and I might not have been here today. And so I think education and using my survivorship to educate people, again, is how I've kind of utilized or embodied being a breast cancer survivor. Wow. And I agree with you because it's not like this is a topic that's talked about often, right? I really don't feel like it is. And with the education that you provide and with your story, you can save many lives. So with everything you know now, you know, if you could go back in time before your diagnosis, is there anything you would do differently, physically, spiritually, and or financially? Oh gosh, physically, I don't think I could have done anything physically or emotionally different. I think you deal with things as they come up. Financially, I guess I would get insurance that and read the fine print, although it also feels like something that's pretty hard to do. I would tell people generally to kind of be honest with yourself and kind of and actually do things that you want to do. There are things that I think personally that would have done differently if I knew that I was going to have a cancer diagnosis where I might not live forever. And so kind of being brave in our life and being diagnosed with something kind of scary makes you live. And that's what I would actually tell people.  I would just say go for it and do that. Love your life to the fullest. Yeah, exactly. I love that. And I love you. And I'm very grateful for you sharing your story and having this conversation with me being similar to the age that you were diagnosed. I feel like this is a very important topic. Personally, I haven't gotten checked. I don't check myself regularly. And this is just for awareness. And not only that, but bring awareness about living life to the fullest. That's what I got from this whole entire conversation we had today. Yes, that's right, Sheena. For this opportunity to talk and to share with you some of my story. Well, thank you so much for being on the show today. And do you have any advice for our viewers today for all viewers, not just women, knowing men can get breast cancer too? I would say be an advocate for yourself. If something doesn't feel right, you are your best intuition. So your wisdom is in being, again, your intuition is going to get you to the doctor. So if something doesn't feel right, go and get it checked out and be an advocate for yourself. All right. Thank you so much, Helen, for being on the show. You're so welcome. And thank you everyone for watching. Hope to see you at the next episode of Money Talks. I'm Sheena Park, a Gen Z inspiring lives of liberties. Thank you.


Hello, everyone. I have a quick update about the stimulus payment. The IRS provided a new link for taxpayers who did not provide their banking information in prior years. Simply put, if you filed your tax return in 2018 2019, and you did not do a direct deposit, or you did not provide if you had a bill, you did not pay your bill using your banking information, the IRS decided to provide this link, get my payment, and taxpayer can go to that link, fill out their information. And by doing so, providing their bank information and routing number, this way the payment can get to your bank account much faster than a regular check. But here's what's happening. Some taxpayers, at least I know of two individual taxpayer in person. And I read online that individuals are getting a check. So after you initially fill out the form, provide your bank information, routing information, when you check your payment status. Initially, they say you'll be receiving a direct deposit. Then when you check your payment status, it says, we schedule your check notice your check on April the 20th 24 2020. So rather than sending them the money in the in the direct deposit, they're sending them a check. Now why could be why would be the reason for this? One reason it could be that those individuals that not filed their 2018, that could be one reason, or it could be that the IRS or they did not file that get my payment on time could be one of these two reasons. I'm not really sure. But if you experience anything similar, please let me know. I hope you I hope you'll get your stimulus payment soon. In the description below, you can tell me a little bit more about your experience. If you'd like me to share any information, any experience, please send it to me. I'll be more than happy as it helps many other taxpayers who are waiting to get their stimulus payment. If you are an accounting students or a CPA candidate, by all means, check out my website. I provide accounting lessons to CPA students and college students. Good luck and stay safe during those coronavirus days. Bye bye.


Hello everyone, myself Professor Prithish Chittay working as an assistant professor in mechanical engineering department in WIT, Sallapur. Today we are starting with the classification of milling machine that is our first session of the course manufacturing technology. So what are the learning outcomes? So at the end of the session the students will be able to explain the classification of milling machine and also the types of milling machine. So these are the content. First we will discuss how actually the milling machine will work after that the classification of milling machine that are different types of milling machine and one type of milling machine that we will discuss in this session that is horizontal milling machine. So first of all we will discuss what is being by milling machine. So in front of you there is one schematic diagram of the milling machine here you can see it consists of a work table on which the work piece can be mounted or that can be placed here. So what is the difference between that is the lathe machine and the milling machine? In case of lathe machine the cylindrical type of work pieces that can be mounted in the lathe machine. In the job holding devices like may be a chuck or may be the mandrel or may be the face plate etcetera these are the job holding devices that can be placed in the lathe machine but in case of milling machine irregular type of work pieces can be mounted that can be placed in the milling machine that is the advantage of the milling machine. For example you are having may be the fuel injector or may be the any component of engine of the vehicle that can be placed on the milling machine for the different types of cutting operations. So this is a very much important advantage of the milling machine that irregular type of work pieces can be placed can be mounted in the milling machine. So it consists of the work table it consists of the work piece or the material or the part this is the milling cutter or the we can in the in the simple word we can called as a cutting tool here the milling cutter can be mounted on the arbor yes you can see there is a arbor that is a very a simple spindle that is keyed with the help of a key yes you can see the rectangular or the square key with the help of which the milling cutter that is fixed with the help of arbor this is the arbor that is the a hatching one that is called as arbor on which your milling cutter will be mounted and it is rotating here the work piece or the table and the milling cutter is having the relative motion that is having the feed but in case of you can see the work table or the work piece can be having the movement in the horizontal direction maybe in this way or maybe in this way and also the milling cutter is also having the rotating action like this maybe the anticlockwise or maybe the counterclockwise direction with respect to the direction of the work table or maybe the work piece but in case of lathe machine your work piece or the cylindrical type of work piece that is rotating in the headstock or may be the three jaw chuck and you can take the cutting tool maybe it's a turning tool or maybe the left hand turning tool or maybe the threading tool or maybe the drilling tool nearer to the work piece means only your work piece is rotating it is not moving in maybe the horizontal direction or maybe the vertical direction but in case of milling machine the work table or can be or maybe the work piece can be having the horizontal direction feed in this way like yes to the right side or to the left side now here the work piece is having the feed in the in this direction and also the milling cutter is rotating in the anticlockwise direction that is in the similar direction of the work piece so whenever so whenever when there will be the chip removal process so there will be the question like when there will be the chip removal process or maybe the metal removal process so when the milling cutter will have the contact with the work piece like this yes you can see this portion yes so just I will mark this portion just a minute okay so you can see this portion here so there is a contact between the milling cutter or the the tip of the milling cutter or the tooth of the milling cutter with respect to the work piece so here we can say here we can say here whenever there will be the relative motion between the milling cutter like this and and the work piece so in that case only in that case only there will be the chip removal process there are the different methods of milling like maybe the up milling or the down milling so with respect to that we can called as how the there will be the chip removal process it is in the increasing direction or maybe it is in the decreasing direction so this is the working principle of we can call it as milling machine hope you understand the working principle of milling machine we will go to the next page okay now just give me a minute now here you can see the classification of milling machine there are the different types of milling machine that is divided into maybe the column and knee type milling machine which consists of horizontal milling machine vertical milling machine or maybe the universal type of milling machine hand milling machine yes we are discussing in detail in upcoming sessions that is maybe the vertical milling machine or horizontal milling machine the another type or the another section of the milling machine that is fixed bed type milling machine where your bed or maybe we can called as the work table that will be fixed which is called as plane type or maybe the duplex head triplex head or maybe the profile milling machine after that there is a planar type milling machine after that there is another section that is production milling machine that is rotary type milling machine or drum type milling machine rotary type milling machine where you can provide the rotary motion to the work table also. Yes as we have discussed in the working principle of the milling machine where the job is having maybe for example in the horizontal direction yes the job is moving maybe in the right side or maybe to the left side yes but in the lathe machine the work piece is only rotating here the work piece is having the horizontal direction or it can be having the rotary movement so that you can have the different types of cutting operation maybe you can provide the angle to the cutting operation or maybe suppose you want to provide the different types of drilling operation to the angle yes you can provide in the milling machine there are the different types of special purpose milling machine for example thread milling machine gear milling machine or there are the different types of machine tools like the gear hobbing machine whenever you want to develop the teeth of the gears or the gears, there is the mechanism which is called as indexing mechanism with the help of which you can create the gears, there is a cam milling, the planetary milling or the table end milling after that. Now, there is one question in front of you, listen very carefully, what is the working principle of milling machine that we have discussed already? You can think about this question and just be ready with your answer, what is the working principle of milling machine. So, as we have discussed that it consists of the work piece and the work piece can be mounted on the work table, yes and the milling cutter that is called as the cutting tool of the milling machine and the milling machine can be mounted on the arbor, yes so that is the working principle of the milling machine. Now, the one type of milling machine that we are discussing today in this session that is horizontal milling machine, so with the help of a simple a diagram with some of the animation part, yes you can easily understood, yes what are the different components it consists of, that we have discussed like the work table, there is a feed handle here, just give me a minute, yes there is a work table, there is a feed handle, so suppose you want to provide the feed or may be for example, you want to provide the movement for the work table or the work piece, yes you can use the work the feed handle here, yes that is in this direction, so after that there is a over arm, yes over arm that will be the support for the may be the armor bracket, the arbor is attached to the arbor bracket, always remember that over arm will be having the very much support to the armor bracket and the armor, on the arbor, yes your milling cutter that will be attached that is in the rotating direction, yes this is this will be acted as a spindle, your arbor that is a hollow portion that can be mounted on the arbor, this is the cutting tool or the milling cutter, this is the machine vice, vice is the job holding device, we will discuss the milling attachment in upcoming session, milling in the milling machine, the machine vice is the job holding device, there is a cross traverse handle, suppose you want to provide the feed to the machine vice or may be the work piece, yes you can use the cross traverse handle, the knee, suppose you want to provide may be you want to provide the movement in the upward direction, may be all to the downward direction to the work piece, yes you can use the cross traverse handle and also the knee, there is a vertical traverse handle, yes means you can provide the movement in the horizontal direction or in the vertical direction to the work piece with the help of a knee or may be the cross traverse handle, so these are the references, thank you.


So, Mike, in 10 games you've started seven different combinations on the offensive line. How challenging is that to build chemistry communication when you have guys going in and out of the lineup like that? Well, that's part of it. We know that it's part of this league. That's just kind of what happens throughout the course of the season. Not to say that it's not challenging, but we've tried to get guys ready to go, tried to ask them to prepare his starters, even if you look at Calvin coming from Carolina and just working hard to try to be ready to go whenever his opportunity presents itself. And the other guys, some of them have been here and waiting for their opportunity. So that's kind of part of the deal. You have to prepare as a starter each and every week. Where's Duncan maybe made his biggest strides, and what maybe is next for him? Well, I think we'll see where he ends up at the end of the week. He'll be working. Diller will be, I think, available to practice as he works his way through protocol. And so, probably work Jalen and him over on the left side and work Dylan on the right side. As we start the week off. Just the experience and going out and playing and working through the calls, the silent cadence, the execution, the plays that he thought that he did a nice job on, the ones that he needs to improve on. Just little things. There was a screen where, unfortunately, Peter was downfield early and Jalen was on the back side and felt like he blocked his guy long enough, but then he ended up being a factor in the play and just explained to Jalen that that's, you know, sometimes those are long developing plays and every block matters. You know, even though that you did, you know, your job for the majority of the play, you know, it's a good lesson to learn out there and seeing that guys finish in and being involved in the play and you can help that. I mean, I think that just probably comfort level for Jalen and Dre and Dylan, you know, just, you know, being able to work those combinations and that's kind of how we'll start the week off and, you know, that may change. Impressions of Grace Young, so far? I think that the operation has been good. The command of the offense and that you see him change in protection on third down, quick release, the ability to scramble, doesn't look like it's too big for him, does a nice job of scanning a field.  Well, it's great not to be able to travel and we have one here and we got to give our fans something to cheer about. That's, you know, we have to go and play in a manner in which they're excited about and cheer and support us and help us on, you know, third down and a silent cadence and helping with momentum when we have those types of plays. Beyond just special teams, how's Colton Dowell coming along in terms of knowledge of the offense and being ready to go and play? He's worked extremely hard and, you know, where those opportunities come at receiver, you know, I don't know, but I know that he's gained a lot of, one confidence in himself and respect of his teammates for what he did on Sunday, just in the kicking game and, you know, blocking on the kickoff return as we've talked about that, that's not an easy task and he went back and set up and blocked the linebacker, it was running down the field and good gunner releases now didn't have an opportunity to make a play, which again, that's the most important thing, you know, they were fair caught or kicked in the end zone, but he was playing with some speed and so hopefully that can translate into more confidence and more impact in the kicking game and then, you know, take advantage of the opportunities when they come on offense. What kind of characteristics do you usually face against a Frank Wright coach team? Well, I think they've always been physical, they like to, which the defense is and then, the ability to run the football, the ability to change pace on offense, the ability to, you know, take advantage of the coverage that you're in and try to match up with that, whether that's, you know, zone concepts, spacing, high-low concepts, or the ability to run man-beaters. Well, I think the speed of the length, but also, you know, there is a burst and sometimes he plays at different speeds and kind of laws you to sleep and knows that he starts faster than the offensive lineman do and so there's times where, you know, he'll come in and kind of stop and, you know, they can see and kind of take a deep breath like, okay, he's done and then all of a sudden he'll burst and did that a couple times against Dallas, you know, even on Sunday. So, I think that's probably something that he's probably picked up. He can go up and under, he can beat you inside in the middle of the pocket, but then also, you know, if he feels like he's got it on the edge to be able to bend. Well, it's completed 50% on first down and 70% on second down. Do you have any feel for why there might be such a discrepancy? I don't. I should probably throw more on second down based on those numbers. When you pull those numbers, does that include two-minute, you know, things of those? Yeah. And so sometimes those numbers get skewed when you look at breakdowns of, you know, the two-minute at the end of the half, two-minute at the end of the game. You know, again, I'm not sure. You know, I know that maybe the pressure forced a throw away and I know we had one the other day there with hop and that there was some leakage and I don't think he felt like he could get it to hop and so, you know, kind of dirted it to Derek. That's just an example. Again, I'm just trying to, I think it's all a product of everything in the entire offense and, you know, looking and realizing that it's not all broken. There's some really cool plays in there. There's really positive plays in there. And then just the, you know, what gets overshadowed, I think, even in our minds and everybody's mind is the negative plays, the self-inflicted wounds, you know, the sacks on early downs that lead to longer yardages, which are tough, you know, the snap or the fall start or all those things. But then there's, you know, there's plenty of good stuff in there as well. It just, unfortunately, gets overshadowed. So we'll have to throw it better on first down and maintain, you know, that same completion percentage and that same accuracy and that same operation of protection, route craft, and then accuracy to keep it at 70% on second down. You mentioned Monty Rice yesterday as somebody who's earned more of a role and taken advantage of his defensive snaps in your eyes. What's gone right for him over the course of a season to be able to do that? Well, I've just been, you know, been continuing to progress and I have good leadership. You know, Aziz has played a lot of football and, you know, whether that's Aziz or Gibby and Monty, you know, you can only play certain amount of guys at one time. You know, so we're trying to balance all that as well, I think. And so with Monty, you know, trying to factor in the kicking game and trying to explain to him how critical that is and how he can and help us there. And then, you know, the opportunities that we've given him on defense, he's been able to, you know, be around the football and show up and, you know, again, not just in the run game at a nice play the other day on the on the boot where, you know, he flipped and ran with Ingram and was able to force it in completion. After the game, talk about how you need to feel like he needs to do more, maybe run harder to do certain things.  Well, you know, I mean, I agree with Derek. I think we all and I'd love that attitude. I think the attitude that we all have to do a little bit more. And even Derek, and we have to help him out. We one, we've got to help him out by being able to run more plays, right? We can't can't give him the ball 10 times and have, you know, would be not that he couldn't have an impact. But there's a process to being able to get him those, those carries that then marinate and mature and, you know, have the ability to bust a few and break some tackles. And then we know that there's going to be some, you know, hopefully not too many, some inefficient runs, but we know that over the course of 18 or 20 or 22 carries that hopefully, you know, that we get some of those that pop. And so there's, there's some room.    Like you said, 18 or 20 or 22 carries, he's averaging under 17. I know. How much of a, like is that a core issue for you guys? It's about the volume of plays. And if you, however many of those are third down that you take down out of there and however many are in two minute, you know, that you take out of there. So that number gets to be pretty small. And so we know that to get everybody involved, the efficiency has to be there. The drives have to be there. And I'm confident that it will. Because I believe that if we are able to do that, then Derek can impact the game and so can hop.  And we still like those chances. We're out on the perimeter.    He just, you know, I think he loves football. I think he will do anything that the team needs. And that's what he will continue to do, I'm sure. Always open. I mean, he is great route craft, good feeling, his own coverage.  And just a lot of really good instincts there for getting open and, you know, rarely drops the football. Titan's defense, right? Okay, great.  You know, we saw that a couple times, you know, creep in there when we haven't had success, right? Where it was Pittsburgh and they creased us in the middle, understanding that not to, you know, all the details that we talk about in the red zone, not backing up and being on top and trying to play square and, you know, trying not to let the quarterback scramble. So all the, all the breakdowns that you see, we've all done those things really well when we're getting stops. Like we did on first and second down, you know, they ran the one play with the quarterback Reed and, you know, Arden and, you know, the corner played it really well and we stopped them. And then they came back later in the game and ran the same thing.  So it's, you know, just being able to execute those details and the stuff that we go over, knowing the coverage concepts that we're in and executing them. But that don't need to continue. Yeah, we'd like them to mix it up. Yeah, we'd like to mix it up. And again, being, being a smart situationally, right, and being aware of where you are at on the field, where you're at down and distance wise, situationally, whether it's, you know, end of half and they're in field goal range, you may want to protect, you know, the yen zone, as opposed to coming up and pressing, you know, third and longer and, you know, different opportunities. And again, if you're going to, you're going to press, you know, to make sure that we're impacting, you know, the route and not just giving them free access. And so that that's most important is that when you're going to go up and press, that you're going to impact the release and force him, you know, to be uncomfortable and to disrupt the timing of the route. I want Christian to have whatever opportunities he has. It's going to keep him, his man from catching a football.  And I know that there's been times where guys have caught it in press or off. So I think being able to mix it up, you know, I just, I think that's important as well. I don't know that, you know, what one's statistically better than the other. And then, you know, there'll be some coverages. But again, in man coverage, it is what it is. And you can't have everybody pressed, right? And making sure that we don't get picked. There are some opportunities there when guys are close together. So, you know, that's kind of where we're at there. No, he'll, no, Traylin won't be there. I'm sorry. No, we need to be better in all levels of our past defense. And I'm hopeful that when I say all levels, I mean up front, that we get there a half a step sooner. And in the back end and, you know, that we're either hitting guys to hold, help the quarterback hold it a half a second longer. That's what I talk about impact in the quarterback and the passing game and talk to the players about that. It's not just one group, but there's times where we've had good coverage and forced them to hold on to the football. There's times where we've gotten there and have not forced them to hold the football. And so just realizing and showing where we can put those things together just a little bit better. And that hopefully will lead to, you know, ball disruption, whether it's a tip pass or a sack or a strip sack or, you know, or an interception because the quarterback's throwing it too soon. Thank you. Yeah, I'm not really too close to them personally. But I mean, I've definitely watched them from far. I've been really impressed with this whole process.  It was really fun watching him, you know, compare myself to the other quarterbacks in the draft class. And he did some great things on Saturdays. He's been doing some great things on Sundays. And look, wish him in the breast of this career. Now that you're in a position to take advantage of some opportunities here, compare yourself to the other quarterbacks. Yeah, I think it's really important, especially like playing at this level, like seeing how other guys have gotten it done at this level. It's important, you know, looking at dudes that, you know, might have a similar skill set to you as to what you can do physically. And just it's a copycat league, you know, just like with plays, just with same with technique, you know, just seeing other guys doing different things that can help your game. So that's been that's been fun. What are some of the things that you learned about the position in the NFL playing quarterback that you had had no way of knowing when you were, you know, just working in practice and watching film? I think just how fast things go during the game.  So just the processing of it all on game day knowing that it's a little sped up, but to have the same confidence you do in practice, to see it the way you do in practice and make the right decisions and get the guys rolling. Yeah, I think it started with the pre-draft process. One guy I really liked watching was Joe Burrow. I think he does some great things and just I think physically we're pretty similar. Dax, another one of those dudes, I think he does some good things with their offense and you know, even just watching just their pass game they had against Carolina and what he was able to do and how he operates. There's this couple that I'd say at the top of my head. How much are you looking forward to playing at home? It's been a while for you guys. Oh, it's great. I mean, we undefeated at home.  It's been what, five, six weeks since we've been there. So it's going to be great because this feels better at home for sure. We have a couple deep throws for you in the last game. Was that a great success on two? But was that more by design or did you just maybe not have time to throw? I mean, we ran 36 plays. Like, I can have more opportunities to run more plays, to give the ball to Derek more, to give the ball to Taj J more, to throw the ball down the field more, to open up those things. But when you truly only have seven opportunities to put drives together, you realize just how important, like we talked about, you know, ad nausea is just the little things. 50% on first down to please you percentage 70% on second down. Were you aware of that discrepancy? Do you have any feel for why it's there? No, no, I thought my head I couldn't point to anything specifically now. No, it's fine. No, it's fine. Nothing else to say. Are you putting any extra just with just the snaps and since last game kind of went a little wonky on the way? Yeah, I mean, his misses, if we go back and just self scout, his misses have all been kind of in that same spot and he's aware of that and we're aware that is no error as well. And we're going to make some adjustments just with how we practice and how we play just to help us out with that, just to make sure that that exchange, which is the start of every play is if we don't get that clean, then nothing else can work. So got to make sure that that's clean every time.  It's just with reps knowing how when you get pushed off your spot, how your eyes can't necessarily go to that next read, how you have to move to this side of the field to find whatever routes coming to you. That's just, you know, knowing the playbook, knowing the scheme, knowing where your guys are going to be at certain times. And then if you have an understanding of what's happened in the back end, where those holes are supposed to be and then reacting to that. I think I mean, I've definitely improved things just in terms of coverage recognition and just not just guessing and having a good idea of what I'm seeing out there. I've done a decent job of that. Just got to keep pushing and get better. It's been great. I mean, they get us ready each and every week with all the looks that we could potentially expect. And then obviously telling us that, you know, we're going to get some looks that we don't expect. I mean, you can go back to last week to talk about their technique in the secondary and how we expected them to be handling all these, you know, deep three level concepts that we work a lot. And we didn't get the responses that we had expected. So it's that much more important that we're able to make those in-game adjustments and that these receivers and everybody else knows their rules and what we might be expecting, but how we have to just turn on a dime and just react to what actually happens opposed to what we're expecting. How do you think you've done with that stuff, the unexpected stuff? Sorry. How do you think you've done with that unexpected stuff? Good. Good. I mean, even with last week, like just that second deep shot that we were able to take, like the guys were in the spots that we were expecting them to be. And because of that, we're able to make a play. So just guys continuing to do that. Obviously, it's not perfect. And just with technique and how we're teaching them to do these things, it's important to, again, compartmentalize like what we're teaching, what we're expecting, but what needs to be done to get the point of the play through. In terms of that, as the rate that people are blitzing you, has that been about what you've expected or has it been a little more than when the city extra guys? Yeah. I think we go back to that second game that I played, just seeing a little more pressure and teams realizing that they were able to get to us a little bit. And then we've seen a little uptick in that and just the pressure percentage. These teams, they are what they are at their core. But if they do see things like that, then they might change their tendencies, which we've been able to get ahead of and at least prepare for, which has been nice. But we've done a good job of having the right answers in protection, and especially in third down, which is ways that we're able to handle and just take as much pressure off the quarterback position. Pretty close. Yeah.  I know that they did the same process with the three or four quarterbacks or whatever they brought in, but they were very professional about all of them. And I thought that they were a well-run organization. Not really, no. I went out there for my top 30 and not that they said it in words, but essentially the vibe was, hey, thanks for coming. And then I think it was like two days later, like the reports come out like, well, Lev is reportedly supposed to be number one pick to Caroline. I really wanted to just stand up on top and be like, they actually told me the opposite. But no, I mean, all respect to Coach Reich and all of them, they handled that process with all the integrity and all the right ways that they should have. And looking forward to competing against them. I don't think I'm looking at a specific team like, dang, like screw these guys. I'm really trying to beat up on them, you know, but now it's just internal motivation just as a whole, just how that whole process went for me that was able to just push me forward and just work the way I have like since I got here. Yeah, he's a beast. I mean, we talk about him. We don't necessarily know who's going to do technique wise from his different positions. So just being locked into, he might be here, but you might expect him to be doing this where he might be coming underneath and he's definitely got to lock in on. And I think overall defensively, we're going to be getting some looks that we haven't gotten in a long time from a front perspective, which is nice that we were able to get ahead of it, knowing that we were going to be facing these types of teams. So a lot of stuff that we'd already worked in training camp that we haven't necessarily been able to come back to that we now just kind of got to refresh our memory with and get the guys tuned up on. So opportunities to do a lot of good things against them, got to handle their guys burns, especially being one of them. Quick conversations, post game. Anybody say anything with Baker or Trevor, anybody you talk to, giving any advice kind of going off about how things are going? I think the quarterback wise has just been really quick in and out with them, but I've had good conversations with dudes that I've played with on other teams in college that obviously they're going to tell me what I want to hear, being their friend, tell me that I'm doing a good job, but it's cool hearing just other guys, other professionals, you know, giving you some affirmation about how you play or whatever, not that that means anything, because it all just comes from within and the guys in here. But it's just cool seeing the dudes that you're able to come up with through college to go and chase their same dreams and then laugh with each other afterwards.