The Good Place is honestly one of the best shows on TV. And if you're like me, you're very sad that it just entered its final season. But here's the thing. There's such amazing social commentary in this show. And I feel like it just goes over a bunch of people's heads. So let's talk about it. What is up, everybody? This is Chris from the Rewired Soul, where we talk about the problem, but focus on the solution. And if you're new to my channel, what I try to do is take different topics from movies, TV shows, the YouTube community, try to see what lessons we can learn from them. So if you're into that stuff, make sure you subscribe and ring that notification bell. And don't forget to follow me over on social media, at the Rewired Soul over on Instagram and Twitter. All right, so, couple quick things. First off, if you haven't watched The Good Place, there's gonna be some spoilers, all right? Not massive spoilers. Some might be considered massive, but it's all based on your own perspective. But anyways, if you haven't watched it, you can leave, come back after you check the show out, or just stick around, and maybe this'll make you interested in watching this show, because it's an amazing show. So if you haven't seen it, go watch it.  I've just been binging these books. And I might do a separate video or a podcast episode, just kind of talking about why I feel philosophy and mental health tie in so much, and how I think moral psychology really affects a lot of people's mental health. But anyways, anyways, let's get started. The Good Place is this amazing show, and it's based around like the first season, they're in The Good Place. Main character is Eleanor, she goes to The Good Place, all right? And something that my girlfriend and I were noticing, like mainly with Tahani in the first season, I was like, how did Tahani get in The Good Place? All right, so Tahani, she donated a lot to charity, she did a lot of fundraisers and everything like that, right? But as you kind of start to learn more about The Good Place and you start to see more dilemmas in later seasons, but we call this self-seeking, right? Doing something, expecting something in return. And Tahani, she was only doing those good things to try to outdo her sister and get recognition and all that kind of stuff, right? And by the way, real quick side note, I'm spiritual but not religious, I know some of you hate when people talk about that, but that's one of the things that I didn't like about religion, and we'll be talking more about that in a second, and this is not all religious people, but I think Tahani is a perfect example of, are you really virtuous if you're only doing something for an end game, right? And we're gonna talk about Doug Forset in just a few minutes, but this is something that I always wondered, like if you're a religious person, you're only doing these things to get into The Good Place or heaven, if you will, are you really that good of a person? So, we later find out, which is was the most unexpected twist that I've seen in a long time on TV. At the end of the first season, we find out that they're not actually in The Good Place, they're actually in The Bad Place, all right? And you're kind of wondering, like I think a lot of us wondered that with Chidi. Tahani, I was like, well, no, duh. But with Chidi, Chidi dedicated his life to moral and ethical philosophy, all right? And there's a lot of talk about utilitarianism and deontology, and we'll talk about that more in just a minute. Those two different trains of thoughts when it comes to philosophy. Well, anyways, as the season goes on, right? We see Michael make this shift from a bad demon to kind of a demon who's empathizing more with these humans, trying to figure out what's going on. So, as it goes on, Michael wants to figure out how to get these people into The Good Place. So, he finds Doug Forsett. Doug Forsett, when he was on, whether it was an acid or a mushroom trip, he figured out what the actual Good Place is and how it's based on a point system. So, they go and visit Doug Forsett, and for this dude, for a majority of this guy's life, he has done every single move he can make to get to The Good Place, right? Like, the dude even goes as far as drinking his own recycled urine, all right? He grows his own things.  He does everything he thinks he can to get into The Good Place, all right? So, I was sitting there watching it. I'm like, huh, even though this isn't the same as Tahani, it seems similar to Tahani, because by this point in the show, we've already seen that if you're trying to do something good to get into The Good Place, that's not how this works. Like, what was it? The end of season, one or two, something like that, where Eleanor sacrificed herself and left The Good Place so other people can stay, right? And it was this selfless act because she no longer cared about being in The Good Place. And that's something that we have to think about. Like, are you only doing this to get somewhere, okay? So, as it goes on, Michael then goes to the accounting office, and what they find out, what they find out is Doug Forsett, the guy who has been living his life perfectly, is not getting into The Good Place, all right? How is that possible? And then Michael, he has his epiphany, unintended consequences. And here's a quick clip, and I hope my video doesn't get taken down. Yo, so they instantly claimed my video.  So, he discusses how when humans are making one decision, they're actually making 12 decisions, which can land them in The Bad Place. So, what does this have to do with anything, all right? The conversation I wanna start having is that we all think, all of us in our own mind, this is something, this is a conversation that I've been trying to have, and some people aren't there yet and ready to have that conversation, but in our own minds, we all think that we're the hero, right? But the reality is, we're not these perfect individuals, and we're constantly judging other people, but what the good place is showing us is that none of us are perfect. We're all doing something that could be deemed as morally bad, right? So, when we look at the philosophy, so, Chidi is this teacher. He teaches moral philosophy and ethics and all these other things, and he's trying to teach Eleanor. So, Chidi is very apparent that he subscribes to deontology, which came from Emmanuel Kant, right? So, deontology, that is a philosophy of you do the right thing no matter what. Okay, no matter what, you do the right thing. So, that age-old question, like is it okay to steal a loaf of bread, to feed your family? He would say no. So, it's never okay to lie, cheat, steal, anything like that. But Eleanor, she subscribes more to utilitarianism, okay? So, this is a philosophy of net positive, okay? So, in any given situation, every situation's different, all right, but you're willing to make sacrifices for the best results, all right? So, I guess the question is, which one of those is correct? Which one is correct? Never, ever, ever wavering? Like, I want you to ask yourself this, because I'm not a huge fan of deontology, but I want you to ask yourself this, all right? And a lot of movies have covered this. Think of John Q. Did anybody see John Q with Denzel Washington? His son was dying, needed a heart transplant, he did everything right, and they couldn't get his kid that transplant, right?   So, a lot of us, in my opinion, a lot of us, I think most logical and rational people subscribe to utilitarianism, okay? But I don't think either one is wrong. I think it's on a case-by-case basis. Like, I think it's good to strive to be deontological, right? To always do the best, no matter what, to minimize your lying and all that kind of stuff, right? But it's a case-by-case basis. And what we see throughout our life is not everything is so black and white. And that's why some people argue against deontology, because there are different situations where you're gonna have to do something, right, that might be against your normal morals for the greater good. You see what I mean? So, anyways, where is this all going? I'll start with myself, all right? But I'm kicking off a new series, Will Blank Get Into the Good Place? Because one of the biggest issues that I've seen in the YouTube community, specifically the commentary community, the drama community, is everybody is playing the morality police. And like I said, the biggest lesson from The Good Place is, is that none of us are as morally pure as we try to tell the world that we are, right? And in this day and age, in the YouTube community, think of the commentary channels and the drama channels as kind of where they're counting everybody's points. They're saying, who's doing good, who's doing bad? This is right, this is wrong, all right? But I wanna start pointing it back at all of us. There are so many things that we're doing. So, as you saw from what Michael said, like even eating a piece of fruit now is doing some kind of damage. So, I think this is something that you can learn more about just by watching John Oliver. It's really fascinating. So for example, John Oliver on last week tonight did a whole episode about fashion, right? And we dive in there and you start to realize how much of our clothes are being made in other countries and things like that and they're exploiting children, they're paying people no wages and all that kind of stuff. Like for example, iPhone, Apple Watch, this technology, this camera and everything like that. I don't know who created all of these things. I don't know who made these things. Are they getting paid the right amount? Would I agree with how much they're getting paid, right? This camera that I'm using, who created this? Was anybody harmed in making this? You see what I'm saying? So, we can strive for that as much as possible but another example is, I just dropped my son off and I came back home. I drive a small compact vehicle which is low on emissions but it's not 100% electric. So, even dropping my son off, I contributed to some of the global warming. You see what I mean? So, let's talk about self-awareness. People love to say that others aren't self-aware and I think that is this kind of defense mechanism because most of us don't wanna look at our own faults. It's so much easier to point at other people and pick out all of their flaws and we don't realize everything that we're doing, all right? But at the end of the day, like all we can do is our best. This is my humble opinion. All we can do is our best. We can try to minimize these things. So, to finish this up, yesterday I made a video on Repzilla and he took it very personally, all right? And I don't blame him but the overall message of that was, it's not just Repzilla. It's all of the commentary community. It's all of the drama community playing the moral police and nobody is as morally good as they think they are. So, I am going to start a series and we'll blank, get into the good place and we're gonna analyze it, all right? I'm gonna be looking at different creators who are judging everybody else and I'm gonna ask, would they get into the good place? Are they so infallible that they would get to the good place even though in the show, nobody has made it to the good place in 500 years, all right? The goal of this series, the reason why I'm doing this is, I think if we start to realize how none of us are perfect, we can start forgiving other people a lot easier and quit judging people so harshly, all right? The point of my Repzilla video yesterday was to point out that morality is not this black and white thing, all right?  There is so much that plays into morality. I love moral philosophy and psychology and I don't know, I'm excited to start this series and who knows who I'll be talking about but I think we need to, all of us, need to be taken down a few notches, especially the morality police here on YouTube, all right? But anyways, if you watch The Good Place, let me know down in the comments below because maybe I'll do some episode breakdowns and everything like that because I love philosophy, psychology and all that stuff so to everybody who recommended that show to me, like thank you so much. We binge watched the first three seasons in the last like week, week and a half or whatever. But anyways, that's all I got for this video. If you liked this video, please give it a thumbs up and if you're new, make sure you subscribe and ring the notification bell because I'm kicking off a new series, baby, all right? And a huge thank you to everybody who supports the channel over on Patreon or through buying my books or buying merch and all that stuff. All of it greatly helps support the channel and just even all of you who watch the videos, you help support the channel too, all right? Anyways, that's all I got for this video. I'll see you next time.


