Hello, Minecraft community. I am Joshua Montgomery, the founder of Minecraft AI, and I am here to talk about all things Minecraft. We are doing a bunch of new things that are fun and I'm here to talk about them. So anyway, without further ado, it is a bit weird talking into my computer with nobody else around. You can see I'm here in the workshop. There are 3D printers and lasers and drones and all kinds of smart speakers right up here behind me. This is my preferred place to be working. As much as I like the office, it is nice being in a place where you can get up and actually do stuff during the course of the day and other than send email and talk to people on the telephone. Anyway, here I am. I actually just got done printing a cooling fan for a project of one of the printers behind me, which I might get out to clean up mid YouTube live. So anyway, so I have a couple questions that I'm supposed to talk to you about and answer. I think we're going to be doing a lot more of these in the near future as we work to better engage the Minecraft community. One of the things that's been really a blessing for the company and the team has been how wide and broad the community has grown over the course of the last six years as more and more people download and install Minecraft on their Raspberry Pi and on their laptops and, you know, on their Plasma TVs and, you know, all these other applications, whether it's Chatterbox or LumaCube or Cubo, the robot, you know, all without us, you know, having to do a big heavy lift on the community building side. Someday, I think we will have folks that travel around the world and just build community. I'm reminded of the folks at SendGrid who used to have a representative at pretty much every startup event that was going on in the U.S. and abroad. You know, it was their job to go to all these startup events to pay for, you know, parties in the evening and then to drink with founders. After talking to a few of them, it was pretty clear that their livers got a little damaged during the course of that career. But it did certainly help SendGrid to engage with a lot of startups, ours included, to help them send email. And I think that that's probably in the future, maybe minus the liver damage from Minecraft as we get closer and closer to being able to drop the technology stack into anything from a Kubota tractor to a you know, a SpaceX space capsule and start looking at ways to engage with all of these companies and getting the voice assistant on to them. So, so anyway, so let's start with some questions. So easy one, right? What does the Minecraft logo mean? So, you know, the original Minecraft logo, the O in Minecraft was actually a speaker grill and you know, the whole idea was to really tell the story of our company as a as an audio technology. Since then we've we've made a change. We've got the little O with the half circle and then we've got the hexagon around it in the in the larger logo. And we've got some really specific colors and fonts we use. You know, the the purpose of the the new logo was to make it easier to animate and easier to to tell the story of the technology. We wanted it to still be sort of speaker like but we wanted a bunch of components in there that we could flip and spin and change colors and and really engage with with our customers on and also something that looked nice in two color. I'm a big fan of logos and branding that involve the fewest colors possible because it makes it a lot easier to print those brands on t-shirts and on devices. So, you know, so yeah, the the Minecraft logo came from a design study that our design team did in the summer of either 16 or 17. We had three or four industrial designers some from the University of Kansas some from the School of Art and Design in Ohio. And they all came together and helped us do a lot of stuff around, you know, building the animations for the screen but also around branding for the company. And so, you know, at the end of that process we were presented with four or five sheets that really encompassed the colors and the shapes and the designs of the the logo and the fonts and and at the end of that we settled on the the logo that we use today. And you may have noticed that the catchphrase under the logo has changed. You know, we used to talk about being the open voice assistant and now we talk about being the private voice assistant. I think that that in many ways we still are open and and always will be right. So the source code is available online. The you know, you can download the stack and run it independent of us. You know, we even provide instructions for for standing up your own version of the Minecraft backend Selene. but you know as the other technology companies in the space started to open their stacks, meaning that they made them more developer friendly and provided APIs didn't really, you know, in many ways, they don't provide the underlying tech, right? They just allow people to access it. I think that that ceased to be as important a component of what we were doing as the privacy aspects of what we were doing. You know, the at the same time the technology companies, you know, kind of pseudo open their their source code or pseudo open their platforms. You know, they have a tendency to shift their focus or or to to focus on growth, right, to be the biggest player in the space. Even if that means that they're given the technology away for free. And, you know, the the way that they get paid for that is of course by by selling, you know, the eyes and ears of the people using their tech.  And so as the the other technologies in in the space became more and more focused on growth and in adding users and being accessible, maybe not open, you know, and then began to focus more and more and more on, you know, figuring out ways to monetize those users, you know, either by by learning their behaviors or selling them products. You know, the the privacy component of what we were doing became more and more and more important, right? You know, especially for a technology that is always listening that is is sitting in the corner of your kitchen and can see all and hear all within your home. You know, privacy becomes really really important and you know, we've been I think we've been doing a good job telling that story and and you know, openness is definitely a big component for privacy, right? Like I can tell you I'm private all all I want, but you know, unless you can see the source code that we're running, like how do you know that we're not violating people's privacy? So, you know, being open goes hand in hand with it.  How are we different? And you know, the answer to that is, you know, not only are we not spying on on you for other people, right? The way that some of those brands do, but we're not spying on you for our own edification too, right? Like, you know, some of those those speaker tech stacks, you know, they advertise, we don't sell your information to anybody, but of course, they're using that information internally to sell you their own products. And we do none of that and and so, you know, adding that private voice assistant tag to the logo really helps, you know, us to communicate, but then also helps us to remember that that's really the focus of the company and that's the, you know, the underlying ethos to what we're doing. So anyway, so anyway, a couple questions out there from the the YouTubers out there. So here's one that's it's kind of interesting. Why did we choose Michael Lewis to be your CEO? So for those of you who have been following the company, Michael joined the company in January of 2019 as the as the CEO. No, I'm sorry, January of 2020 as the CEO like two months before the pandemic started and and, you know, I gave up the CEO hat and and really wear a founder hat.  Talking to our customers, talking to investors, talking to partners, talking to the community and listening to the community. And so, you know, Michael put on the operational hat, which he's had at a couple of a couple of other companies and and I've said this before, but I'll say it again, you know, as the founder of a company on day one, it's you and maybe two or three other people around you. You know, when we founded Minecraft, you know, it was me and my co-founder, Chris Adair, who's also my wife, Ryan Sypes, who, you know, was doing projects in our in our maker space and really was plugged into the local Linux community. Derek Shweppy, who helped us with our original Kickstarter.  So, you know, in Derek's case, you know, he was doing design work and helping us with all the enclosures and things that you see behind us, but he was also helping with video production and branding and a series of other, other, a series of other tasks within the company. You know, Chris Adair was playing the role of social media maven and marketing and running the Kickstarter campaign, but was also doing all of the bookkeeping, for example, and, you know, handling a lot of the overhead and supervisory work. You know, me as the CEO, you know, I was working to help tell the story and writing copy for the website and you know, working to find investors and working to help manage cash flow and making decisions about technology.  And your, your goal as an entrepreneur, as you grow your team is to look at each one of those tasks that you're performing and to find somebody who's better at that task than you are and to give them that hat, right? So, you know, for the CFO role, you know, finding somebody who's fantastic at, you know, as a controller and a fundraiser and giving them that hat for, you know, the technology development side, you know, finding developers that are really great at, you know, database stuff or finding developers that are really great at front end stuff and giving them that hat. And then taking them all off, you know, one at a time and in a perfect world as a founder, you know, your goal is to have the business that you're building or the project that you're building operate without, right? Like, there's nothing that's more limiting to your freedom than, you know, being the essential cog in a business because you can never go on vacation. You know, you're always kind of saddled with whatever hats you're wearing. So, you know, as that business grows and as it becomes more successful, the goal is to take those hats off and give them to somebody else. And, you know, in early 2019 or late 2019, early 2020, you know, we were having a lot of challenges. You know, mid 2019, we made some pretty substantial staffing changes because we weren't really happy with where we were on the technology side. And despite the fact that we were doing okay financially, it just wasn't clear to me as the CEO that the team that we had was going to take us from where we were to where we needed to be. And that wasn't the fault of any specific team member, right? It really came down to something that was almost undefinable, right? And so, to really push the software that we wanted to push out to get the hardware out that we wanted to get out to get something out that really met the needs or helped us to achieve the vision that we created when we ran the Mark II Kickstarter and developed the Mark II feature set, we needed to make some changes. And so, between the summer of 2019 and the beginning of 2020, we limited the team to a very small number of people. We took a daily stand up, you know, we set really achievable short-term goals. And the goal was to make as much progress as we could as quickly as we could. And so, during that time, you know, we really did go from a technology stack that was where we were having a lot of trouble and a project management approach that, you know, just wasn't allowing us to meet the deadlines that we needed to meet to something that was quite a bit faster, right? And towards the end of that time, you know, I went out to the valley to talk to investors.  What do you do about Google? What do you do about Apple? Like, what makes you different? Why are you going to win in the face of competition from some of the most innovative, well-funded companies in the world? And, you know, to me, the answer to that question is obvious, right? It's, you know, we focus on privacy, we focus on community, a big open source community with a lot of diverse viewpoints and a lot of freedom can build software that is more stable, more reliable, and more engaging than, you know, these big tech companies can, simply using internal resources, right? You know, that's really the thesis. And, you know, one of the other things that we bring to the table is, hey, look, you know, our monetization strategy is built around, we provide something of value and people pay us for it, right? As opposed to this kind of oblique strategy of, you know, hey, we're going to dominate the user experience in this vertical and then use that dominance to, you know, drive business to one of our other business verticals where we'll make money. But of course, you know, that isn't instantly obvious to venture capital folks who've made admittedly huge fortunes in surveillance capitalism, right? Backing companies that, you know, as their primary mode of monetization, spy on people and sell that information or sell access to that information to others. So I went to the valley and was talking to a series of investors and really wasn't getting the response that I had historically gotten when I went to the valley. And so I reached out to some of our larger investors and said, you know, for the first time since we founded the company in 2015, I really don't feel like I've got a handle on, you know, where we're going to be tomorrow. And I really could use some help, right? And I sat down with several investors and, you know, when I sat down with Michael, he really clicked in a lot of ways. You know, Michael has a really strong track record, you know, at Stellar Semiconductor, he created a company that was very, very valuable despite the fact that they never actually even shipped a product, right? They did designs and they were, you know, working their way into becoming one of the early graphical vector graphics or GPU companies, right? And, you know, Broadcom, you know, viewed the GPU as such an important part of their technology stack that they acquired the company despite the fact that Stellar hadn't shipped its own chip at the time. You know, and then he went on later to found a gaming company and, you know, it was really early to the MMO space, like right around the same time that World of Warcraft was taking off and people were really getting into MMO games, Cryptic Studios published the heroes. And so it was just really clear to me in talking to Michael number one that our values aligned and that he was as committed to privacy and user agency and openness as I was, right? Maybe more so in a lot of cases. And I think that the reverse was true too, like he saw the, you know, a move mountains to build a company that is based on those basic principles. And then, you know, coupled with his experience, it just made sense for him to take the role of CEO and, you know, the chief operator. And, you know, at Minecraft, it's taken us a year or two to really define what that CEO role is, you know, typically, the CEO is outward facing, you know, they're the ones that are dealing with investors, they're the one who are dealing with bigger customers. And, you know, they might have somebody in house operating, but, you know, at the end of the day, the primary job of the CEO is don't let the company run out of money, right, which typically involves fundraising. Now, in Michael's case, he took a little bit of different approach to that because he had had so much success, you know, he reached into his foundation or his foundation reached into their coffers and, and provided us with, you know, the operating capital that we needed to really, you know, take the next steps that we needed to as a company. And so I was really happy to take that that CEO hat off and pass it on to somebody who is more capable. And, you know, when we find somebody who's more capable of telling our story, I intend to take that hat off as well. And when we, you know, finally cross the threshold of, you know, selling product to pay our bills as opposed to raising money to pay our bills, you know, I'm looking, looking forward to taking some of those sales hats off and those fundraising hats off as well.  I think that that would be a great role for me. And I'd be really happy to work with marketers and fundraisers and operators and, you know, product managers and project managers and developers, all of whom are more capable than I am in the same way that Michael is CEO is more capable than I am. So, so that's pretty exciting. So let's see, what are you doing about the global parts shortage? So there's a couple of things that are going on in the global parts shortage. Like there's the obvious stuff, which is, you know, COVID has messed up supply chains. You know, we have some, some climate change related issues, you know, drought in Taiwan, where a Taiwan semiconductor is located, has caused problems with production.  But then there's some second tier effects that come from that that are also causing some problems within that, within that market. You know, one of them is, one of them is duplicate orders. So, you know, as the Silicon market started to get constipated for lack of a better word, companies that needed chips started putting in orders of multiple vendors. So, you know, if you need 10,000 chips for your automobile, let's say, you know, you have your typical supply chain, and then you probably have some supply chain redundancy, you know, companies like Toyota made that a huge priority after the after the tidal wave in Japan. But, you know, those companies started to go outside of their standard supply chain and put in orders for the parts that they needed with other vendors. And so a company that needs 10,000 microchips might have put in an order with, you know, one vendor, two vendor, three vendor, four vendors, and to the upstream microchip manufacturing manufacturer, that might look like an order for 40,000 chips, right? Because they're selling through distributors, and they don't necessarily know who the end customer of that part is. You know, as those orders are fulfilled, you know, as those orders were dropped, it made the semiconductor supply chain look more and more and more behind. And what we're finding is that as those orders are being fulfilled, so, you know, you ordered 10,000 from four vendors, one vendor finally delivers, the other three orders are getting canceled. And what that's doing is it's freeing up supply for other people who might have ordered that chip or something like it. And so, you know, we're already starting to see some loosening in that supply chain. And, you know, recently, I think on the Raspberry Pi side of things, we found a vendor who was able to cross fingers, meet our needs for the upcoming, you know, initial production run. But the same is true of audio chips, the same is true of some of the supporting chips that are going on the SJ201 board. And so, you know, we're navigating it to the best of our ability, you know, we're working with our upstream supply chain. And then, you know, we're doing what a lot of those other vendors are doing, you know, ordered the same parts from five vendors, you know, with the goal of getting parts in-house at a reasonable cost as early as possible, and getting those Mark II out the Mark II def kits or production Mark IIs out the door. The def kits actually are out the door effective last week. So I'm super excited about that. So next question, why are you doing another raise? So that's a good question. A healthy startup will be raising money even after it's profitable, right?  A local ice cream shop probably plans to lose money for some period of time. But, you know, they look at the market for ice cream in their space, they look at the rent on the place that they're going to be, on the venue that they're going to occupy, they look at the labor rates within their local community, they do a little bit of math, they set aside enough money to get through the initial startup period, right? And ideally, after six months or a year or 18 months, that company has no longer, that little ice cream shop is no longer burning cash. They're now profitable and, you know, maybe they start looking at either franchising or expanding into other locations, right? A startup is very different from that. So, you know, a typical startup in the modern startup economy, you know, the life cycle might be 10 years, right? From the time that the company is founded to the time that the company exits either through an IPO to a public market or through to a sale to somebody else in the industry or, you know, failure, which is a real outcome in a lot of different cases. And, you know, a lot of times the difference between having a successful outcome and failing is the availability of capital through that process. You know, when a startup initially gets started, what it's doing, especially if you're developing new technology, is seeking a customer base and a market that matches the capability of the startups and then once the startup finds it, you know, doubling down and growing into that marketplace. In our case, when we first got started, as smart speakers weren't a thing, right? Like, a Minecraft pre-exists Amazon Echo or Google Home or Apple's HomePod, we used to have to explain what a smart speaker was. But we had this concept that, you know, given modern machine learning algorithms and modern natural language understanding and modern speech transcription methods that we could build, you know, an artificial intelligence that interacted with people exactly like a person, right, which is the end goal of the technology that we're building.  Like, you know, smartphones really weren't going to be a good solution for us because we don't control the microphones. We don't control the operating system, you know, either for Android or for iOS. And as a result of not having access to the hardware, you know, it makes it very, very difficult to have a wakeward activated technology. You know, the other thing that they kind of, and that this is still the case with voice assistants on smartphones, you know, a voice assistant really occupies a space, right? And so when we got started, the first thing that we did is we went to explore that market. We did a Kickstarter to see if anybody wanted a smart speaker. It turns out lots of people did. And then we started, you know, building the technology while simultaneously looking for investors that shared our vision.  You know, the first Kickstarter was like $125,000. We joined Techstars, which was another $120,000 check, raised a little angel round that, you know, $350,000. And then kind of started down the path of building that technology, hiring the team, you know, getting ready to go into production. You know, shortly after that, we went out and raised another round, right? We ended up raising, you know, I think it's now nearly $7 million over the course of four or five small rounds, some of which are discrete, some of which kind of flow together. You know, I'm a big fan of always being in a position to bring on board a new investor into the company, never being shut down on fundraising, which puts me a little bit in opposition for some other founders who like to do fundraising in discrete rounds. And as long as the company is growing in value, and as long as the share price continues to go up, you know, that becomes a blessing for everybody involved. You know, when we originally raised money from Mycroft, it was on a par value of like 0.0001 cent per share. You know, today we're raising money on $1.70 a share value, which makes the, you know, the before money value for our latest raise $38 million. So, you know, and we're selling that stock in arms length transactions to investors that we're in no way related to. And so that really does set the value for the company, right? And, you know, the next round, we might raise, I don't know, another $5 million on a $50 million pre or a $60 million pre. And then, you know, at the end for our company, or at least the part where we go public and start providing some liquidity, will probably be a Series A plus or maybe even a SPAC, you know, that allows us to tap into public markets and, you know, continue to grow the company. And so, you know, the idea of the startup is to explore the market, find a niche, you know, double down and invest in that niche.  And to do that involves raising multiple rounds at higher and higher evaluations over time. And that does a couple of things. Number one, it shows early investors that the company is growing in value. It makes sure that the founders don't get diluted too deeply out of the company. And then, of course, it makes capital available so that the company can grow and expand. And so, we're really excited right now to be raising on start engine. You know, we're raising $5 million, which we're looking to do over the course of the next year or so. The first few weeks of that campaign have been very, very successful. You know, we're on track and on pace. Actually, we're ahead of the pace that we had originally set to raise money for this round. And, you know, we're raising at a higher evaluation than we did last time, which is great for existing investors and should be an indicator for other investors as to what the future might hold for Microsoft provided, you know, the market remains the same and, you know, forward-looking statements should be taken with a grain of salt clearly. So, yeah, we're pretty excited to be raising another round and, you know, making the shares of the company stock available to people other than VCs within the inside track. You know, one of the things I read in the news recently, which kind of blew my mind, was Peter Teal's Roth IRA, right? So, here in the United States, you know, the maximum you can contribute to a Roth IRA is $5,500 if you're under 50, and then I think it goes up to $6,000 if you're 50 or over. Anyway, something like that.  The total amount of money you can contribute to a Roth IRA is about $300,000, or $350,000, something like that. You know, Peter Teal's Roth IRA has something like $5 billion in it, and the way that he was able to build that kind of value for his IRA was by, you know, initially putting eBay stock in it, which was valued at a very low value, exiting eBay, taking a million, million, five, and investing it early on in Facebook.  The thing is, is that you and I, as normal investors that are not plugged into the PayPal Mafia or the Silicon Valley VC scene, you know, today we don't get access to those types of early stage deals. And so, one of the other reasons I'm excited about raising money through crowdfunding and through, you know, some of the other mechanisms that we've raised money with over the years is that it gives normal people access to our early stage startup. And, you know, that might have a catastrophic end for them, right? Like the company, there's no guarantee of success. But if we are successful, you know, that means that they're able to get in involved in the company at a time where for a typical startup, you know, they may only have three or four or five venture capital firms on their cap table. And ideally, you know, whether it's us or some other startup, some of these crowdfunding mechanisms will create opportunities for early stage investors to create the types of outsized returns that guys like Peter Teal have gotten by being, you know, Silicon Valley insiders and making investments that way. So, super excited to be making that available to the general public. So anyway, it looks like I've been sitting here long enough. My motion sensor just set the lights in my shop off. I'm really happy to be here at my craft talking to folks. You know, if you want to submit some questions for us to answer in the future, I'd love to love to engage. And I think we'll be doing a lot more of these as we're continuing to try and engage with our community. So thank you so much for watching the YouTube live stream. And I'm looking forward to talking to you again in the future. Thanks so much.