In the military, proper equipment maintenance and cleanliness is a readiness priority. Keeping vehicles and equipment ready for action generates many substances that may be harmful to the environment. Left untreated, these substances can damage local screens, ponds, and waterways. To protect their environment, maintenance personnel are required to follow federal, state, local, and DOD regulations and guidance. Sometimes the enthusiasm of the worker to get the job done overshadows personal obligation to protect their environment. And sometimes they mistakenly think that enthusiasm for finishing the job is washing what's not wanted down that drain. Hey, stop that! You're gumming up the works down here! Did you hear something? Hear what? I said, knock it off! What's down that drain? Did you see it? Yeah, I think so. We must be working too hard. I don't believe we're on our hands and knees listening to a... whatever that is. I was once a maintenance officer, actually chief maintenance officer, until I fouled up my oil-water separator and brought grief to the environment. Environment? Well, I thought this was just a drain. A place for all this stuff to go down. Yeah, it's just a drain. What's it got to do with any oil-water separator thing? I think a tour of the oil-water separator is in order for you guys. So come on down! Where, where are we? I think we're actually inside the oil-water separator. Look at all this stuff. I'm afraid to move. I can't swim. Don't worry. You won't drown. I just want you to see what's down the drain. And the best way to learn is from the inside out. Now listen up, Pilgrim. This guy knows his stuff. The job of an oil-water separator is to remove small amounts of oily substances and some solids from the wastewater that goes down the drain. It's not an all-purpose disposal for everything in the shop. This keeps pollutants out of your streams, ponds and waterways and off the shorelines so everyone can enjoy them. Now, really, listen to this guy. He's going to tell you how a typical separator works. The wastewater enters a grit chamber where the water slows down and solids fall out. Then the water flows into a separation chamber where it hits a plate. The plate slows the flow and distributes the wastewater across the tank. Since oil floats, the oil separates by rising to the surface where it's trapped behind a second plate. Down below, the oil-free wastewater flows out of the separator. It may flow into a sanitary sewer where it gets further treatment or it may go into a storm drain and directly into the environment. To work properly, this system must be able to remove substances from the wastewater entering the separator. In our eagerness to clean and maintain, we sometimes let a lot of stuff besides oily water go down the drain. Take note of this list of items that can easily pollute our environment. You must be very careful when using items like soaps, detergents and cleaners or solvent and paint. You must be even more careful when cleaning around plating wastes, trash and debris, used oil, off-spec fuels, lubricants and antifreeze. And really look out for battery acid and the dreaded hazardous materials. Remember, these items, when used without careful thinking, can harm the very places you spend your personal time, relaxing with your friends and family. The oil-water separator was never meant to remove all these items. And when the separator can't remove the stuff, it gets into the water and damages the environment. That's where you two come in. Now listen up. I'm going to show you how to keep the oil-water separator working smoothly, how to protect the environment and how to maintain the readiness of your equipment. Here are the key things you need to do. Keep hoses turned off when you're not using them to reduce water flow. Remove as much dirt as possible from vehicles and equipment before washing. If you must use cleaners, limit them to the minimum amount needed to do the job. Keep corrosives like battery acid and alkaline paint strippers away from the floor drains and out of the separator. Set up recycling containers for used oil. Lubricants, antifreeze and other fluids. This will drastically limit the junk that enters the oil-water separator. Where possible, plug floor drains to keep substances out of the separator. Use dry absorbent to collect spills. Dry sweep floors to limit what goes down the drain. Hey, we're back in the shop. Hey, look. It's starting to work. I'm starting to get clean again. I don't believe it. Look down the drain. You will protect the environment. It belongs to all of us. It's not that tough. Just follow the rules.