Favourite Bible verses part five, John 9.41. Jesus says, if you were blind, you wouldn't be guilty, but you remain guilty because you claim you can see. Like straight mic drop.   But to those who recognize that sin has blinded them from knowing the truth, he gave spiritual understanding, he gave them insight.


Russia. We see that West tries to create second front in Georgia and Moldova. In its military political and diplomatic plans, Russia takes into account the West's attempts to create a so-called second front in Georgia and Moldova, as well as the Polish military contingent on the border with Belarus, said Foreign Minister of the Russian Federation Sergei Lavrov at a press conference on the results of his visit to Uzbekistan. A combination of these factors, of course, does not allow anyone to relax. We are not relaxing. We see all of this and take it all into account in our planning, both political, military and diplomatic and in other relations, he said. We see such attempts. There have been attempts to drag the Georgian leadership into creating a so-called second front. The current Georgian leaders are showing a responsible approach. They show an approach that is based first and foremost on the fundamental national interests of their people, and they refuse this kind of approach. There were reports that they are trying to make such a second third and a half front out of Moldova as well, said Lavrov. Poland has concentrated serious military contingents on the border with Belarus, several tens of thousands of military personnel. There was such information. I do not know how true it is, but it is certain that considerable forces are concentrated there. Lavrov concluded.