Hi, I am Dr. Sanjay Prasad Hegde, senior orthopedic and arthroscopic surgeon, Manipal Hospital Varthu Road. Today I am going to talk about what an arthroscopy means. Arthroscopy is a keyhole surgery in which we make keyholes into the joint and we visualize the joint through that keyhole with a camera. This camera is attached to a monitor so we can visualize the joint in the monitor and through other keyholes we operate the joint with some special instruments and implants. The most common joints we operate is the knee and next will be the shoulder. All smaller joints can also be operated and all other joints can also be operated with these keyhole procedures. We reconstruct ligaments, we repair ligaments, we trim the damaged tissues as well as shave off all the unhealthy tissues with the special instruments we have. Since these procedures are keyhole procedures damage to the tissues is lesser. So the post-op recovery will be less painful and it will be faster. So hence we discharge the patients on the same days. So this will be daycare procedures. Get treated for many ailments in less than 24 hours. Safe surgery means Manipal Hospital because our stars are our doctors. No more excuses.


Good afternoon, Voting Village. My name is Forrest Senty. I'm the Director of Business and Government Affairs at the National Cyber Security Center. And I'm Maddie Gullickson, and I'm the Program Manager for Secure the Vote. We'd like to thank all of you for having us here today. We're excited to have our presentation accepted to the Voting Village. We look forward to future years in our work in elections. So we're with the National Cyber Security Center. We're a 501C3 based out of Clark Springs, Colorado. We were founded in 2016, and a lot of our big focus has to do with cyber innovation and awareness in solving world cyber problems. We work in areas like space, where we actually have a presentation from one of our fellow colleagues in the Airspace Village today, as well as areas like Smart City Technology, like ICS, and K-12, so being the future of the cyber workforce. Our presentation today is about the electronic ballot return standards and guidelines, titled The Future of Voting. I want to start off by talking a little bit about who we are, what the program is, and kind of how we fit into this whole picture. I want to start off by acknowledging that Secure the Vote is a non-partisan, multi-agency, multi-policy group that kind of goes after a layered challenge. A lot of the different things out there with groups like EAC, CIS, CIS, the Election Security ISAC, even groups like Verified Voting, MIT, the Alliance for Security and Democracy all tackle different aspects of our election security problem in the US. And the combination of all of these has led to a brilliant ecosystem in the United States that allows us for us to be able to publish and listen to and advocate for different policy standards, guidelines, whether it be at the federal or state and local levels. And a lot of our focus has primarily been on the ways that we can identify different gaps in critical infrastructure related to elections. So the first gap that we've really identified that we really want to talk about, the reason why we're here today again, is all about this gap where security exists in the conversation of election technology. Security traditionally over the past four, five years has become the even heightened level of focus in the role of election security. So we're not gonna say that we're gonna become the new experts, but the biggest thing for us is all about identifying the critical piece of the future of voting technology. And what it means is that we've identified that security, cybersecurity specifically, is a barrier to the future of election technology. And what that looks like is that if people with disabilities or overseas voters or even the everyday person who might have an emergency come up and they can't get to their mail ballot or in-person voting, that there's more and more calls, especially after the pandemic if you want to do this. But the biggest thing in the community agrees that security is an issue and is a barrier to the future of what these technologies can go. And that's why we're interested in the conversation today. A little more back on us and how we've kind of learned more about this space and why our program was started in the middle of 2018, specifically to work on helping address security issues for overseas voters. Since then, we've participated in reviewing post-collection logs and got feedback from jurisdictions and 10 pilots involving the use of mobile and online voting between 2019 and 2020. And like all critics of online social voting, in every single pilot, we saw the need for enhancement of these technologies. We also saw that there was also increased demand of the pilots we worked in. There was at least two to one, if in some cases three to one and more demand for more places to use it. But the number one reason people chose not to is because of security concerns. So the more we try and understand these technologies and find and understand the different things that address the gap between where we are today, where we are tomorrow, consistently between election officials, the security community and the academic community, we consistently see that these knowledge technologies not going away, but the desire for them is growing and to go back to the beginning, security is still a barrier. So, ready? And through those pilots, some of the things that we have seen that are part of that core security problem are critical need for end to end verification of votes that maintains the secrecy of the ballot, critical need for common standards around voter verification procedures and policies. Again, there's really no federally mandated or even state mandated requirements around these newer technologies. And so there is a need for common standards around voter information privacy procedures as well. And also one of the biggest concerns is that vulnerability of the voter's devices that may have problems on them that could hurt the system and interfere with the vote. And so we really need to have a system in place and standards in place that these newer technologies can be held accountable to. We need pre-election reviews and post-election reviews. We need the same kind of a level of guidelines that are offered through the voluntary voting system guidelines to the EAC. And that's really where we are working with, we have a working group that is looking at these different issues. We continue to look at these issues through the pilots. But ultimately, again, we're really working on these questions because even in 2016, there were about 3 million overseas voters who were eligible to vote, but only 6.9% of them actually submitted a ballot compared to a 72% rate of domestic voters who were eligible to vote. We're doing this because if disabled voters had had the same access that voters without disabilities had in the 2018 election, we would have seen a rate increase of about 2.35 million additional voters participating in the system. Ultimately, we live in the 21st century and we shouldn't accept that people living overseas or with disabilities don't vote because they struggle with access to voting centers or because they lack the privacy to do so. And this slide in particular just demonstrates that technology is a part of voting and it is part of our infrastructure. We have email and fax are already continually used by over 31 states. We have web portals that are allowing people to return a ballot via a web portal. So the technology exists, it's moving in that direction. Again, we just believe that there needs to be a common set of standards and guidelines that can be used to help provide those guardrails as this technology develops. When we look back at our progress in voting, one of the biggest things in the Strives' Home, the point that Forest was making is we see that most of our legislation around voting has had to do with undoing policy barriers that have actively kept people from voting. For the 21st century, what is that gonna look like? It's gonna look like trying to undo the barriers of technology and security as the things that prohibit people from voting. And so, as we look to that future, we wanna participate with as many people as possible and collaborate with as many people as possible to figure out what does that future state of voting look like? What is the timeline gonna look like in the next 10 to 30 years of legislation that we see of technological advancements that we see? These are some ideas, these are some of the things that we'd love to see happen. And we understand the concern about these types of technologies taking place today. But the point is that it isn't going away. And so how do we work together? How do we come together to figure out how to make these things happen? Because we believe that with the collective genius of the elections community and of the security community, we can make an end voter verification a reality. We can make full scale citizen audits of these a reality. And so this is what we envision when we see the timeline going forward and what gets us excited about it. There's with the different organizations that we've worked with, blockchains than one of the ways that people have been able to, one of the technologies that people have used is that the right way? Does it complicate things or does it make it safer? AWS as the secure cloud service, is that the right way? These are the kinds of conversations that we need to be having, not just the binary conversation of it shouldn't or it should, the fact is that it is. And so we have to have that conversation about what this looks like moving forward. And really that's the full circle of where we wanted to come to the voting village, which is really that we want feedback. We know so many of you have thought through these things and we wanna provide that place where you can offer your advice and your feedback on how we can make these things the safest, the most secure, but ultimately the most accessible because that's the whole point of this thing in the first place. And to get really sentimental about voting, I mean, it is truly the better rock of our representative democracy. If we still have significant barriers to voting, that whole piece, the integrity of that institution in itself is undermined. And so we want your feedback. And so if you have thoughts, questions about it even, please email us at securethevote at cyber-center.org. We also will have an RFI that's gonna go live this month for solutions to some of these key issues like we talked through that are associated with mobile or online voting. Voting, so please email us to receive a notification when that goes live. If you've got that next brilliant idea of how you think you can tackle a piece of this. Absolutely. Well, a big thanks again to the voting village for having us. We wanna thank you and just reaffirm that this issue is not just a security community's issue. This goes out to all the different election officials, government organizations, non-profits, and think tanks out there that are all working on this. Whether you're against it or for it is a component of this that will be driving into the future. And if it's going to happen, the best thing we can do is make it as secure as possible. So thank you. Hi, this is Colorado governor, Jared Polis. And I wanna thank everyone involved with this effort to secure the vote. Voting is the most sacred right that we have in America. It's the right that protects all of our other rights, which means that we need to do everything that we can to safeguard voting. I'm proud that Colorado has been a national model for voting rights. With our all-male ballot system that guarantees paper trail for every vote, same-day registration, and so many other protections, we're not only recognized as one of the most secure election states, but one of those top states for voter participation and turnout as well. But we can't rest on our laurels and our past success. We need to continue to meet the challenges to today and tomorrow, which is why I'm proud. The one initiative led by the National Cybersecurity Center started right here in Colorado to secure the vote pilot program, where over 4,000 Coloradans used a blockchain secured mobile voting application to cast their vote. That program from Denver has since expanded to six other states and now includes other technologies to also secure our vote and empower voters. Free and fair elections are the bedrock of democracy, and we need to work together to protect the integrity of our elections together. Thank you for your work on this critical and important initiative to make sure everyone has confidence that their vote will be counted. Good afternoon. My name is Jocelyn Baccaro. I'm the director of elections for the city and county of Denver, and I want to thank the National Cybersecurity Center for the invitation to be a part of this video. I am here because COVID-19 has highlighted the need for more options for voters to vote safely and securely, particularly voters with disabilities. Many states already offer some form of electronic delivery and return for some voters, but unfortunately, these voting technologies exist without robust standards for safety and security. This crisis has shown why we can't wait. We need all levels of government security, policy, and technology to join with election officials to establish better standards and guidelines to implement new technology solutions so all voters can vote safely and securely. Thank you so much. Hi, my name is Amelia Powers Gardner. I'm the Utah County Clerk Auditor, and I'm here to bring you a challenge, one that I'm confident you can accomplish. As you know, this week we mark an important milestone. Astronauts safely return to Earth from the space station for the first time aboard a private vessel. Add to that the mere fact that we have put men on the moon can 3D print internal organs, and there's even emerging technology that can edit DNA. Technology has radically transformed the human experience and solved a great number of our challenges, both large and small. It's time to start finding voting solutions for the 21st century. It's no longer acceptable to suppress votes of entire demographic or to accept low voter turnout because of weather, natural disasters, or a pandemic. Mobile voting is the future of elections. Upcoming generations demand it, and our current generations need to embrace it as a solution to age-old problems with voting. Our current voting methods require extensive logistics and cost a lot of money while still failing many voters, including those with disabilities, those with lower socioeconomic status, and our men and women serving us in the military. It's time to stop saying it can't be done and it is time to start finding a way to do mobile voting. The industry needs to create standards that innovators can strive to accomplish and that election administrators like myself can use to judge potential solutions by. Join me in improving the way we do democracy in the 21st century. Thank you.