salaamu alaikum warahmatullahi guys what is going on it's your brother Muhammad Al-Annalusi here founder of AndalusiaInstitute.com today I wanted to make a quick video inshallah to point out a very simple thing that you can start doing in the beginning of your learning the Arabic language that if you don't do from the very beginning it will be really hard later on to put in practice and what this little thing will allow you to do is actually correct yourself as you are using the Arabic language whether it's while speaking whether it's while reading without haraqat without vowels and this is what the students at AndalusiaInstitute.com are doing and what I like to train them to be able to do because it's a skill that if you have you can later on become an independent student and correct yourself as I said do you hear how he said yancy and then he went back to the past and he said nasia yensa and that's because we have memorized it that way you see when it comes to learning for the sake of competition like practicing or working out for a for a competition it's not the same as just working out for the sake of working out for the sake of being healthy right so it happens the same with Arabic many times people don't know the right method of building vocabulary they just know sometimes they don't even know a method and and what happens is that they don't learn it for the sake of using it later on to speak with it to understand to listen and understand at the same time to read um and the thing is you know you might ask okay why is vocabulary so important why is building vocabulary so important what about grammar what about morphology but the thing is that when learning language building your vocabulary is the basis of the development of all the other skills um you know whether it's reading comprehension listening comprehension speaking uh writing spelling the pronunciation as well and this is like a wise man once said he said uh while without grammar little can be conveyed without vocabulary nothing can be conveyed because vocabulary is most of what we speak with so how do you acquire new vocabulary um the easiest way I would say in the most natural way is through reading and through listening okay and that's how we acquire vocabulary in understitute.com we first go over the text extract all the vocabulary memorize it then meet up on a weekly basis to put all the vocabulary into practice so that's kind of like our battlefield right our competition because we actually you know get ready throughout the week to go into the competition so we pretty much use both ways um reading and listening now going back to to the one thing that you can do that will boost your progress immensely is it's so simple and what you want to do is when when you are reading or listening with the intention of learning the Arabic language you want to take the past tense present tense imperative and source i.e. the the name of the action so for example um you know if you are reading and you come across the Haba right which means to go so you write down in your notebook the Haba Yed Haba Idhab the Habun so here the Habun would be the name of the action which could be literally translated to uh to go or that you know the act of going so if it's if it's a noun that you came across like for example Beytun you will go ahead and write down the plural of that noun in this case Boyutun okay if you want to go an extra mile what you can do is actually write all the plurals of that particular word so in this case Beytun Boyutun is the plural Abiyatun is another plural and for the words that have synonyms and antonyms you can add in your notebook those as well which will give you you know extra vocabulary that's what I did in the first year of uh fluent Arabic like about a decade ago and that's why after 10 months I was pretty much to a level of fluency because I had too much vocabulary so you might ask right now okay but where do I find the past tense the present tense um the imperative of verbs how do I put it together how where do I find it right so I will show you a digital resource that you can use in order for you to start building your vocabulary in this way and you can have it you know stored in a in a uh you know in a Kitabat Abiyat which is what we call it under this institute.com and you can from there start building your vocabulary and memorizing that vocabulary to the point where you know all the vocabulary that is in your own book in your own mental dictionary so let's jump into the laptop and I'll show you this all right so here we are on google what you want to do is type al-ma'ani just as you see so this supposed to be Arabic al-ma'ani for the meanings is the plural for ma'ana and you go ahead and click the first one that will pop up now you want to go and search for the Arabic to Arabic one this is a digital dictionary like I said so you go for the Arabic to Arabic and let's say that you come across a word you're reading right and you come across a word that um that uh for example that have a right but let's say that you come across the the the um the present form so what you want to do is you go ahead and write what you seen in the text or what you heard on an audio that's why um you know you see reading and writing comes first which is very simple you could uh learn that in in less than two weeks at least that's what it lasts um our module inside of Arabic like in Arabic it lasts around two weeks to learn how to read and write now you go ahead and look for this and you will see that most Arabic dictionaries they are um organized in a way where they give you the past tense they give you the present tense they give you the master which is the the sorry sometimes as well they give you the actual the imperative as in the command do this so for example the habit past tense yet he goes present tense either meaning go and the habit meaning the the act of going or the name for the action right so here you have you wrote down yet habit because that's what you came across on the on the text so you will find the habit you will find here yet the habit and what's what's most important is what is the haraqa mainly for the three for the for the verbs are on three um that have three letters which are the most basic ones the habit is not like stuff or in or things like that so or other weights what i mean so the simplest one is the three letters right so the only thing you need is to know what what haraqa is in the middle of the of the present of the present tense so is it yet the habit is it yet habit so it gives you the haraqa that's why you don't see the other vowels on the on the other letters because this is i mean once you get into it it's pretty much obvious that is yet habit this how all the presents are are so here's the habit right then it gives you a muster so the habit or the habit and here it gives you more advanced forms of the verb or names extracted from the actual source of the verb from the habit like the habit who's the person that does the action or the mafool which is like the the thing that is being gone to but these are a little bit more advanced we actually go over this after 17 lessons of arabic like an arab so even even in arabic like an arab we don't give this straight away for you to not yeah i'm saying this for you to not get confused with this so the most important part that you need to to look at here here gives you a lot of a lot of examples which is very good to understand and to relate the context that you read and where you found that verb and and to relate it to to one of the context that gives you here because as you guys seen before sometimes there is articles that goes with the with the verb right just like in english is if you say i went to i went by i went with if you change the article it changed the meaning so it's the same with with with the arabic language it's not the same as to say the habit then saying the habit be right so um so here gives you a lot of examples with different contexts and then if you keep going down it gives you other forms of you know derivate or extracted from the same three word root letters the habit okay so from here what you would want to focus on the most is this part which we seen on at the top of the page as well which is which is um the past tense so the habit then the present tense yet habit and then the like i said sometimes it gives you most of the of the dictionaries don't give you the actual imperative or the command of it because it's pretty obvious the only thing that changes is one letter so if to say like the command if if we are talking about the habit he goes yet habit for you to say to someone if have or go you just need to remove the yeah add an alif and if the third letter is a kasra or a fat halak here then you will use the kasra on that alif so you will say if the hub okay if if is a kasra like for example for example irsil irsil then you use kasra as well but if it's yablug where the third letter is a dhamma then you say uplug you will use on the first alif a dhamma on it so so that's a little bit more um you know it doesn't give it to you here because it's very obvious once you know those those little rules that's why it's always better to learn with an instructor it's very hard i'm giving this to you guys and for you guys to to do this on your own but obviously when it comes to learn Arabic mainly in the beginning in the very beginning it's very important for you to have an instructor and here you have as well the the um the imperative form or the command if the hub if hub so this is the ayah from the Quran it gives you examples from the Quran where that word comes from or where that word is is as well in the Quran now uh if this wasn't enough i will show you guys another uh conjugator so in this website as well this is called cooljugator so you write that you write down cooljugator.com and you will come to this page and then you can write down here for example to go and then it gives you it gives you different things it gives you the fun the phonetic way for you to to know how to pronounce which you can display or choose to display or not so for example adhabu so ana meaning me adhabu and it gives you how to pronounce it here um and as well it gives you so anti tathabu this is actually playing with the pronouns as well so this is a little bit of morphology but i was just showing you guys in in case in the al maani it doesn't give you the imperative form command form and you don't know how to find that you can find it here if you come down here you come here in imperatives and it gives you adhab adhab and on top of that it gives you you know it shows you how to use the pronouns etc but does a little bit more more advanced and related to morphology so i was just showing you guys how to extract vocabulary from a text and put it into a form of kitab tabid as i show you guys to actually start building some vocabulary that's actually if you start just building vocabulary you know a lot of vocabulary like this like if you know the habithab the habun it means to go and akala kulkul akluni means to eat shari'iba ishrab ishrab sharama it means to it means to drink na maya na mu nam na mu mu ni means to sleep if you build the most basic the most basic 250 500 verbs and and and um and nouns and plurals this way when preparing yourself to go to learn to someone or waiting for you to actually save some money to actually pay yourself a instructor anything like that it will save you a lot of time if you can actually do it now let's talk about the nouns because i showed you guys um i showed you guys the for the verbs which is the most important and a little bit more complicated but i didn't show you for the now so let's say let's take the same example that we took before baytun if you come across baytun and you type baytun here it will give you straight away it will give you straight away here baytun al-jamru meaning the plural abiyatun and as well boyutun and as well boyutatun okay so so these are all the different plurals it is enough sometimes mainly in the beginning to just memorize one one form of a verb however obviously as you progress you want to build more your vocabulary and become richer in terms of vocabulary so it's very recommended for you to go ahead and memorize the other forms of vocabulary so um so this is um this is what you can do in in in order for you to boost your building of the vocabulary of the arabic language mainly the very basic one in the beginning and this is how it should go this is the method to go like i don't know any other method better than this and i don't think there is actually because i mean there is the method of like building your vocabulary through learning um verbs and and now it's okay that's known but systemites like systemites like this way i have never seen it before and all the other maracas all the other centers of arabic that are that are that are knowing egypt that don't use this method most of the times the students they they not as sharp in terms of vocabulary than the other students um they might be sharper in grammar but as we said you know uh while without grammar little can be conveyed without vocabulary nothing can be conveyed so um so most of the maracas in the most known place to learn the arabic language like for example egypt most of the centers they use this method so i highly encourage you to use this method and to um and to apply it into your learning of the arabic language and if you are interested in knowing a little bit more about this method is the actual method that we're using andresinstitute.com so i would encourage you to check out um in the description below how to actually learn more about this method and how to actually if you were to uh if you were interested in learning and with us in in arabic like another program then go ahead and click the link in the description and join the free webinar the actual the actual webinar where i explain you the method and present to you the program is for free then the program the 50 month program is is a paying program so you can learn more about it through the link in the description and i hope you guys benefit it from this um from this little tutorial little video little tip video and i'll see you guys on the next one


Good morning, everyone. Before I get started, I want to speak very quickly about the call I had earlier this morning with President Zelensky of Ukraine. The President and I discussed our shared concerns about recent Russian military activity and ongoing aggression in the Donbas and in Crimea. On our call, I reaffirmed Canada's unwavering support and friendship for Ukraine's sovereignty and territorial integrity, as well as our commitment to further deepening our long-standing friendship with Ukraine. For many people, the end of the week was the opportunity to have family meetings on Zoom or to spend time outside. But it wasn't a challenge for everyone. In the four corners of the country, nurses, doctors, contact tracers, and staff members of public health were at work. They are there to ensure our security, and we must do so for them. What they tell us is that all the modellizations confirm that the situation is very worrying. Around the world, countries are facing a very serious third wave of this pandemic. And right now, so is Canada. This isn't the news any of us wanted, but hospitalizations are surging. ICU beds are filling up, variants are spreading, and even people who had convinced themselves they didn't need to be concerned are getting sick. Even if the sun is shining and the weather is getting warmer, COVID-19 isn't done with us yet. And that means we all have to hold tight a little longer. Later today, I'll speak to Premier Ford about the situation in Ontario. I know we'll talk about what the spike in cases means for hospitals, and the importance of vaccinating as many people as possible as quickly as possible. We'll continue working together to keep Ontarians safe and support people and businesses through this next wave. On that note, I'll also be speaking to all premiers tomorrow about our continued and shared work to protect and support all Canadians right across the country. As long as we don't have to vaccinate as many people as possible, we will have to continue to protect each other by following public health advice. A little everywhere, depending on the increase or decrease in cases, the rules will have to be changed. Ontario, the British Columbia and Quebec have already made the most necessary and difficult choice to take more strict measures to stop the spike in cases. It's not easy, and we know that measures may become even more strict, but that's what we have to do. We do that to save lives. We need to flatten the curve to save lives. To young people, you've made tremendous sacrifices over the past year to protect your parents, grandparents, and the heroes on the front lines. Thank you. You are saving lives. We need you to keep doing this a while longer. If you can stay home, please do. And to frontline workers, I know you're tired, exhausted. I know you're really scared about what the coming weeks could bring because you're seeing the seriousness of these new variants and the spike in cases. You have done an unbelievable job over the past year. Know that we will continue to be there for you, and we will get through this together. If you need to take time off because you're sick or self-isolating, we've made sure the Canada Recovery Sickness Benefit is still there for you and any worker who needs it. In fact, we've added two more weeks to that benefit. Go to canada.ca to see how you can qualify because no one should be going to work sick right now. Of course, if you need PPE on the job, we're continuing to get you that. And above all, we're working around the clock to get vaccines delivered. You probably know people who received their first dose, or maybe you received it yourself. So you know that each dose counts. We've already delivered more than 10 million doses of vaccines to the provinces and territories. We haven't only reached our goal for March, but we've largely surpassed it. And from now on, the doses will continue to arrive faster and faster. This month and next month, we will receive more than a million doses per week of Pfizer only, in addition to the delivery of Moderna and AstraZeneca. Later this month, Janssen will also start delivering his vaccine to Canada. And as I said last week, Pfizer confirmed that they would advance 5 million doses for June. These doses were planned for the end of summer. We will now receive them sooner. Minister Anand and his team, as well as the Canada Public Health Agency, are working tirelessly to advance and coordinate deliveries. We do everything we can to help the vaccines be administered as quickly as possible. Our government is delivering over a million doses a week to the provinces and territories. And we'll keep making sure these vaccines get to people as quickly as possible. As Deputy Prime Minister Freeland announced, we're providing additional support to the provinces and territories for their pressing needs on vaccine rollout. The federal government has paid for the vaccines, and we're happy to continue to help with more resources as needed. Because this is no time to go back and forth over who should pay for what. This is the time to do everything we can together to get as many people vaccinated as soon as possible. From day one, beating COVID-19 has been a Team Canada effort. Last summer, we delivered $19 billion through the Safe Restart Agreement to support the provinces and territories on what Canadians needed to get through this crisis. That money has helped with everything from additional staff at seniors' homes in Alberta, to modeling in BC to help keep communities safe, to mobile testing in Nova Scotia to reach rural areas. Today, we're delivering on the final installment for that Safe Restart Agreement. Our priority is for funding to go where it's needed most, whether it's for patients in hospitals, PPE for essential workers, or COVID-19 testing and screening for people on the front lines. Just like the first verse, the investment of $700 million announced today in the Safe Restart Agreement will help ensure people's safety and help families and small businesses to get through this crisis. All the money invested in Canada to fight this pandemic, $8.10, comes from the federal government. We want to help people through this crisis and make sure our country is in a good position to rebuild better. Before I end this morning, I want to take a moment to recognize that this will be an especially difficult day for a lot of people. It's now been three years since the terrible Humboldt Broncos crash. Today, we remember 16 people taken from us much too soon. And as we do, we stand with the families, friends, and teammates whose lives were changed forever. To people grieving across the country who are thinking of you. I can only imagine how hard it is for you not to be able to gather on this day. And to everyone who continues to recover and rebuild, your strength is remarkable. Every day, all Canadians stand with you.