So I'm so glad to be here and in front of you, I'm so happy to be here and to go through this baby step process of going back to normal, because I personally love being part of conferences. That's where I think that people should connect and link to each other even though they're just maybe from different parts of the world. So I'm glad you're taking some time and coming here. So a little bit about us. So my name is Andresa and I know it's difficult to pronounce because it's an Albanian name. I live in a place called Kosovo and I'm a software developer. This place is based in the Balkans. It's in southeastern Europe specifically. And you will see these two markers up there. The red one up there, it's WeTech. It's our company, which is the business which provides the software solutions to international customers. And they are web-based mostly. And the other one down there is Koder Girls, which is a community based and present in our hometown. We started this community like three or four years ago when we were part of our college days because it was so hard to travel like from place to place to even be there physically on job interviews and other stuff or participate in tech industry. So we started organizing events, hackathons, conferences based in open source. And we try to have a glimpse and gather people there in one place so they can know what this industry means and how important is open source. And yeah, the other speaker. Hi, everyone. I think this one is working. So yeah, I am Albiona. I'm Andresa's sister and we are here together to attend the open source summit for the third time, organized by the Linux Foundation. And we kind of started a super basic three years ago. We were organizing events by Koder Girls and we were like studying and getting hands on the professional careers. So I am a DevRel and a full stack developer based in Kosovo. And today, I think we are good to go with our topic. But before that, you can find us on GitHub on the links that are here. And we can kind of start with the presentation. Yeah. Sure. So today, we are going to talk more about the cloud native and we will be focused on the cloud native architecture as a whole. We'll be continuing on cloud native services. We'll be talking about serverless and what serverless means to us and how serverless has changed the way developers build applications. We'll continue talking about the serverless framework. And we also included one of the functions as a service providers here. So we're taking an example of that later on. We're also will be having a glimpse of serverless anatomy on our example. And by the end, we'll be able to see how to build a scalable API using serverless with some basic configuration files and deploying it later on. Okay, then we will start off with the fundamental into the cloud computing before continuing on the, let's say, the best components when it comes to the cloud computing architecture. Cloud computing gives us the option to have our IT infrastructure, let's say, based on somewhere else kind of as a utility. And that's because up until now or super late, we were like handling everything ourselves and that means owning the servers and managing the IT and, of course, the real estate for the servers. But when it comes to the utility or as a service, having the cloud computing be part of the different companies who are, who function as a providers to us, it's basically easier or it has different advantages on computing or building up different projects. And these are kind of three basic or, let's say, overall advantages of the cloud computing and those are the lowering, the total cost of ownership because if we are kind of getting all of these services from somewhere else, that means we will be focusing more on our business models and kind of providing the solutions to our clients. And then the agility and the skill and performance when it comes to the demand of our users. We will continue on the best parts of the, not best parts, but the parts that we chose to talk today about the cloud computing architecture, but we will note some kind of definitions from different resources and one of them is the Linux foundation where they put together this definition about cloud native computing which uses an open source software stack to deploy applications as microservices where each of the parts is packaged and I'm sorry for the voice, where each of the parts is packaged into containers and that goes together with all of the orchestrating all of these to manage the resources or the utilization from these providers. We will focus on the containers, we will focus on the dynamic orchestration and on the microservices part. So the containers, when it comes to the containers, they are packages of software that gives us the opportunity to package our code and the dependencies and that we can, together with the container tool, we can run all of the things that we have in our application in any environment depending on the, depending on, it depends on the tool that you are using or the cloud service, let's say the private cloud or the public storage and things like that. When it comes to the, yeah, let me just check something. So when it comes to the containers, the Docker kind of is a tool that provides you with the container functionality and they say that, let's say the container is a standard software tool that packages up the code and the dependencies so that the application can run quickly on any environment or any computing environment in different parts of the, let's say, world. When it comes to what they offer is that they offer this Docker image which is a lightweight standalone package that will provide you with all of the necessary things that you need to put up your application and that is the code, the runtime, the system about the libraries and the storage as well as the settings. The containers allow us with their lightweight packages to kind of put together the code with all of its dependencies and we can focus on the things such as the versioning of these dependencies and the language runtime versions as well that are required to set up and running your application anywhere. When it comes to the differences between the containers and the other part that are the virtual machines that provide you kind of the same solution, those differ a lot between because containers are an abstraction on top of the app and that gives you the opportunity to work with just the code and the dependencies but the operating system kernel layer is based there and you can use a lot of containers to, on top of that operating system layer and that means you'll have the opportunity to have more space or have your package super small to run it everywhere whereas the virtual machines are an abstract on the physical hardware layer and that means that each, let's say, package or container for virtual machines will have their own operating system, the code, the dependencies and that makes it super heavy when it comes to the storage. So the three benefits for containers are the separation of responsibilities and that comes up with dividing the teams of development and the IT where the development team can focus on bringing up the functions or the features of the application, the logic part of it and depending on the IT, like, depending on their own requirements to meet the business logic side and when it comes to the IT team, they can operate on their own to set up all of the necessary, let's say, configurations so that this application can be up and running and they don't have to kind of mix things up and it comes to the versioning and other details. The workload probability, it comes with the, let's say, containers can run anywhere globally in that means to the private storages or to the public cloud providers or your own based on laptop where you can set up the container and run it everywhere. So it's like, it's super easy for developers to set up and going with the application and to focus more on their kind of priorities. And then the application isolation and that is about the container, containers visual, virtualize the CPU, the memory storage and network resources that makes it, but it comes to the, providing to the developers with an overview of how the operating system logically is connected with everything. And then we have the dynamic orchestration that is a pre-integrated solution that enables service providers to launch out of the box business logics or business use cases that leverages both the physical and the virtual network functions. These are all come to one place of enabling the quick to time to market focusing on the optimizing the costs and providing the solutions to the target users that are behind the scenes when it comes to the solution itself. The components for the solution include the VNF visual network functions onboarding that is quickly on board and validate multi vendor VNFs on the service provider environment. There is the end to end orchestration, element management, assurance and the inventory. This is when it comes to the kind of a lot of, a lot of services, let's say, or these set up out of the box business use cases can leverage each other's services or features because they are set up in a place where it's easier for them to be connected and kind of to share the resources. And about the microservices. So the microservices are an architectural approach to the development. When it comes to the having all bits of the system set up, it's like every part of the function of the application is set up into different services. And that means each service can have its own team that is focused on prioritizing their goals, let's say, or development features, when it comes to their kind of end solution, dividing the front end, back end, storage, all of these are set up on their own. It's like small bits of projects that are connected into providing a bigger solution. This architecture makes applications easier to scale, faster to develop and enabling innovation and accelerating time to market for the new features. Comparing it with the monolithic architecture and the microservices, the monolithic on the other side, it has all of the, let's say, parts of the application together in one place, making it easier to, making it harder to scale because based on the new features, let's say, it, all of the code base will have to be changed if it needs to be kind of another feature developed. And that is super dependent on every part of it. It makes it super complex code base and it's super hard to later on to kind of scale in this way. And that's where the microservice architecture comes in, where the application is built based on the different components that run each of their processes separately without depending on each other. And they are kind of connected with the lightweight, super defined APIs to send and receive, let's say, requirements from each of these services. We will go through the cloud computing types, starting with the infrastructure as a service, then platform and function as a service on the cloud computing providers. The infrastructure as a service, so it offers the user the option to use all of the services when it comes to the networking and storage and servers. Basically you will need to set up everything when it comes to your application and platforms and the infrastructure parties will be handled by the providers in this case. Some of the advantages of it is that you will have to pay what you are using when it comes to the computing part. It's scaled dynamically and it has a part of the security set up because another part of it is not that because it goes down to the availability in this case because based on their own, the way, how they work, you will have to be kind of dependent on that side for the availability. The challenges are the lack of support from their kind of teams of these services, the integration is kind of complex and the processes do change because it depends based on their development roadmaps. When it comes to the platform as a service, it is a cloud computing offering that it provides to you the opportunity to set up all of your platform and application in this case to the cloud. It comes up with pre-built tools that helps you to develop and add new features easily and test these applications. In this side, when it comes to the advantages, they are cost-effective. It's time savings because this way you will kind of have it free to kind of build up an application idea that you have to see and test things out and then you have the security as well that is increased and you have the flexibility to kind of iterate through different versions of the applications and platforms you are developing. And then the challenges of platform as a service, there is a lot of security risks because it all depends on the cloud provider that you are kind of using their services. You don't have to, you can't have some kind of hands on to change things or to update things. It's the compatibility, the vendor dependency, and then risk of lock-in. And to the other type of cloud computing provider service types is the function as a service, which is one of the most, one of the famous types of cloud computing because it allows you to set up small building code snippets to kind of set up and running whenever you have events. And that is super cool because all of the other parts you will have to manage to yourself. You don't need to depend on about the computing storage and things like that from different other services. And here the advantages are that you have improved the developer velocity. It's built in scalability depending on the usage of these functions. It will scale and the cost is efficient because whenever those functions are set up and are used, you will get to pay only that time. The challenges are that it's less system control and it's a more complexity required for testing. This is when it comes to the types of cloud computing services that we chose. And for the next part, we will continue with the serverless. Okay, great. Thank you everyone. Back in the day when we tried to build applications, we needed to take care of some processes before going to the most exciting part, writing the business logic. And we had to start on the bottom layer, which was the hardware layer where the storage of the computer and everything was stored at. And then we needed to move to the virtualization layer in which we needed to have a single running operating system. But we also needed to create virtual machines to help it horizontally scale. The upper layer would be the operating system, which I'm sure everybody knows what this means to us and what this matters, which is a software that helps us run the programs that we would need to work on. And I think the most important layer, which would be the runtime, because this will help to put on work the operating system and the application layer. So after that one, it comes the most exciting part that I was talking about earlier, the one where we could write our business logic and we could maybe form teams to design, to build and deploy these applications. So based on this, all of this would have been like the exact process we would go through if you would plan to work on an application, which would maybe solve an existing problem. By that I mean, imagine you're working in a startup and you're trying to launch that product as soon as possible. But at the meantime, you're like the first person you're doing all the job in the background. By that I mean having to take care of your infrastructure, code, management, sales and everything else. So that's why by this, they started to emerge some cloud services by some of the famous that we already know, let's say AWS, because that's what we're using for our next example. So they just started to focus more on making things efficient, like the services that I've been on mentioned. And all of these networking storage were just removed from an extra resources because they were already started to get some help from these outsiders from the cloud services providers. And then we started to just accomplish a more, maybe not manual way of building those applications. So all of these services that we mentioned, the most important one I would say maybe is the last one function as a service which is a kind of cloud computing service that does not require coding to a particular framework or library is just a function that lets you focus on that. And that function is just abstracts the application and it makes you build an individual component which makes the whole application. So what's serverless bringing to the table? I think that this is what makes it special because the deployment is very different from the traditional system since we do not have server applications to run ourselves. It's just that we upload the code into one function and that function is being taken care of a service provider and then everything else is all sorted to somebody else and it just continue to do everything else in the background, all the necessary things including provisioning and other stuff. So when we say that we include serverless into our applications, sometimes we don't have a clear view of what that means but we can focus on two main areas that will explain better of that term. Serverless, when we hear of this word it doesn't mean that it doesn't include servers in the background, it does actually but what we understand is that someone else is just taking care of that behind us. So another term that would use to describe it is that serverless would be third party cloud application and services so we can manage the logic application like single page web apps or mobile apps that have cloud databases. Another one way to think of this is the function as a service because as discussed earlier, because now we do have like many platforms that offer this service as you can see there's lambda function from AWS Azure functions and Google Cloud functions. So right now we will be focusing more on the AWS lambda that's what we chose for the examples. What lambda does actually is just you can run a code virtually on it. It might be of any type of application or backend service. Each lambda that you create contains the code that you want to execute and everything else that happens in the background that we'll see later. So there are two ways that you can create them. You can use a AWS console but before doing that you need to have an AWS account with all its proper credentials so you can have a proper function of the lambda and the other way of creating it is through using serverless framework. So you just can go through the dashboard when you can create the function and just within your service and then continue to work on that or you can just use the terminal to log in through terminal with a single command in the serverless framework and then create that function that you want to just continue working on that. So while we're here we can see and we can like appreciate how much a serverless framework is helping us and what is offering to us. All of the things that were explained earlier such as defining your applications or your functions and your events, it's like too easy right now. Deploy infrastructure, it's too easy as well with one line command or using plugins that would make your code or your deploying like very simple and many, many more which is offering right now. So we will jump right now into anatomy of serverless so if you're thinking of building an application which will include serverless within that, you would need like it's a must that you would include a serverless YAML file inside that application and there's, I mean there's a lot of resources so there's a file, it should be a structure to write on that file. But some of these attributes are a must. So the project right here that we're going to try is starting with the organization name, in this case it's my name and I was trying to build an e-commerce so I can include serverless in it and the app name should be included as well which in this case is you really store and the service name should be included here. We've talked about plugins that we've, if you would need to like make anything easy to deploy or to work on your application you just include it in your serverless YAML file, in this case it's serverless offline that we needed to include and also the providers that we mentioned earlier we used AWS in this case so we've included here name of the provider and their runtime version, stage, whether it's development or production, region of that function that you've created it in that provider and this one right here is the role statements because I've used DynamoDB to store my data so there's some configuration steps to include that here and also the environment variable which is my table name. So the function that we've talked until now you can just include them here as well if there are some resources that you need to get or add the data but in this case since the application will grow and it will just make the code immense I've just added it into a separate file which is called jewelry.yaml and I've just included the functions right here. Also I've included the resources file here which is the configuration of the data table that we're using on this example and the last one should be .env because as I said you need to have the proper credentials to create a function in AWS so they would provide you the access key and secret access key and other stuff you can include them in your JS files or anywhere but I just added an .env file and I just called them here. So this is one way of including functions and events when you're trying to build an application with serverless so the file that I included here into the serverless is the same one which includes the resources here and so I've just added a screenshot with two of them it's a jewelry which is the name of the function and then the handler which contains the path of that method and you can include the timeout so the important part of that is the events so you can have the HTTP method and the path here in this example it should be a post request with a path of jewelry so the same thing goes for the other function is just it has another purpose by getting all jewelry that we need. So the other picture is a screenshot of the resources file so this part maybe goes more with DynamoDB structure which I think maybe we should do another section of that but it's just a little bit a basic structure where you could have the name type and the properties with the partition here in the sort here that table and of course the name of that table. This is the way of so this method that we've used where we could call the lambda function and a way we defined a method where we could just get an item and return the result or even the message if it fails so it's just a basic one we would use everywhere. So right now let's see I have an example here which I made it beforehand because of the time so all of the picture you saw until now it's based on this project which is a public repository and my GitHub you can find it there if you want to build an application and you can just set up a server less it's easy and it's like a boilerplate you can use it and you can just add more features on it if you want to so there's an SRC directory where I store my services and inside the utils I store my response messages and the credentials and I call the file with AWS credentials this is the service where I store my resources and the most important part is the serverless folder where I include my functions and then all of these functions are called here in the serverless YAML file so right now what I'm trying to do is that I should be these right here would be basic CRUD functionality where we would be able to add, edit, delete or get some data for this project but what I have not included here is the get method so we're going to do it right now I'm just going to copy and paste it right here so we can see it what happens and this is the place okay this should be in my service right in the current here and so this should be a basic function to get all of the properties here okay this is this should be the proper way now that we've added everything we've needed we can just go and write this simple command to deploy the changes that we made I hope that everything will go as planned so right now it's doing all of the stuff that we've discussed until now in the background it's just continuing to deploy these resources and so we can try them and test them how this works like internally while we're here what I show you what I did so I opened an account as I said I think you should fix the region here it's US okay so I've used DynamoDB to store my data and I've added a table here which you can see it's named serverless presentation example and we can view the items here so I've had at the moment like three products one of them should be yes one of them should be this one because I've added it one before five minutes before the presentation and its name should be Linux now we already have all the resources to test this crowd functionality we've added just the get method okay I think it's done so maybe we can try it here in the terminal but you can try it using any tool you want like postman or insomnia I'll try it here and see if it returns my data yeah it's here so every so the whole object is here as you can see it in DynamoDB and it's working so it's just a simple a very simple step to deploy your application and test it and then see if everything goes as planned so I'm continuing on this slide so based on that we need to do a more debugging when it comes to that but based on community and lots of developers there's a lack of resources when it comes to debugging because what lambda returns you there are many times there are errors when you just cannot understand those information but it still depends on the type of error you get so if you get a syntax error maybe you could just enable serverless debug and then continue using that but if you get another error it just depends on what tool you're using or what the kind of error that is another way of monitoring them is using AWS console so you have there's cloud watch there and it's a platform it's a actually very powerful platform where you could see a way of visualized way actually all of your data all of your logs there so you can kind of get a hint what's going wrong or if it's working properly and things like that this what you're seeing on the screen is the dashboard of the serverless framework where you also can use it as a debugging tool right now I'm seeing my dashboard for my service and you just can use it for different purposes like I've wanted to know more about the API requests and errors in the period of time for example for the last seven days and yeah it's super helpful so I know we've talked a lot about serverless and the benefits that you could have by using it and including it in your applications but there are drawbacks and challenges as well when you try to work with that so some of that you can see on the screen but there are many of that many of them that there are not included here let's say when they're locking so when we say that we use service provider to help us do all of the things in the background we just put our faith in that and we just play by their rules so it's one of the challenges and one of the cons maybe that we have to deal with it when we start to or when we decide to include serverless in our applications another maybe cons that would be it's that if your application it's part of your AWS service provider it's not that easy to just port your application to Azure let's say or another cloud service provider so that's one of the cons that I would say it matters and like anything else in technology we must consider the security factor because when it comes to serverless as I said about the vendor lock in it goes the same thing with the security everything falls under the cloud service provider and not the consumer and also despite all of the documentation and the community and other stuff it's still hard to find the learning curve that you need for to maybe migrate or to start something from scratch using serverless because it's quite a challenge to work in that and start doing things with that and many many other things like you need to have a significant mindset shift and it's also like the every time would be the lack of local testing options as I mentioned earlier and many many things so yeah these are some references that we've used to work on this presentation so this presentation is uploaded on Sketch I would kindly invite you guys to view it because the first links are very important to us and it will show you what we're doing in Kosovo and how important open source is to us and what we're trying to build you can see them all there and the links down there there are representation resources that we've used to work on this and to build this application or this presentation that we would present today so yeah this is it and you're welcome to ask questions if you have any and talk to us for everything that you need thank you for your participation we really appreciate you taking your time to get here so thanks oh we're also as I said that we're trying to go back to normal we also want the bid to organize Debian conference in Kosovo it's the first time that it's being organized in a country in the Balkans or in Europe at least because they already choose with places eastern or somewhere up there so if you're a fan of open source and you want to know more about Debian we're also contributed to that part so you can come there next year and or talk to us that we can help you so yeah oh yeah yeah I'm I don't really have much experience using other cloud services I've read something about the company that I've used to work with they used Google functions and they are basically like they had the same issues as we as you would have in AWS or another like cloud service is just maybe AWS with it has actually the best documentation that you would need to work with that and to maybe develop that application using serverless because it has even the community is very like sophisticated they just hold events they organize talks about how can you set up a Lambda function and how can you use it with other application stuff but yeah I think I think it's basically the same issues in all of the cloud services providers thank you yeah I actually have one of that here in my in my links here I think it's called only serverless serverless architectures with AWS Lambda I can share with you too it's one of that it's also I don't know the author of that but it's about the micro services and cloud cloud native I'll send you the link so it's just describes in details how can you use this and how can you approach build the way of building application using serverless the other one I've used I mean no the other one it's more of for the DynamoDB it's by Alex debris DynamoDB book but yeah I can share some of that with you so they're pretty detailed yes but yes some of these are the main ones that I've used okay yeah okay nice okay so if anyone doesn't have any questions just call it an end so thank you again and let's be in touch