Item number SCP-760 Object Class Safe Special Containment Procedures Each specimen of SCP-760 is to be kept in an individual containment area. The locks on the doors to these containment areas are to be changed every month. Feetings composed of grams of a nutrient-rich paste are to be issued once a day. Interactions are only to be introduced to each other in experiments meant to observe social interactions and subsequent psychological events between specimens. At least two armed guards are to be posted outside of each containment area at any time. Each containment area is to be lit with no more than one 40-watt light bulb and equipped with low-light surveillance cameras. In the event of an equipment malfunction, equipment should be manually replaced as soon as possible, as instances of SCP-760 have a tendency to disassemble maintenance equipment. Personnel are allowed to give specimens of SCP-760 items that they no longer want or need, given that the objects do not violate current Foundation regulations, and that they are approved by the overseeing researcher. Items requested for donation to SCP-760 include, but are not limited to, car keys, denied, a broken clock, approved, a Rubik's Cube toy, approved, everyday trash, denied, a broken Foundation computer, approved, provided that the hard drive is removed. Description SCP-760 is a vaguely humanoid species of animal, only three of which have ever been obtained by the Foundation. The skeletal and muscular system of SCP-760 differ greatly in areas from those of humans. The most notable effects of these differences being legs that extrude perpendicular to the torso, and an ape-like curvature of the spine that results in a preference to walk on all fours. Other notable differences include the addition of an extra joint on each finger of SCP-760, and an average of 150% of the joint degrees of freedom that are allowed for humans. This makes SCP-760 much more flexible in the average human, which aids specimens of SCP-760 during feeding. Where a face would be on a human, there is a mass of hair on SCP-760. This hair is shown to have some sort of sensory function that allows for sight in the dark. Underneath the hair, there are no eyes, nose, or mouth. However, the skin of the face is pulled taut as a part of a speaker-like vocal system. SCP-760 has muscle structures in the front of their head that they can use to vibrate the skin as if it were a drum head, producing a variable-pitched wine. Further observation led to the discovery that this vocal structure is also capable of opening and serving as a mouth. Even this mouth is a tongue, approximately 40 cm in length, with a soft but coarse texture. The epidermis of SCP-760 is shown to react to light in a way that makes them invisible. This is done via a complex system of reflective data expunged, roughly 78% of SCP-760's skin. The hair on SCP-760's head disappears as well. The removal analysis shows the hair to be similar in composition to a polar bear's. As light dims, however, this effect fades, and in very dim light, it is possible to see SCP-760 completely. Removal of the skin also hinders this effect, and it appears to do so on more areas of SCP-760 than where the skin was removed, suggesting that the function of SCP-760's invisibility on any part of the body requires that same function on all surrounding parts. It is also worth noting that SCP-760 appears agitated when subjected to light, for longer than what would be normal sunlight hours, near latitude north or south. Instances of SCP-760 are very docile under normal circumstances. They exhibit behavior and tendencies similar to canines or primates, thus making understanding what they are thinking relatively easy. They are generally curious creatures. Any object that is placed in the containment area is almost sure to be examined thoroughly by them. They seem to enjoy toying with new things, particularly taking objects apart and examining their pieces. They also seem to enjoy attempting to figure out how things work, and as long as they are attempting to learn about something, they are completely content to stay in the containment area. Instances of objects by personnel have served as more than enough to keep this want for new objects appeased. It is, generally speaking, entirely safe to enter the containment area, and specimens of SCP-760 seem to either enjoy or be indifferent to the presence of people. They have shown behaviors towards humans that are almost childlike in nature, and almost always benevolent. Species of SCP-760 appear to be particularly interested in sleeping humans. In experiments performed investigating this, it was discovered that specimens of SCP-760 feed on human secretions and dead matter. When presented with a sleeping human, SCP-760 will proceed to carefully position itself over the subject, onto their chest if the subject is sleeping on their back, and begin vocalizing at approximately 20 decibels for a period of r— to r— minutes. This vocalization appears to promote slow-wave sleep in r— percent of subjects, greatly reducing the chance of the subject awakening. The exact mechanism responsible for this effect is unknown, but is thought to involve data expunged. In the remaining r— percent, the subject is largely unaffected by the vocalization, and may regain some level of consciousness. Several subjects who have reported this experience have likened it to sleep paralysis, stating that they awoke to find themselves aware of an inhuman presence in the room, but unable to move. After this period, SCP-760 will use its tongue to consume any easily accessible secretions present on the subject, including ocular discharge, hair oils, dead skin cells, pimples, and r—. This process has been observed to be largely harmless to the subject. However, experimental observation indicates that if the subject shifts during sleep or some external event occurs, SCP-760 may become startled and exert additional force on the subject, in several cases causing sore areas, and slight bruising. Addendum 761. Research into weaponizing SCP-760's invisibility is pending approval. Addendum 762. On r— two thousand r— eighty-six days after the initial discovery of SCP-760, another specimen of SCP-760 was obtained, revealing it to be a member of a species rather than an independent creature. Specimen previously in possession reclassified as SCP-761, and newly obtained specimen was classified as SCP-762. Research into the social interactions between the two began immediately following SCP-762's arrival at Sector V. Addendum 763. SCP-761 and 2 were observed taking part in what appears to be some sort of mating ritual, which involved consecutive hours of consistently screaming at each other, and data expunged, resulted in the immediate medical treatment of SCP-761, and the knowledge that specimens of SCP-760 are hermaphroditic. Addendum 764. SCP-762 gave birth. Subject titled SCP-763. Incident report, 761i. On r— two thousand r— at approximately twenty-one forty-eight, one of the guards posted to contain SCP-761 fell asleep on his shift. SCP-761 was somehow able to see this, suggesting that the hairs on its face allowed to sense through walls. It then proceeded to its containment door and partially disassembled it from the inside, a process taking roughly hours, and proceeded to feed on the guard as he slept. The other guard was unaware of this due to SCP-761's active camouflage in the hallway lights, but proceeded to coax it back into its containment area the moment he realized what was happening. Lesson complete. If you missed the previous orientation, go watch SCP-759, sourdough starter, right now. Or for the complete course, watch this playlist.


Attention Green Valley Ranch residents this is a community notification of a new sexually violent predator in your area please stay tuned to the following short program for more information. Hi I'm technician Ron Hackett with the Denver Police Department. The sex offender registration and compliance unit at DPD is responsible for the registration monitoring and tracking of all registered sex offenders and sexually violent predators who live in the city and county of Denver. Here's a brief history of sex offender legislation in Colorado. Our state laws trickle down from federal government mandates. In 1994 we had the Jacob Wetterling Act which mandated that states would establish a sex offender list. Magans law of 1996 said that the public would have access to those sex offender registration lists. The Pam Litchner Act of 1996 stated that some offenders might have to have lifetime registrations and the Adam Walsh Act of 2006 unified sex offender laws across a country. In Colorado the legislature has determined that sexually violent predators by definition pose a higher risk to the community at large and therefore mandated that upon their release from the Department of Corrections the community must be notified. Sex offender notification in Colorado happens in two ways. The first is passive and ongoing through the sex offender registration process which is a list maintained by a local police department. The second way is active via community notification for those offenders determined to be sexually violent predators by the courts or by the parole board. Most sex offenders in Colorado are supervised by the criminal justice system in our communities. Most sex offenders engage in crossover behavior which means they may have been arrested for one type of crime but be apt to commit another.  There is no typical sex offender but all tend to be deceptive, manipulative and secretive. 80 to 93 percent of sex offenses are committed by someone known to the victim. Sexual deviancy begins in mid to late adolescence. Sex offenses are not impulsive.  The community has a vested interest in helping offenders to be successfully managed in the community. Sex offenders have the same need for housing and employment as any other citizen.  There are approximately 16,500 registered sex offenders in the state of Colorado. About 65 percent of convicted sex offenders are placed in the community on probation. The remainder are in the Department of Corrections or community corrections. Offenders may be caught for one type of offense but be at a high risk to commit another type. Crime of conviction is only one indicator of risk.  The offender's residence must be verified quarterly by the Denver Police Department. The full sex offender registration list is available by calling the Denver Police Department Identification Bureau at<PHONE_NUMBER>. Convicted felons and those with multiple convictions are posted online at DenverGov.org slash police.   Now here's a look at the newest sexually violent predator living in Denver. Here's an overview of the registered sex offenders currently living in Denver. There are 2,494 total living within city limits. In Denver Police District 5, there are 252. Precinct 523 has 73 registered sex offenders. Of those, 43 have felony convictions and 30 have misdemeanor convictions. Christopher John Salazar is a sexually violent predator currently living in Denver. He's 30 years old and was born on August 17, 1989.  He's currently living at 19239 East 39th Place in the Green Valley Ranch neighborhood of Denver. Schools located within one mile of this offender include Martin Luther King Jr. Middle School and High School at 19535 East 46th Avenue, Green Valley Elementary at 4100 North Jericho Street, Marama Elementary at 19100 East 40th Avenue. Parks located within one mile of this offender include Highline Canal, Green Valley Ranch East, Ensenada Park, Green Valley Tennis Courts, Marama Park, Green Valley Ranch West, 47th and Telluride Park. Bus routes located within one mile of this offender include Route 42 45th Avenue and Argonne Street. Routes 42 45 and 169 L 43rd Street and Tower Road.  He's not currently on parole and registered with the Denver Police Department on August 2, 2019 to 19239 East 39th Place in the Green Valley Ranch neighborhood of Denver. Past charges against this offender include assault, parole violation, traffic offenses. Christopher John Salazar has been determined as sexually violent predator after meeting the following criteria. Criteria one age 18 or older on the date of the offense or under 18 and tried as an adult. The offender was age 20 at the time of the offense. Criteria two the crime must have been committed on or after July 1, 1997 and convicted on or after July 1, 1999.  The offender was convicted on January 10, 2011 for attempted sexual assault on a child, child abuse, negligent, no injury, and sexual assault, 10-year age difference. Criteria three the relationship to the victim was one of the following. Victim was a stranger to the offender or the offender established or promoted a relationship with the victim primarily for the purpose of sexual victimization. The victim was a nine year old female. The offender was known to the victim. Criteria four positive results are the passing of a risk assessment instrument administered by probation parole staff and a qualified treatment evaluator. Positive results include an assessment for the presence of a mental abnormality, a level of denial regarding the offense, treatment appropriateness and motivation, presence of sexual deviant interests. The offender was evaluated by the Denver County courts with positive results determining him to be a sexually violent predator.


Coalition of APC Geographical Zone Support Groups, not West Zone, have urged all Progressive Congress leadership and the president-elect, Borla Tinibu, to include the not-central in the sharing of national assembly leadership positions. Addressing a press conference in Caduna yesterday, the coalition said the APC and the president-elect should review the national assembly leadership zone in arrangement to include not-central, so as to give each section of the country a sense of belonging. The leadership of the coalition and coordinator of not-west Abu Bakr Ali Bagwai, who was flanked by his secretary, Barista Bello Musa Kabao, said they were vehemently opposed to all forms of favoritism and marginalization. Spirit of fairness, equity, justice, inclusiveness and national unity. We hereby call on the APC National Working Committee and the president-elect, Asuaju Borla Amit Tinibu, to review the national assembly leadership zoning arrangement to include not-central, so as to give each section of the country a sense of belonging. We, the coalition of APC Geopolitical Zone Support Groups, not west, are also saying no to favoritism and no to marginalization of the not-central. There shouldn't be favoritism or preference to any section of the country and no region should be marginalized, excluded or sidelined. We are aware that our zone, the not-west, has been given two leadership positions, Speaker and Deputy Senate President. By the APC National Assembly Zoning Arrangement, while the not-central were given none, this has created an image of favoritism toward the not-west and marginalization against not-central.


So welcome everyone to the session named a peek into observability from Testers Lens by Parveen Khan. We are glad she can join us today and yeah just without further delay over to you Parveen. Thank you so much for, thank you so much first of all thank you so much for having me at APM conference and I'm so super excited to present. I can see some of them are trying to join the session maybe we can wait a couple of like seconds or something to give people to join the session maybe just maybe few seconds more and then I can get started because I can see people. Still joining. Sure. Yeah. Yeah. And then I can give the start. Let me share. Let me quickly share my screen first and yeah. So yeah, I mean I think I'll get started without delaying. I can see a lot of people joining in so yeah. So hello everyone. Good morning and good afternoon and good evening wherever you're joining this session from. I'm Parveen Khan and I'm a senior quality analyst consultant at ThoughtWorks, which is based in London UK. So today, I'm going to share my experience and my learning experience and the talk is all about like you can see the title is a peek into observability from Testers Lens. There might be a lot of you all who already know what observability is or maybe there are a few of you who are new to this. So the purpose or aim of like of this talk is to introduce you all to this topic and to give you some food for thought. So how it could be helpful for Testers. So this is basically my own story. What you can expect from this entire talk is like I'll share my story of how I got introduced to this term and how I learned and how I introduced this in within my team. And I'll also try to share some of the theory part of what exactly it is. So, yeah, let's get started. Before into the jump before even I jump onto the topic of like to say, oh, what this is what is observability and this is how we do it. I really want you to quickly take you through this simple scenario and the credit for this scenario goes to pure of insert from where I took this inspiration from. I like this how he uses examples so I thought, let me use this as well so. So imagine. What would you do if you kind of come across this kind of a foggy road while you're driving in a very weird weather condition. Okay. Think about that. So one thing what comes to your mind. So one thing that comes to our mind is that we need to slow down right. Why do we need to slow down. It's because we don't have the visibility of what's ahead of us, and we kind of consciously make a decision based on the risk, right. If you're not, if we are not able to drive does that mean that we are bad drivers that we can't drive fast enough on a foggy road, not at all right. In fact, we are good drivers because we are making decisions based on the risk. So does that mean that the car isn't good enough to drive faster on this foggy road. Our cars can drive much faster but they but we as drivers has have to just hold them back because we know it's bad to drive when there's no visibility right. So basically in this situation we are kind of ultimately stuck. But how about these planes like these airplanes all the time they all the time fly among the clouds right. So it is because pilots have additional instruments to do that and they don't have to solely rely on their eyes. What now, what is it to do with the software development. Okay, we all know that the current trend is all about going faster and delivering value very faster and we all are kind of trying to adopt certain practices like agile DevOps working in distributed system, working in microservices world. Right, and all they're trying to do is this because we want to deliver something with some value quickly right by doing this, all we are doing is we are building faster cars. The reason why we are moving into microservices architecture or maybe trying to work in distributed systems is because we want to. We want some kind of simplicity while development right, but on the other hand, there's a lot of complexity and there are multiple moving parts at the same time which means it, it is even more complex. So, when distributing a system we are also distributing the places where things might go wrong. So, we know we need visibility, but how can we get the visibility into a system. So, the answer is by having observability. Before even going ahead in trying to understand what observability is let's try to first understand why do we need it in first place. Like, I always try to look for real real life examples to understand like any kind of given concept and I kind of don't get convinced by just reading through some theoretical concepts. I'd like to share my real world experience with you of how I came to an understanding of why we need observability. So, to give you a bit of context, I joined a new team, and the entire team was totally new, and I kind of had an opportunity to join this team and work on a really very exciting and interesting product. It was an automated inverse system which was built on an architect microservices architecture. And it used to like a bit more context was it used to take real time data on a lot of great controllers and to take care of the business credits. So, it was kind of very complex. Okay, the work which we were doing as a team was to build like new features of the way we as a team joined. So, as a tester, when we start working on a new product, what do we try to do? What is the first thing that you try to do? Like, you may try to answer like you may just drop something on the chat like what is the first thing that you try to do whenever you join a new team, and you know that the product is completely new and the domain is new. What is the first thing as a tester we try to do? So, yeah, requirements gathering. So, we read documentation, yeah, I think, yeah, that's what like we try to we try to get the requirements we try to read the documentation to the reason why we read this and try to gather this is because we want to understand the product right yeah understand the architecture yes. So, we want we want to understand the architecture we want to understand the product right, so that's exactly what I was trying to do as well when I joined this new product. So the more I was learning about the product and trying to understand I would feel somehow that oh this is too complex. I had that feeling that this product is too complex. The reason to feel this way was that I had seen some kind of pattern in in in few weeks of me joining that kind of lot of tickets were being marked as blogged. Okay. I saw a lot of production issues each day and like I saw that developers would pick up and I of course I used to play with them. And we used to try to investigate to find the root cause. And the team used to spend quite a lot of time and like spend days and weeks and then mark those tickets as blog as they did not have any kind of information about what is what is causing the issue or like maybe where the issue is. So, that made me think about what's wrong here like you know I stopped thinking that at this point I really stopped thinking that product is complex as an excuse. So interestingly enough, at the same time, I was trying to read a lot about observability without knowing Ben and where it's used. I was reading but I was trying to understand the concept by using like different tools that really promise to deliver this to see what it brings. Having at the same point like having having conversation within my team and with my team member with one of my team member I can say, who was a developer gave me some kind of food for thought that oh this is what we are missing on a product because I had this conversation and why do we why can't we find information about those issues or something. So that's where I got this food for thought that oh this is exactly what we are missing on our product, and that's what is called observability. The conversation was kind of a light bulb moment for me because that kind of unlocked quite a lot of answers to few of my questions but of course it did open up a lot of different questions as well. I understood and I got an answer that we had very less or no visibility into our system, which is why quite a lot of issues were marked as blocked as the team could not debug to figure out the root cause. And because they could not debug, they could not find out any information or they could not say how to fix or what we could do ahead with that. Now that that was the situation where okay that is exactly where I understood okay this is what we need on the system and I tried to I tried to learn a bit more about it. Now we know, I gave you a bit of context about why we needed observability as a team for us. Okay, now I keep talking about observability right now let's take a look into what exactly it is okay. There are quite a lot of definitions that can be found if you Google it, but one of them is a simple one which is like it says that observability is a measure of how well internal states of a system can be inferred from its external output. Okay, it means that you can answer any questions about what's happening on the inside of the system just by observing the outside of the system and without having to ship you code to answer those new questions. But when systems are down, we need to find answers by asking questions as quickly as possible. Okay, and all the way if all we are doing is asking questions and not getting an answer means that there's something lacking. So, the system needs to be observable so that it can explain what what's happening inside. Okay, so, so that we can find out what's not just what's happening inside of the system by just looking at from the outside of outside right. The question is, how can we make the system observable and how can we make the system visible. The answer to that is by using the data that now how can we get the data and you might think like Oh, how can we get the data and what type of the data do we need to make the system observable. So, we can get the data to make the system observable by adding instrumentation and that instrumentation can give us the data that can be in the form of either it could be in the form of logs it could be in the form of traces or it could be in the form of metrics. Okay, now I'll pause the story a bit here and then I want to talk a little bit more in detail about what exactly logs are and what are traces and what are metrics to understand more about this, how we could use this kind of data to make the system more observable. So, first let's look at logs, what are logs. A log, you might have already seen this quite a lot of people might already make use of this like a log is a simple message which has some kind of information right. It might be, it might be a timestamp like you know a simple, a simple piece of information where it has a timestamp and has a payload, which can help us to give more context right but looking at the logs. It might help us giving more context like it might give us information about it depends on what we log right it gives information about which service is it coming from. What has it done so some kind of a payload and at what time did it occur so kind of this is what the log is. Again, getting back to, again, if we are talking about distributed system. We do not want to get into like each service and try to look into the logs. So, rather than having logs for each services differently, we need to have log, we need to have them centralized at one place so it's, it is easier for us okay. It's not about just having some logs in place to make this is observable, but it is about having centralized logs. Let me give you an example of why I think why I am saying that we need to have centralized log okay. So while I was working with this team. We used to have logs like it's not that we never had logs we used to have logs, we, but they were stored separately for each service, and we used and log for that, and to access those logs. We had to get into SSH into each of those services, and the only way to view the list of the entire logs was by using not bad plus plus. Whenever there was an issue, like you know whenever we wanted to find out something what's going on, we would end up having multiple not pass not bad plus plus tabs open. And it was like such a pain and add to the way we could search and to add to that pain, the only way we could search. If they like you know if you want to search something from the logs it was control f like can you imagine how painful that was. And this is the reason why we should, it's not about just having logs but this is the reason why we should have logs that are easily searchable. And the way it can be easily searchable is by having structured logs. So, at this point we kind of had, like, you know, having to get into each service like by the time we move around for different service to look at what information is it is giving us. We kind of get lost of the like you know we lose the context. So that is the reason why we need to have all the logs in a centralized place so that they are easily searchable. Now, after looking at the logs now let's look at metrics. Metrics could be like you know it is kind of a very simple friending number or you can say it's it's kind of a simple value that can express the data about the system. So, these metrics, like, you can see like these metrics would represent different things right. Like, they might be like system metrics, you might have some application metrics you might have some business metrics. So usually they kind of are calculated over a period of time. For example, if you say a system metric can tell you how much memory is used by a process out of like in total. Okay. An application metric could be something like showing the number of requests per second being handled by a service or it could be anything like error rate of an API. For example of a business business metric could be something like Oh, how long does it take for a user to log in or how long does it take for a user to navigate between different, different pages like something like that. Okay, depending on the product you have. So, metrics are really good at aggregating things but not really good at pinpointing specific detail about something like Oh, at this particular time this is the customer who was having the problem. How could we do that. It is by using some more data right in the form of traces the next thing to understand is traces. So trace is kind of traces are something like it is kind of telling a story, which kind of gives you more level of details. Okay, it shows the entire flow of the request and I think it's kind of really very valuable while, while debugging. So, a sting, a single phrase shows the activity for an individual transaction or you can say as for individual request or an event as it flows through an application. It kind of shows the end to end request and and phrases are really critical part of observability as they provide a lot of context. Okay, so I have been saying quite a lot of time that you might have noticed that with observability we can ask questions, but what kind of questions can we ask. Okay, I'll give you an example, I'll give you some, it could be any kind of questions depending on the context of your product you're working on but I'll give you some of the examples of what kind of questions we can ask to find the answer if we have system, or visibility of the system. Okay, it could be like, Oh, why is X broken, why is my service broken. What went wrong during these, what went wrong during the release like you know, or it could be like what other services dependent on my service like you know where for example if you're working on a one single service. And what when, why has the performance degraded over the past quarter, what log should we look for right now when there is some kind of issue or what did my service look like at point X. So these are some of the examples which you could, you could ask while, if you have while looking at the logs or by looking at the traces. So just like, just like how we talk about DevOps, we cannot say that we are doing or we are adopting or we are following DevOps by just saying, but by just having some automated tools in place. It is more than tools right it is more than it is, it is a cultural mindset change, right. Similarly, we cannot say that we are following or approaching or doing observability by just having different tools in place. It is not just about getting the tools and having lots of data in place and saying that Oh, we are. We are following observability or our system is observable. It's not about that it's a it's a it's a cultural change and it's a mindset change as well. Now, I'm sure we all are testers right now, most of us among the audience are testers right so now you might be thinking like, Okay, we get it observability is this and that fine but now what what's in for testers with all this observability and all these new tools in place. Why what how does it help testers right so it makes easier to find more information around issues like I'll give you some of those some of those benefits I can say not all of them but some of them. So one of them would be easier to find information around issues so for example, while we are testing we might see some kind of unexpected behavior or maybe we kind of see some failures right. So having these kind of having these kind of tools in place. Kind of allows us to look under the hood to find what's happening with each of the requests, like you know, and not just that it allows us to learn more about a system and how it helps us in learning how it communicates and books. I mean, the more previously like the more I would use is the depth tools to see what's going on. When something did not look right to me while I was testing but I wouldn't get enough information so by having these tools help me in getting more information that can be like for example added to the tickets like you know when while we are raising the bugs or while having the conversation with the team, when like you know which might help the team to understand to give more context and information around any kind of issue right. It's not just about finding more information while looking for looking into the issues but it could also help us uncover understanding of our products. Testers like it could be another reason another help or another useful benefit of benefit of this would be for testers would be like a tool for exploring and asking questions. Now how many of you all think that we are testers are curious explorers. You can just drop drop something in the chat saying like you know, do you think testers are curious explorers. Yes. Yeah, they have to be yes of course yeah. So I think we testers are very curious explorers and we are great at asking questions right as a tester. I mean of course I'm sure we all like I tend to ask a lot of questions when I don't understand things. So, as we know the as we say that testers are great at exploratory testing, not just good at asking questions but the testers are always curious to find more information about the system right. While exploring the logs and metrics and any kind of like these kind of data testers might point out more point out where more instrumentation is needed, and not just that, but it also supports and helps testers for testing in production. So it kind of allows a team not just to shift left but shift right. Like for example like you know when it's not just like you're making use of the data but you be as testers while testing and you're making use of those logs or metrics or any kind of data. We might say that oh we are not finding any of information. When something is gone wrong can we improve our instrumentation can we improve our log so that I can see what's going behind so that whenever there's this kind of issue is in production then we would know there is enough information to figure out. Now I'm not saying that if you have logs. It's always like we will able to find everything but it might help. So we as testers, because we are very curious explorers we explore the entire product. We might also try to add the value of improving our instrumentation when needed. Like I saw this tweet and I really like how Marit has put this together saying that a lot of times, good debugging and good exploratory testing are both indistinguishable. Okay. So when, when the developer explores, they call it more often as debugging. Whether they know there is a problem or this kind of suspect there is there is a problem what do developers or anyone like you know, while debugging what do they do do they know that where the problem is no right they try to find where the problem is that's what exactly debugging is. So when testers explores the same debugging is close to the last word, right it is similarly like we don't know, like we don't know but still we are trying to explore and learn more about the system. So, to kind of like summarize. I would say by making, by making systems more observable anyone on the team can easily navigate from the effect of the course in the product of the system. Okay, it. I'm not saying that you get the answers straight away but it makes it easier to debug. The goal of observability is not just to collect logs, metrics and places, but using the data to get the feedback. And it just doesn't allow us to find the knowns of the system, but also allows us to know and find out unknown unknowns. Okay, it's not because it's not all about what we know. What we know about the system and we found out what we know right it is more than that so it is all about finding the unknown unknowns and making system observable will help us in figuring out what are the unknown unknowns of our system of our product of our application. And, like, every learning experience or every story or every journey has something to take away right. So, even I had some, I had some of the takeaways to out of this learning experience while trying to, while trying to understand why I was trying to learn, and why I was trying to implement these within my team, thinking outside the box. So, the key takeaway for me is that we as testers can, can go out of the way, like you know, I think we care and advocate about quality and that could be related to like the way we try to bring and like if you see something wrong or if you want to improve our quality. It could be different ways we try to improve that like right. So it could be like, we try to improve bring improvements in the process, maybe bringing in the new tools ready to test automation, but that's not the limit. I learned that we do not have to limit ourselves and say that okay, like you know this is not related to testing so let's not look into this, or let's not learn about it. So, while throughout this experience throughout this process, I saw within my team that I saw that there were problems within my team my team was going through I saw the problems that team was going through. Like, for example, developers were getting frustrated when they could not resolve the production issues and I saw that I noticed and I saw that product owners were getting frustrated for like not having an answer to provide those answers to the client. And they were not having enough information related to those production issues. I didn't know the answer or I didn't know the solution to it, but being active in the community and seeing new tools and the concepts and exploring them and finding and finding the solution and then trying out myself by using different tools.  So, I tried this. So, not limiting myself to just testing tools only and trying to think outside the box to help my team. Before I left that team, we were not there yet in terms of implementation for the entire observability part but we had already we started by after this we had our first step started was like from having visibility to like we had no visibility to having structured and like centralized logs that could be easy that way very easy to query. Like you know how like the steps we took where like smaller steps by starting to get implement the centralized logs first, moving all the logs into one place so that they are easily searchable, then trying to implement some races. So, we took smaller steps one by one to start implementation. So, to end, to end with, I would really like to say that observability gives power to the entire team to get the visibility when needed. It's not, it is not something, it's not a tool that only can, it's not a tool or it's not some, not the data just used only for certain roles for certain people but it helps it gives the power to the entire team when we get the visibility. And observability is much more powerful when you apply like kind of with the right mindset and the clear kind of a process and using different tooling in place. It also allows the teams to it kind of also allows the team to become more productive towards the issues rather than reactive. Again, I'm not saying that that will solve entirely by having observability but quite a lot of time what happens is like we, a lot of time we know there are some kind of issues only when the users complain. So, by, by having these kind of things in place. It kind of allows a team to become even more proactive, rather than being very reactive. So it kind of gives power and kind of empowers everyone on the team whether it's kind of a, again, as I said, like it could be developers, it could be ops engineers, it could be engineers or it could be SREs or it could be testers. And we as testers need to be need to be comfortable using these kind of tools and so that we can learn more about the product we can add value. We can add value to this kind of implementation. So, if there is one thing apart from getting introduced to observability and how this observability is helpful. One thing, one, if there's one more thing that I want you all to take away from my talk today is that we all believe in like we all believe in diversity and having diversity means building powerful solutions right. Then why not have diverse roles like developers, testers, ops engineers or any other roles or SREs be involved while building these kind of solutions, like while building like observability on the system. So this could add so much value when we as a team try to build these kind of solutions rather than just saying that oh this is not something for us and it could be not useful for something for us. So this is one thing I learned throughout this that we as a testers can also add value to this and can also make use of, can make use of these kind of tools and observability. Yeah, thank you so much for joining my session today and I'll be happy to answer if you have any questions and, and yeah be sure to check out my blog site I do blog. I share all my learnings and I share all things at on for being counts.com. This is my blog site and don't forget to follow me on for being underscore content. Again, for joining my session and listening to my story. Thank you for being there was really a great session thanks for you know all those understandings on observability. I learned a lot. I am not basically from the test of background but thank you so much for all those, you know understanding it was quite informative. In terms of questions I I feel the session was awesome nobody has any questions so far it was so good with the examples everything. So, yeah. I think yeah I don't see any questions so yeah. Correct. Being a host potentially you know I can ask some question. If nobody has since I said I'm not from a tester background, purely from black and ingenious perspective. I always had this question probably nice time to ask. So, we do this. Being a developer I generally do unit testing I write you know component testing component test integration test etc function test. I always, you know used to wonder how you know q is when they write their test etc how you know they are different. And, you know what we do all whether the roles are actually quite emerging in one on the other.  Yeah, so you mean to say is like how like yeah come again can you come again the last part because I was just trying to stop my screen chain like you want to see like how testers can, how, how do they can you just repeat that part please sorry I'm so sorry. Hey, no worries, no worries. So just to repeat. So it's quite abstract by the way, the question is quite abstract. The idea is that we always write this unit test you know developers writing the test and developers do those debugging and when testers are doing exploratory testing you know some of that merges for a period of time. So on the similar lines it's like when you know we, you know, do sort of a TDD BDD, you know we write test. Yeah, yeah, yeah, duration test etc. I always wanted to know what would be the mindset of, you know, a tester per se when when they do the QA, right, with what sort of a mindset and how does it differ from the developers mindset. So that would basically help me to understand the two roles, you know, different. Yeah, yeah, I think, yeah. I think you're trying to understand the mindset. Yeah, I mean, it's, it's, it's hard to explain but one thing I would say is like, I think as a tester that's what I was mentioning during my talk like how this concept will help us is because like, we have this mindset of like, asking those questions being curious about how our users are going to use this when it's like when we release it's like for example if you're working on any kind of a feature. When I'm testing that feature, and I'm looking at the different layers, even though I'm looking at the different layers it could be API is a code or pairing with the devs on the unit test level. I always have that user hat on me and always have that curiosity hat on me saying that okay why are we doing this why are we doing that. So I think having that kind of a mindset always, that is more of like, you know, while exploring users, mine is always in our like, you know, whatever we are testing so that's, that's one thing I would say like that's how the mindset would be like you know when we are testing how differs like I don't know how exactly the mindset of developers is while they are actually writing the code or like, while they're implementing the feature what they think about. But when we as tester I can talk about everyone on like as testers but I think it is very quite common that when we are exploring we make sure that we try to use different personas like not just one Oh this is a user and he will use he or she will use it in this way, but trying to understand trying to think from different personas point of view, how and like you know and trying to see how the journeys would look like you know not not just that simple piece of puzzle like you know we look at the picture not just the one single piece of puzzle or if that puzzle works fine. That's it yay no. I think we look at the entire picture and then try to look from different personas and different user perspective and I think that's that's how if I say some of the general thinking kind like you think that's how I would say yeah. Perfect. I think yeah that that answers my question. Thank you for that. Thank you so much for that. So, oh, I think we have one question now. I think that's more of like an answer to work for me. That's correct. That's that summarizes what we have just mentioned. Yeah. Thanks. Yeah. So, yeah, I think we are we are pretty much at the end then I think if there are no more questions. And even if you if even if you don't have any questions maybe people can still like if people ask I can see still people around so you can just drop in some kind of conversation and it could be conversation not kind of a question as well. Even that is fine. Yeah, I can see Serena saying that they think around to make make things work, but we testers think around to found H cases to break it exactly. I do agree. Yeah, I do agree not exactly like yeah we try to break it in the sense of like just trying to break it no but just trying to see if it breaks it in some different kind of H cases if people are like if different users are using it. So I do agree with that yeah. Correct. I think so yeah I think that's like pretty much end of first session. Thank you for being for sharing your experience with us today. Thank you so much for having me and thank you so much for being an amazing host.