Okay, let's talk about something other than your music.  Tell me about your music and what do you think about it? What I'm doing is pretty much a lot of things. Sorry, sorry. I'm not a doctor. Now say it. I think I thank you for your advice.  You know, having to go through a children's home and growing up in a children's home and coming back to my mother, living in Islam and all those things.  And my life is all around me.  I'm not a street boy anymore. I'm a street boy. I'm not around my brother or my sister anymore. The biggest problem right now is that I can go to你看 the city for everyone except for children. It feels like I need a conversations. And I thought for a while I would talk to the government about I love to share my life. It feels like I'm not traveling because I don't understand how it feels to live in a child's home, to live in the streets. For me the music is ministry. It's entertainment. the vibe in the trap, others will feel the melody, but it doesn't get the real impact as now doing something to that person, you understand? So that after you have ministered to them, the ministry that you have done is enough as far as the heart and the soul is concerned, but now physically, umsya nanin kudishi mazee, understand? Umsya nanin kula la place, aji funi ke. Naizu azizu kujya through music, come on as I go to the pocket and be able to bless. So for me, it's not because I have much, but because I love a banana, ele uchungu yaku ishi apu evu. Now, especially for the ones that I have been visiting, kuna zilevi tu ana go through ze n'ya nanajo, min ko maali banana, n'aji funi ka banana, n'a la la fit, yara sa zingine si lali, but ni kona bed, ni ko keja fit, ni ni is of tuzote, zilesis to me, nakunam si ana itaji mazee, aki pata, ni ata kama ni bed, si tifu, ata feel fit imazee, understand? So being the doctor, I am living not for myself, but for other people who need the treatment, I say, hey, ata nai itaji kutibi waba.  So you na maa ni siya bomba, a wu gishi we mo nye we, batun nai si ko saba be a twingine, so that now when I am done with music, if I'd ever be done with music, I would just sit down and look at the things that I have done for other people, and you know the kids that I have grown in music and feel like, you know, me achieve. When you're eloquent, have you ever been a public speaker? No, I haven't. Really? You should think about it. Okay, sasa, music in touch, yana anyway. I have a special question for you, and I want to phrase this in honesty and in truth. But what do I put on someone on a work or a gospel industry? I ask them a question that I think I should ask you. Thank you. You know a gospel industry? Is there any gospel industry in your music that you call it? Kattel? No, I'm not. I'm not a gospel artist. You don't know any other than that? I'm not an outgrow Kattel. What does that mean? I'm not a Kattel artist. I can't even be born in Kattel. 28 28 28 28 28 28 8 28 28 28 29 29 30 30 32 33 34 34 34 35 36 37 34 35 37 39 a but I'm the journalist. I think I'll prepare Mr. Dukanya Shinski, sit down and do it for us. Congratulations to him. He's a great guy. Congratulations to him. He's a great guy. Congratulations to him. He's a great guy. But I think it's because of the gospel song. So you think it's because of the random gospel song and contemporary. Do you think it's because of the random song? Because it's called Keshav. Yes, I think it's because of the music. Where is that strictly? I think it's because of the music. I don't know. I don't know. I don't know. I think it's because of the music. Let me tell you one thing. This music from the heart goes to the heart. And most of the time it's just music that comes out of the heart. The Bible says that out of the abundance of the heart, the mouth speaks, you understand? So if I sing a secular song, if I sing a secular song, it's out of the abundance of my heart. Now my heart is fully in abundance of the Word of God. So I think it's because of the music. Do you think it's because of the soul? Yes. Because of the soul, I think it's because of the music. Really? Yes. I'll see you. It's because of the music that comes out of the heart. Shout out, Vendrick, that if the president of the Republic of Kenya was to ask you, what is your favorite song, Eako, when you? It's the name of the song. I don't know if I can perform it or not. I don't understand the energy in it, for all of them. Because the song is a song that touches my heart, as an individual song, it touches my heart. So, I wouldn't say that I have a really specific one, because all of them speak to me at a specific time, and they speak to me very greatly. So, Zotan has spanned a tool. I think now they know the new song. Now we have a test today. Hi, hi, how are you? Fine. So, come and play with us. Come and have fun with us. We have a DM and we are here to help you. I told you a special guy. But I want you to know why I told you a special guy. I will tell you. I know you are going to give me a lot of comments, but I don't know what to say. I know you are going to give me a lot of comments, but I don't know what to say. I don't know what to say. I don't know what to say. I don't know what to say. So, this is with Joe. Guardian Angel knows your name. Hey, Raka Raka, the box 254. Quick, quick, quick, quick. That's a true message from Guardian. Let's help each other. Help me today. I help you tomorrow. And in a favour, I don't know about Kesho. Quesli? Very well. You know, you are not going to give up. Yes. Do you know how to give up? No. You are not going to give up. But if you don't give up. Joe, you are going to give me a lot of comments. What are you doing? I am giving you a lot of comments. You know, you are going to give me a lot of comments. Hey, we have wisdom again. What a surprise. I'm going to say again, what a surprise. He says, Episode 2! Weze Joe. Weze Joe. Weze Joe. Weze Joe. Weze Joe. Weze Joe. Weze Joe. Weze Joe. Weze Joe. Weze Joe. Weze Joe. Why are you calling me? He is a horse man this one. Ok. So we are going to ask him, and it's from Guardian Angel. Now, we want to ask him, is he a Jin or a Jin? Yes. He is a Jin. Not a Jin. Ok. So, where is the skin, where is the insides? Oh, at the Bounce 254 Facebook Instagram. So, let me tell him that he is a Jin. Oh. I get his number. I want to get him a hoodie for a neighbouring, in my name, so. Hmm. Hmm. Thank you so much for coming. Would you like to? That's not it. Oh! I was telling Kingsy, it was a long, long story. One woman came to Kumbusha when she was turned into a wengie in town. And according to the census, it is apparently true. There's research that says that if someone comes to Kiyanza here, my life will turn into a wengie. But at the end of the day, no one will come to Kuyasha. And one of the causes is depression. And it's the stories of the people who are suffering from it. And since you've been from extreme situations, what are your thoughts on this? Hmm. My name is Dave. Hmm. Hmm. Quaili? Hmm. Hmm. Hmm. Hmm. Hmm. Mother Akkai, you are the recipient of your bed. Understand? If you have a home, say, if you have a home, say, if you have a bedroom, if you have a kitchen, if you have a stretch queue, if you have an engine, you know? But we're serious. Well, we all say, if you want to check, you can do it. If you want to do it, you can do it. If you want to leave, you can do it. Understand? But Joe, this is one awesome thing about having faith in God. God says that He only has a good purpose for you, and He will give you a future, and He will give you hope. He says, He knew you before He formed you, and this is for everyone. He does not select you, but for everyone. And it depends on you. So, Mother, if you have a future, you can hope. If you have a future, you can do it before you leave.  So, if you have a future, God will create it. If you have a future, you can do it. If you have a future, you can do it. If you have a future, if you have a future, you can do it. I raise my hand to pray for God, to fly. So for the future and for the hope that he has for you right now I am fit to live God have many blessed my mother my mother my mother my mother my mother my mother is a nurse in Canada the same guys life is I am a person who is not fit to live I am fit to live God have many blessed me right now so if I speak to someone who is not fit to live there is no reason to give up in life because if you believe in God at the end of the day you will be able to fly and you will be able to fly and you will be able to fly by that when the end of time you will be able to do that so we ask God to accept everything we? we do it we do it I also mess about and we talk about I also face brain we have to make sure the person is not to be present in life So it is a good way where I laugh out loud because we are still here on Hashtag Bounce Nation.


OK, am I audible? Sorry, I'm not using a mic because I have to do some coding. So I'm not using a mic. If I'm not audible, let me know. I'll try to use a mic. So today I'm going to show you how we actually build a simple block and also deploy. So I'm going to use a Jamstack here. So the Jamstack is, as you are aware, like it's a JavaScript, APIs, and mockup. I'm going to use a Gatsby. Instead of talking much, let's jump on to a demo and very quickly let's build a block. So I have a very basic setup here. So I have some dependencies Gatsby and Gatsby source file system. So I'll explain why I needed that and transform and remark with React and React DOM, obviously. So just to give an introduction of the Gatsby, it's built on top of React to make things very easier. And also it uses the GraphQL to fix some data, to read the data, to read any information about our site. So very quickly, so the Gatsby needed a source folder, SRC folder, and pages. So this is the pages. So whatever you put in within the pages will be rendered as a separate HTML page. So once you build it, it will be separate HTML page. Like say, for example, the index.js is a main HTML page, which will be rendered the moment that you land on to your website. So here I have a very simple component, which actually shows you the hello world. On top of it, there is a layout component. So the layout component is just I have some header and then main. It's very simple. So let me quickly show you. So when you say Gatsby developed, so it's basically Gatsby developed, it takes all your pages and then renders it to a HTML file. So the moment I'll go here, so it renders my layout component. Layout component contains my header and as well as the content of my blog. And it also comes with the GraphQL IDE, so where you can actually query all information about your website. So I'm going to actually show you what I can query in later stage. Let's jump on here. Like say, for example, as I mentioned, I can create another page. Let me create a about page and call it subot me and come here and say slash about. So that's simple it is. So you create a page and then you can easily query the page also. Like say, for example, I don't want to actually keep that my blog. It has to be very dynamic so that I can easily ship, make things changes dynamically. Let me introduce you to the gatsbyconfig.js file, so which is a very specific configuration that is required by the Gatsby to maintain your configs as well as your plugin system, the Gatsby plugin system. So I'll very quickly show you how it looks. So I have a small code here. Let me create a file. So Gatsby config, it has to be in this format. The very first thing is the site metadata which shows you the title. I'm going to replace my blog with this title. And also I have few plugins which I'll come to that part later. So let me quickly go here. So how do I actually query this title? So using GraphQL, I have to query this title. So since I have added the Gatsby config, I have to rebuild. So let me run this again. Now I can go to my GraphQL interface. This has added more information about my site. Like say, for example, let's take the site. And you can see the site metadata. This has been added now. And you can query the title. So now I can get this information. Let me quickly take this query and then go to... So I'm going to, you know, I'm sorry. So there is a... Sorry. There is a use static query from the Gatsby. This is a simple hook which lets you to query static information of your site. Like say, for example, the site metadata is a static information which you can query from the components, not from the pages. So you cannot use the use static query from the pages. So that means like index.js or about.js. Any file within the pages folder, you cannot query the static information. So that is the reason I'm putting it into the layout component. So this is, as I mentioned, it's a GraphQL. Very quickly I replaced this with site and site metadata and title. So that's simple it is. Now let's jump on to the... OK. So now I have a very basic setup of my website. Now I want to make it as a blog. So I should be able to write posts and then post it to my blog. To do that, I want to actually write posts on using the mockdown because that is very simple for me to, you know, instead of putting into different HTML files and all those stuff, I'm going to put it into the mockdown. So I already have a few mockdowns here. So like say for example, first post and my second post, it's the same content. I mean different content by the way. The only thing is that the same format. So title and date. So these are the kind of meta information of the particular post. So you can add any information here. You can add tags also. Just for a preview, I'm going to keep these two information. As I mentioned, like coming back to the Gatsby config, the Gatsby source file system is a plugin, Gatsby plugin, which lets you to read all the files from your data folder. So I have mentioned here from that to, you know, read the information. So that's what I had given here. So if you look at this, okay, and also there is a Gatsby transformer remark plugin, which helps you to convert your mockdown to a HTML content. So whatever you write it in a mockdown file, it will be converted to a HTML content. So these two plugins will be helping me now. And let's go back. You can see the all mockdown remark that has been added now after you add the plugin and which will help you to go to the nodes and front matter. So you can query the date and title here. Like say, for example, I want to query date as month, DD, and here. And also I want to query the excerpt. So there is an excerpt also. Excerpt lets you to give the only few characters of your content. So query, you get all this information on your write, your date, title from your mockdown, and also the content. So just for a time sake, I'm going to quickly replace my index.js here and explain this. So this is the same query that I used in the GraphiQL interface. And here I just replaced with the just coring that information. So if you look at here, I'm not using a use static query here. This is a page query basically because I'm coring from the page. And let's go here very quickly. So whatever the blog post that I'm writing, I'll be able to publish it in this way. So very quickly, let me show you Gatsby node. Now I have a home page which lists down all my posts. Now it should be clickable and read the entire content of each post. So for that, I have to build my pages dynamically because every post is a single HTML file. So that means I have to build these pages dynamically. So to build those pages, I use Gatsby's Create Pages API, which let you to query some information. Say for example, there is a slug. But by default, there is no slug from your mockdown. So what I have to do is I have to dynamically build this slug from my existing mockdown remark. So that is what the create node does. So I'm taking the mockdown remark type. So there are many internal types. So I'm just reading only the mockdown remark type. And I'm creating a slug. So and then I'm coring the slug. I'm creating the pages basically. But if you look at this here. So I'm having a source template and post.js. So what it does is I'm going to create a one single file which accesses a template for my post page. So let me quickly show you that page. So here again, I'm using the same kind of graphical query. But only thing is that instead of all mockdown remark, I'm coring only for a mockdown remark with a variable. So say for example, here the slug. Slug is the first, sorry, here it has to be the dollar slug. And the variable should be slug and string. So this is the variable. I'm passing the slug. And it will be replaced. So the variable value will be substituted. And I'll be getting the information. How do I pass this slug? If you come back to the Gatsby node, there is a context field which lets you to pass this slug to your page, to your template via the query. I'm going to quickly, oh, I'm sorry here. So let me build it successfully. So I have to add a link, but sorry. So now I can render the entire template here. So this is done. Now very quickly, I'm going to deploy using a now. So hope you know how to use now. So I have a now CLI. It's a Zeeds now. So I'm going to deploy. So we build a block and just I do a now. It actually builds my Gatsby and then deploys into the cloud CDN. You can actually view the logs at runtime while it is building. So this is very handy because now with all this tool set, I can build the blocks very quickly. I can build my web set very quickly and also deploy. And this now is very easy for us to deploy it in a very speed in a couple of seconds. It's almost ready now. Yeah, the Gatsby build is running. All right, yeah, done. So let's open. OK, yeah. So it's now in an internet. Thank you. Sorry, I took more time.


Hello Welcome to the last but one. I think talk of our jolyndia 2018. Have you had a good conference? Yeah, thank you for the organizers. It's been brilliant So thank you for coming to this one choosing my talk. I'm gonna be talking today about evolutionary architecture I'm gonna be talking about How I think these days we can Take a different approach to designing and building Software systems actually quite complicated software systems as well based on uncovering architecture as we go so How many in the room were at Gregor's? Keynotes yesterday So some excellent. So in that keynote Gregor mentioned something called real options option theory about decisions and why decisions and Keeping our options open might have value Or have value intrinsic value and how in an increasingly volatile world where change happens well where we require Change to happen more regularly Actually options and having options and keeping options open. It actually has more value So that's kind of what this talk is about That's the betting part of this talk betting on evolutionary architecture How can we place small bets keeping our options open place in small bets? In order to drive the design of our system This the subtitle a note on software architecture as code is about well Martin Fowler always sort of described software architecture is the stuff that's hard to change about piece of software about an application or a state of application And I think that there's a number of techniques that and practices that we've sort of developed over the last probably even only three years That enable us to make changes to those things that were formerly hard to change in very simple ways So this talk is about keeping our options open place in small bets and how we can make small changes Based on essentially the scientific methods. So can we run experiments on our code bases to help us make better decisions? I should oh, it's back. Yeah back in the room. I Should probably explain who I am first. So this talk is only tangentially about microservices I wrote this thing with Martin and work for a company called ThoughtWorks. So I maybe have a hand up for those of you in the room who know ThoughtWorks Sorry, I probably don't need to explain to most people but we're a bespoke software development company We started about 25 years ago about 5,000 or so people now globally We've got a very big center in Bangalore, although annoyingly. It's my first time first time to Bangalore I've been to Chennai our Chennai offices before but I think there's pretty about 800 people or so in Bangalore now if not more So that's what we do. We write software for people. We solve hard problems and we advise our clients on Best approaches to I guess take advantage of the market volatility that we see I wrote this thing. It's quite interesting You can blame Fred for the name and blame me for writing it all down So I'd like to start with a question Torrible question, I guess how do we usually make decisions about architecture design performance some of the critical characteristics of our systems And I would argue in general we make them in a couple of different ways We make them based on experience This is good. You know as you get more experience and you take on more I guess more experienced roles And you have more responsibility for the design of software Hopefully the experience you've had over time building software helps you make better decisions This is good actually, right? So there's a thing called the drapes model of skill acquisition as you do a thing more regularly You develop that skill Until you become an expert in it. If you've read the pragmatic programmers book on I think it's called Refactoring your wetwear something like that. That's the subtitle they talk about the 10,000 hours You need to become an expert if you've got 10,000 hours in software architecture building software Then you know making decisions based on experience is good But it also comes with a downside because we have something there is something called survivorship bias This is one of a number of cognitive biases that we can't help but fall Pray to survivorship bias says we're more likely essentially to make a decision based on our previous successful experiences So even though experience is good it can also steer the way our decisions go in the future We had a successful project. I'll do the next one exactly the same way that kind of thing We also do it based on gut feel I think this feels like the right solution Especially as we're in this sort of drapes level of expertise You know, we've got this insight that this feels like the right sort of thing and drapes You know drapes the drapes model suggests that as you become an expert in something This is actually a good thing to trust your instincts more But see point one survivorship bias. It can lie to you. Your gut feel can lie And oftentimes we decide things up front And this is a legacy often of the sort of scar tissue we've built up as an industry that makes us think changing things later is hard And actually changing things later has been hard Especially decisions about things like software architecture the stuff that's fundamentally hard to change But I think and hopefully I'll go through some example an example of why that's different. I think now So this is the question. I'm hoping to answer over the course of this talk Can we make design decisions more systematically and if we could what would that look like? And the way I'm going to explore this question is by reading a book What a strange idea so who in the room has come across the idea or the type of book called choose your own adventure Okay, not so many people. So this was something that was very popular when I was growing up I guess in the sort of late 70s early 80s in I guess the UK the US And this type of book it's interesting right because they tend to be set in sort of fantasy worlds Populated by dragons wizards mystical beings and things and that the aim of the book generally is to is is to set yourself up as a hero and To take decisions a bit like role playing dungeons and dragons or something like that To help out a village or to smite a mighty dragon or to find a horde of gold And when I was trying to work out how best To talk about evolutionary architecture and the sort of decisions we make I was searching online I found I found one of these books about evolutionary architecture What a strange strange thing and it's called the endlessly bifurcating trousers of reality Now I think in our industry we don't tell stories often enough I actually think stories are a really powerful way of communicating the decisions that we've made and the our experiences that we've had In fact a former colleague who's think now still at Facebook by Google and then ThoughtWorks before that He talks about the idea of having a team shaman who can gather the team around and tell you the story of how things on your project got that way I like that idea and this is a book about a particular project Tells the story of that project of some decisions that we made so let's see what happens when we dive in The lawful good product owners of a publishing house had long lived in awe and fear of their publishing systems In all they had made a tremendous amount of gold and in fear of a time taken to change them That their slowness and their fragility a messenger was sent to Falsch help from a distant land of Mighty wizards you have taken up this challenge Maybe I should give you some context about what this story is about so a couple of years ago now I was involved in rebuilding replatforming rearchitecting a very successful 15-year-old publishing system for a scientific publishing house Very successful. It was making upwards of one and a half depending on the year one and a half to two billion dollars a year Very so you know pretty good But it was a 15-year-old C++ service-oriented architecture that was becoming increasingly difficult to change And so we were asked to come in and see if we could help out by rebuilding this system. This is what the stories about You must save the product owners by rebuilding their website You start off the project in the course of discussions. You discover that your goals are threefold You need to improve availability improve performance and reduce the cost of delay An enterprise architect approaches and addresses you you may use some and walk-in skeleton Or you may cast analysis paralysis Or you may if you have none of these things you'll have to draw your sword and fight I should unpack this right so in publishing is kind of interesting especially scientific publishing Availability is directly tied to how much your company is worth And that's because you have to prove essentially how many people have clicked on a link and downloaded a scientific paper And then you attribute that click to an organization That's that's purchased access to your site and you charge them And actually the CEOs of these companies will report shortly to the stock markets Basically how many people have clicked on links? It's kind of interesting. So any time your site is down Globally, someone isn't going to be able to click on the link and that directly leads to a loss of revenue and actually to your share price Precinct or not increasing at the right rate need to improve performance Turns out China is a thing India is a thing you know Australia is a thing and this particular website was hosted out of a data center in the West of the United States and so performance in places like China places like India places like Australia especially in Australia where they have to Still bust the internet in on ships with USB sticks as true I don't know if you know that But improve a performance was was a pain up to 15 seconds for page load and they wanted to reduce the cost of delay Improve the cost of delay so they wanted to make be able to make changes to their system more rapidly They wanted to be able to deliver more value more quickly to be able to deliver more value to their customers more quickly So what should we do? We could summon a walk-in skeleton We can cast analysis paralysis So a walk-in skeleton if you haven't come across this before is the thinnest slice through your system that you could make To prove out your path to production and to prove out the first User story or requirement that you're writing. What should we do walk-in skeleton hands up? analysis paralysis Really don't care Yeah, that's most of you okay excellent right well in this case what we did is cast analysis paralysis You cast analysis paralysis at the enterprise architect foolish young adventurer says the architect We follow the evolutionary school of architecture and we shall have none of the lawful evil ways of waterfall The last thing you see before everything goes dark is the architecting counting in a strange voice You have died to turn to page one Oh dear So perhaps we'll summon a walk-in skeleton instead walking skeleton is a fairly well understood sort of practice. I can't remember the Exact derivation, but I know that price and Steve Freeman talk about it in their seminal book on Test driven design growing object-oriented systems guided by tests So we'll summon a walk-in skeleton and see what happens Your walk-in skeleton coalesces in a cloud of noxious gases and solidifies as a Java drop wizard application You reach into your backpack and deploy a content store Your walk-in skeleton reaches out its skeletal arms and grabs armfuls of raw XML Would you like to transform the XML inside the microservice the skeleton or use a magic box another microservice? So generally in publishing what happens is you have a publishing pipeline where you have a set of documents There are editors submitted by researchers Editors editors lots of reviews go on and then it's turned into a big pile of XML and pushed through to some store Where you need it to be transformed and displayed to your users in our case all this content was pushed into s3 We had a giant enormous number of XML documents sitting in sitting in x3 and we had to transform these somehow into html So we can show our users and you know we can take different decisions at this point We can either inside our our single application that we've already created We can write some functions in there Maybe create a module that will do the transformation display the html to our user or we can We can separate that concern into a separate service. We push that into another microservice And that's interesting because this is the first point at which we've got options about where to go This is the first point we can start to think about the bets that we can place the different decisions that we can make This is a divergent evolutionary graph showing how species diverge over time And actually this is kind of an imaginary look at the future states for this system based on the decisions that we can make At one point we might be able to we might decide to transform the content within a module in the walking skeleton But we also you know on the other hand might say we'll create this extra micro microservice And at this point we're diverging the architecture that we're building this design of our system is diverging and you know Reduct your out of pseudom if you go down one path you end up with a distributed system composed of a number of microservices But if you get on the other path you end up with that sort of monolithic NBC type app everything is Is contained within that single application? And this is what I mean about options about placing small bets, how do you decide which path to follow? So I call this betting on evolutionary architecture So what's the definition of bet? The act of gambling money on the outcome of a race game or other unpredictable event That's a good deal of betting of races going on. I guess that's quite apt being that I think we're at number one race course road at the moment That's the act of placing us placing a bet on some on some outcome that we don't know about yes Unpredictable event and a lot of people think that building software is predictable You know certainly most of the project managers I've ever worked with Think that's predicting software that building software is a predictable thing But actually what we're talking about when we're building software. We're talking about a complex adaptive system By definition by definition. It's unpredictable. What's going to happen in a complex adaptive system? We've got a number of people involved in building this we've got a number of decisions that we can make Complex adaptive system. It's unpredictable by its nature and becoming more so as business requirements change at an ever-increasing rate Betting on evolutionary architecture So I would argue that the idea of an evolutionary approach to architecture allows us to place small bets and Then reevaluate our decisions based on the outcomes of those bets This is the options that Gregor was talking about. We can create options for what we do in the future We can have a number of different options each of these is going to have associated a cost and a value Have to spend some money to do this thing, but it's if we but if this thing if the bet If the bet is a successful bet and we've correctly predicted the outcome then we're going to get we're going to get some value back In comparison the idea of this upfront design phase that we do on a lot of projects This is sort of the equivalent of betting the house, right? We're going to guess at the start of a project exactly What the finished end state should be we're going to place all our money on a single bet bet the house I don't like that in my house. I quite like my house Maybe I'm not just a betting. I'm just not not a betting man So back to the story What we decided to do was create another microservice. That was the option that we purchased and You throw the magic box in between the walking skeleton in the content store a villager approaches and exclaims this beautiful content I see before me takes an awful long time to get here You must somehow make the content arrive faster if you have an HTTP cache in your inventory you may use it now And we've gone again got a number of options because distributed system. We've created options actually by creating a distributed system We can cash in between s3 where our XML is and the content micro service or we can cash between The sort of proxy fronting stuff and our micro service the content that the content micro service that's doing the transformation This is what you know in a naughty way this sort of architecture looks like we had some sort of templating basically edge side includes templating application at the top little micro service that was just doing Returning html to our users that we have this computationally expensive service Which was using one of the greatest functional languages of all time XSLT And that was transforming the XML into some html then we had some XML in x3 and we had a bunch of stuff Bunch of other services And when I said about you know availability performance and things these these are the performance requirements that we had for our users globally It was a 0.8 seconds time to first bite One and a half seconds page loads no matter where you were in the world So pretty pretty stringent constraints and when we first started testing whether we were meeting these cross-functional requirements We got this sort of answer out So our page load time was about 35 seconds Now I mean I'm a physicist not a mathematician, but I'm pretty sure that 35 is greater than one and a half That we can we can all agree that that is a thing Which is bad right this is this is kind of a bad thing hence us thinking about caching That's just thinking about where are we gonna put this cash? Are we gonna put it in front of the computationally expensive service all behind it? Let's put some caching in So again, we've reached one of these decision points right where we've got a number of options up Detective performance problems Let's just add a cache Now the thing about caching Who's implemented a cache in the room? Right, okay a few people How many of you think that's an easy thing to do of those people who implemented a cache? There's lots of no and there's not a single hand going up for those people at the front But that's because caching is hard and caching is hard for very good reasons Right we can either put this cash in front We can put it behind Now the thing is with with with things like scientific publishing. It's not like news publishing with a newspaper Right, you know the sort of stuff you need to catch The sort of stuff you need to catch is the stuff that's accessed all the time All right It's the stuff that's published that just been published and maybe over the last day has been published But with scientific papers you might be accessing something that's a hundred years old It might be something that was published in the journal 200 years ago that has been OCRed into XML and put in your content store. So essentially Rather than having a nice set of cashable documents where cash hits predominate With scientific publishing you've got the opposite right cash hit cash misses are always going to predominate unless you pre-populate the cash This is actually a tricky set of options to evaluate Every talk with a cash in it has to have this this this quote from Phil Carlton There are only two hard things in computer science cash in validation and naming things I've got a bonus joke for you if anyone's done any messaging There are only two hard things in messaging exactly wants delivery one delivery order exactly wants delivery, haha So, you know this idea of let's just add a cash No one ever said let's just add a cash Right, this is a decision that we don't take lightly when we're building out software So how do we decide what to do? How do we decide which option which option to purchase which bet to place? So I called the subtitle a note on software architecture as code. How do we decide which bets to place? Does anyone recognize this guy? Anyone anyone Bueller Shags Vineman Richard Feynman, absolutely no well-priced winning physicist bongo player safe cracker Richard Feynman has got what I think is my favorite definition of the science method there with me We'll just take a look at his definition In general we look we look for a new law by the following process first we guess it and When he does this you can actually go to the lecture online where he actually describes this it's called on the characteristics of natural law I think When he says we guess it the whole audience collapses in laughter This is the great no prize winning physicist Richard Feynman saying the scientific process starts with a guess But actually he goes on to say then we compute the consequences of the guess to see what would be implied If this law that we guessed is right then we compare the result of the computation to nature with experiment Compare it directly with observation to see if it works And this is the crucial bit if it disagrees with experiment it is wrong in that simple statement He says is the key to science He also goes on to say and I think this is lovely It does not make any difference how beautiful your guess is it does not make any difference How smart you are who made the guess or what his name is if it disagrees with experiment It's simply wrong and that goes for what I'm saying up here as well Don't just believe what I'm saying because I'm standing on stage What I say disagrees with experiments. It's wrong. So that's interesting. Let's unpack this So what he says is first of all we observe nature Then we make a guess We compute the implications of our guess and we compare the results of those implications with nature and then we draw our conclusion So what would that look like if we were trying to use this approach these days with the practices that are described momentarily To make decisions about which bets to place in our software architectures Well, we need to observe some metrics. We need to make our guess So we need to observe the current state of our universe. We need to make a guess make a small change run the experiment Measure results compare that with results of our experiment and then ask ourselves was I right? Was this the correct experiment? Did we place our bet correctly? So what do we need to do this? observable systems Need a brain most of us have gone out. I hope The ability to deploy small changes quickly We need some form of lightweight probes so we can run small experiments. So the next section is on these practices There are more as well So the first is good monitoring observable systems observability has become a thing recently Which is which is good and I think it's become a thing because of the prevalence these days of people building distributed systems But we talk about monitoring Monitoring what does monitoring actually mean? I want to credit down north with this definition of monitoring So Dan talks about monitoring has been composed of five elements the first is instrumentation So this is the fact that our code and hardware describes what it's doing We have the ability inside our code for it to describe its execution and the amount of time it's taking to do things We then need telemetry. All right, we have to get a have a way of getting that data from our system to somewhere else We have a way of gathering that data Then we need some visualization we need to understand What's happening in our systems and using by meaningfully visualizing that data And then alerting right we need to take some action based on what we find And there's a bonus one which is predictive alerting but that's kind of Outside the scope of this tool. So we need to monitor. What do I mean by all this stuff? Well, I've said for a long time if you've got a distributed system the sort of minimum You should be looking for in terms of observability of that system should include end-to-end request latency should include system health Service health it should include monitoring of downstream dependencies of those systems It should include OS metrics and it should include things like a flash tracing So this should should be the sort of minimum set of Metrics that we should be building into systems to make them observable So that we can make decisions about stuff in our case in the scientific publishing world This was a couple years ago now And we had a whole set of tools that we'll be using to make our civs to make our system to Turn it into an observable system to we reason things like history for circuit breakers we use in tenacity Kodahill metrics because we reason drop wizards using things like breakables in the other We had a whole bunch of stuff that we visualized. This is our graphite visualization of this is request latency Yeah, and then this is a dashboard that we put together using history's dashboard of all of our circuit breakers in the system So we could see exactly what's happening with when services are making calls to external services Then we need sort of continuous delivery Which I'm going to define for the purposes of this talk is the ability to safely and sustainably reduce lead time to value These are the three monkeys of continuous delivery down north Sam Newman and jazz humble and because he's not in the photo We've got Dave Farley popping in the corner These are the original authors of or some of the original authors of continuous delivery the book But only jazz and they've managed it through the umpteen years. It took them to write it. So Yeah, the four monkeys of continuous delivery with a mention to Chris Reed is not there It's what do you mean by continuous delivery? Okay, we're on the continuous delivery and DevOps track I'm not gonna hop on about what continuous delivery looks like but very simply we need some way to safely and automatically Push carried from developer. Hey, it works in my machine into some repository somewhere Create an artifact and then progress that through a build pipeline applying progressively More tests to that for that to that artifact Before finally we deploy into production And as we go one way we get more product like the other way clearly we get faster feedback So we've actually called this out on the thought list technology radar a couple of years it while maybe this last year We had pipelines for infrastructure as code in trial And that's a key to the technique of software architecture as code I think is actually having the ability to push not just changes to our the functionality the features in our software Through one of these pipelines of the production But with a special mention to Keith more issues in the room the ability to push changes to our infrastructure code Through automatically through like tested Through pipelines where tests are applied or tests are run and we can apply this stuff automatically in the production Because of course, you know these days if you're deploying software without using something like Ansible without using something like Terraform Well, you know, you may as well go home, right? Okay, so Not everyone is cloud native yet. It's just the way we're going It's the idea of pipelines automatically testing our infrastructure as code or infrastructure code as we push that through in the production It's getting tech is gaining traction And what that allows us to do is actually go through this cycle In a really short period of time So previously in order to make a change to our deployment of topography So we say maybe we might have to wait months for servers to be provisioned We might have to wait months for firewalls to be reconfigured the lead time to things that were hard to change was long Whereas these days when we use techniques like continuous delivery of infrastructure code We can make sweeping changes to our infrastructure in a really short period of time safely and sustainably So the lead time to doing that has massively decreased The other thing we need is some form of probe right we need to be able to understand We can observe our system. We know what the world looks like We need to be able to we need to be able to run some form of testing to understand What the results of our experiments are the changes that we're making And when I talk about performance test to talk about specifically light weight performance testing I'm not talking about the sort of thing you do right at the end of the project Right where you get gatling up and locust and you know insert loadrunner and inserts your very heavy tool here Barely heavy tool here. I'm talking about really simple lightweight tests stuff You can put into your build pipelines that run for a minute or so They'll just give you some form of baseline some idea of how your system is performing and I think when you combine that the ability to make rapid change to your infrastructure code as well as your feature code Functional code and the ability to observe our systems. You get some interesting things What I'm not talking about in terms of performance testing research on Wikipedia This is the sort of word clouds for performance testing that comes up, right? There's tons of types of performance tests. I'm talking about very very simple ones And on the technology radar we had this idea on it as well a couple years ago simple performance training So what sort of thing do I mean? There are tools out there. We can just stick into our build pipelines with very little effort patchy bench That's literally how you run a patchy bench. It's not hard We can use siege siege is another nice tool for doing this sort of stuff Well, there's another another nice tool written in Golang called Vegeta. I actually quite like Vegeta because it allows you it gives you the ability The others tend to just fire off a ton of requests at an endpoint and then tell you at the end of it The the latency in the metrics for the results of the test with Vegeta You can specify a rate at which Requests should be issued so you can say I want to run for a minute with 10 requests per second And that means you can use those results as a tracer bullet if you like to understand the performance characteristics of your system And then I think we need some form of cloud Well, this is enabled certainly by cloud native infrastructure as code and Shout-outs to the guy sitting in the second row Keith obviously just this was last year. I believe he's Published this book infrastructure as code This this idea that we can we can describe our infrastructure in a way that we would describe features in our system through code and Automatically progress changes to those through introduction So tools in this space things like AWS and small things like BOTO And this is actually the tool chain that we use to create this image of a blue green deploy in our system Just interrogating the AWS API is using BOTO Simple stuff so Back to our scientific method We've got the ability to observe nature. We've got good monitoring observable systems a brain But the ability to quickly deploy small changes right small changes to things that were used to be hard to change You should have long lead times to change and lightweight probes So what happens in this story I was telling when we put all this together, which we did You may remember I said at the time this was our requirement all point eight seconds time TT FB and one and a half seconds page load and we started off at 30 seconds 35 seconds Said that man this point we've got a number of options. These are the small bets These are the options that we can we can we can purchase We've got one option, which is to add CPU right come to that in a second We've got another option Which is to cash content in one of two places cash in front of s3 or cash service in front of the service So in order to work out which option to purchase We ran some experiments So we observed nature. We understood what was going on in our system. This is 35 seconds Our hypothesis was that XSL T can actually be quite expensive. Perhaps your CPU bound We ran some performance tests after computing some implications Maybe we increased the number of CPUs that would help And then we were compared the results with nature and after adding more CPUs, this is what we've got We were down to six seconds. I want to say adding more CPUs again Right, this is possible now by changing one line of code Playbooks We've got that in six seconds Which is better? Our second guess, maybe we should move compute to the data so we were running our infrastructure in the Amazon region in in Dublin the West one, but Our data the XML was sitting in the s3 region in the US So we posited that perhaps going across the Atlantic every single time we wanted to Renders some data was maybe not helping us. So perhaps we could move compute to the data And we did that so you know again It's a few more lines of code to change but we brought down our production infrastructure in Europe brought it up again in the US and After we did that we were down to about four seconds. We saved two seconds on the hops across the Atlantic A third guess we made is that transformations are slow and maybe we could optimize those transformations And the nice thing about this is because we'd instrumented all the transformation code Exactly how long these transformations took. This is a pretty good guess Once we optimized the transformations, we were down to about three and a half seconds Pretty good And finally after we bought all those options ran all those experiments implemented all these changes in our code And moved our production infrastructure from Europe to the US Increased the size the number of CPUs or increased the instant sizes of the boxes during the transformations We were down to about three and a half seconds And the final option we elect with and initially we put our cash in between Templating and the extra the transformation service basically Once we did that We got down to about 0.2 seconds If you're on that program look you're on that project, that's a total result 0.2 seconds per page And some of these things are big documents, right? We're talking 50 100 sometimes 200 megabytes obviously we were paging some stuff But still this is pretty good So going back to our sort of graph of these options these bets that we were placing what do we do? We chose to create another service to transform content this is one bet and Then after purchasing some other options adding increasing the number of CPUs moving data moving compute to the data Tuning the transform service, etc. We got to this other point. Do we add a cash or we have further options? We could put a cash in front of S3. That's one bet We can put a cash in front of the content service That's another bet and in both of these cases we've got different trade-offs to make in the one hand We're going to save just the fetch from S3, which is a couple of hundred milliseconds We'll actually varies between about 150 in our case up to about 500. There's actually a secondary industry now in monitoring S3 latency Or we could cash in front of the content service And that's going to save that fetch but it's also going to save our XSLT transform time And that's what give us gave us the massive boost down to 0.2 seconds We didn't just save the fetch We also saved the milliseconds involved in running the transformation over sometimes very large documents So the result of this Content trickles into the store you keep up by listening for the new content and casting wuget on the cash to keep it refreshed New types of content appears content the villagers have never seen before Content the walk-in skeleton is unable to combat Every time the structure of the content changes the cash must be refreshed the cash grows and grows until blah blah blah There's no longer possible to refresh it latency increases. You have died So what happened why did we sort of hit this problem? Let me unpack that basically what happened was We made this guess that we wanted to save the transform time as well The problem of course is as we're actively developing this We're making changes to the API the content API every time we want to make a change to the content API We need to invalidate the whole cache of tens of thousands of objects and rebuild it And eventually it got to the point where that just wasn't doing So we can either cash in front of the content or in front of s3 and actually one of these was an evolutionary dead end in our case but Remember what I'm saying the changes we're making to our infrastructure are incredibly small This is all version control Standing up varnish is a is applying a set of templates essentially to your infrastructure So what did we do we rolled back? And then we made a different set of small changes and applied those changes to put the cash in front of s3 So whilst we didn't save the content transformation time. We did save the time on that The cash causes the content load to drop from 300 milliseconds to 150 milliseconds Everything was brilliant wasn't quite as good as we originally thought but it was still well within the limits of our requirements Villages are happy. I think it's time to close this book Finish the story So I guess I'm going to have some up but talking about this idea of real options and small bets What I mean when I say we've got we can apply different approaches now to building software to designing our software systems I'm making small changes and pushing those through the production is no longer limited just to our functional code just to the code That is delivering features to our users We can now apply the same techniques to things that were really hard to do if we have a set of Practices in place We can place much smaller bets. We can create more options more cheaply. We no longer have the better house So in summary, I guess what I'm saying is to apply this technique. We need some way of observing nature, which we do You have some way of running experiments So performance testing I'm saying doesn't have to be heavyweight. We can use simple tools to gain deep insight into our systems And then we have the ability now to rapidly change all the things not just some of the things So cloud-native infrastructure continuous delivery for infrastructure in summary every three architecture this sort of approach Which is in options placed in smaller bets keeps our options open longer These techniques CD lean product engineering infrastructure as code they reduce the amount of money We need to place on a bet. We don't have to bet the house anymore. We can make small changes which cost much less and Using this sort of lightweight probes. We can make guesses and test our hypothesis hypothesis much more simply I think with a few minutes for questions. That's gonna be me. Thank you very much You


Welcome to All Hands Update. This is your week in Navy history. On October 21, 1797, the frigate USS Constitution launched at Edmund Hart's shipyard in Boston. Constitution is now the oldest commissioned warship in the world. October 22, 1962, President John F. Kennedy ordered a surface blockade of Cuba to keep Soviet weapons out of the country during the Cuban Missile Crisis. President Kennedy was successful in handling a dangerous Soviet Union without war. On October 23, 1944, the Battle of Leyte Golf began when U.S. submarines attacked two elements of the Japanese armada. In the Palawan Passage, USS Darter and USS Dase sank heavy cruisers Maya and Otago. The Battle of Leyte Golf is why they considered to be the largest naval battle of World War II. To learn more about the Navy's history, visit the Naval History and Heritage Command website.


Today, I'm using one of my favorite pans, the Skinny Grill Pan, to make grill shrimp, and then I'm going to serve it with a side of summer corn succotash. It's so simple. Yeah, totally delicious. First, let's grill the shrimp for a few minutes per side, then char that corn on the same skinny grill. We're going to take that off the cob. We're going to saute some green onions in a little olive oil, add that charred corn in the pan, give it a stir with some salt, then add cherry tomatoes and sliced basil to finish. Yum!


Hi, welcome to Nursing School Explained. Today I'm going to review the Littman Classic II stethoscope, which I think is one of the best stethoscopes out there for the price and the quality. So in general, of course, it comes in all kinds of different colors. The tubing length can also be adjusted, so depending if you're tall or short or working with small or big patients, you can have that at a different length. The ear pieces here are always flexible, so they're more comfortable to use, and then they also usually give you a second set of flexible ear pieces or one of the more harder ones, so you can choose whatever ear pieces work best for you. Then it has a single flexible tube, which is just a really good quality, and then as for the bell and diaphragm here, it is reversible. So to use the bell, you would flip it around and then you can see this little opening here rather than it being closed, and so now this would allow me to listen with the bell. And the bell we use for more low-pitched sounds, such as heart murmurs as well as vascular sounds, where the bigger part here is the diaphragm, and the diaphragm typically we use for breast sounds as well as bowel sounds, which are typically more high-pitched. And then just make sure that you flip that part around again so that you're listening to the correct side. When you're using it, you can place it in your ears, always make sure that the ear pieces go towards your nose so that it forms this nice seal, and then gently tap each surface and see where you can hear it. And be very gentle because it's projects, so it can be quite uncomfortable if you tap it too much. So right now I'm on the diaphragm. If I flip it over, I can just check it on the bell of the setoscope here. So just make sure that you check this before you use it, otherwise you might not hear anything and be wondering if the patient has absent breast sounds when they're actually there and you didn't just didn't flip your setoscope. In general, this setoscope probably cost you somewhere between 80 and 90 dollars depending on where you buy it. And the color, of course, different colors can be a little bit more expensive. You can also get it engraved. So that's another option that most setoscope sellers will offer. But in general, this is probably my favorite. I have had this setoscope probably for about 12 or 15 years. It has served me really well. Keep in mind, I also have my name tag on here to make sure that I know which one is mine because let's be honest, a lot of us have the same setoscopes and we don't want to get it mixed up because it is a tool that we use every day. So in general, this is probably the one that I would recommend for the clinical setting depending on how much money you have to spend. And maybe you can just ask for a good present when you start nursing school rather than getting this on graduation because in the two or three or four years that you're spending in school, it will serve you well and it will be well worth the money and it will make your study and do clinical so much easier. Thanks for watching this video on the setoscope review. Also check out my other videos on specifically setoscopes and the different types and then also the clinical playlist where I have a bunch of different skills as well as videos on assessments and so forth. Thanks for watching Nursing School Explained. See you soon.


The hallmarks of higher education and of democracy is the ability to converse with and learn from those with whom we disagree. If this behavior continues, your degrees will be mailed to you. When graduating seniors at Bethune Cookman University booed U.S. Education Secretary Betsy DeVos in 2017, it was mostly a statement against the political danger of the administration she represented and the lack of political nuance of the administration which invited her to campus. We may be fast approaching another situation at an HBCU, this time at Virginia Union University, which will host and battle Virginia Governor Ralph Northam next week in what summer building has his Apology Tour. Set aside for the moment the idea that black people and black institutions shouldn't have to be the gateway for white enlightenment on racial issues. You said that the competition in San Antonio was a dance competition. Yes. Was it you who danced the moonwalk? That's right. Are you still able to moonwalk? Uh, inappropriate circumstances. My wife says inappropriate circumstances. Let's focus on exactly how this will work for out for union or any other HBCU that will venture to be a part of its tour. On one hand, welcoming the governor and asking black communities to forgive the man whom we helped elect because of aligned political beliefs is a good play. Virginia HBCUs are in great position to benefit from a governor who is anxious to prove that he is a leader for the future, despite a racially reprehensible past and a mistake-laden present. If you look at Virginia's history, we're now at the 400 year anniversary. Just 90 miles from here in 1619, the first indentured servant from Africa landed on our shores in old point comfort, what we call now Fort Monroe and Wilde. Also known as slavery. Yes. Democrats in Virginia should be eager to back the governor with a legislative agenda that matches resources with reconciliation. And HBCUs should be eager to welcome them. But on the other hand, our resources and even trade for the negative feedback that could possibly come unions way. Union is not Bethune Cookman and it is in Howard where political misalignment brings out the best in the collective protest identity of their students and alumni. But union is still an HBCU and that means that there is a potential for those students and faculty to reject this appearance, reject Northam's refusal to resign and to reject their institution being used as a pawn for his political reclamation efforts and the goal of keeping Virginia alive as a reliably blue state ahead of the 2020 presidential election. Union may be hoping for the best in Northam's appearance, but they should expect the worst in a state that is very conscious of its racist past and diverse future. Northam's crisis is not a Charlottesville Nazi situation, but it is equally racially intense that could be made worse with a gaffe from governor on an HBCU campus. In the short term, HBCU students and black activists could turn this into exactly what the country expects to see. That could impact enrollment, philanthropy and the stability of the college's leadership. In the long term, it could yield benefits for HBCU students and campuses in the way of programming and scholarship opportunities. The question is if the risk is worth it for union and the HBCU community. The answer? If recent history has been in the indicator, it should be a resounding not today and tomorrow may not be good either.


When do I put it on my channel? When the girls decide. What's your name? Why so serious though? What's your name? It's a single question daddy. My name is Osekuwame. Today, what does Osekuwame mean? Today Osekuwame means a free guy, you know.  I think there's something you've left out, a love of conversation. A love of conversation, yes. But life is a big umbrella. Life is one big conversation. The reason we're born a lot is because of our mutual affection for conversation. Let's start off the conversation with what do you think about conversations? I think conversations are... This might sound fake deep. But they are the pathway to the soul. It's like a path. Conversation is a journey. Conversation is a walk together. And often you would know a lot about somebody when you walk together. Because in conversation, you... If you do have room for empathy, in conversation, you empathize with the person. In empathizing with the person, you walk a little bit in their shoes. In walking a bit in their shoes, you understand them properly or understand them better.  What are some of your favorite conversations today? If you say today, you mean figuratively? Yes. Yes, figuratively. I like to have mental health conversations. I like to have people's passion influences. I send things they love to do and why they love to do them. And things that bring them joy. Yeah, I like to have those conversations because there's so much darkness. If I should put it that way, there's so much darkness. There's so much stress. There's so much tiredness all around.  In that moment, they get to live. They get to have their... It's a dopamine run through their system and they're happy to share. So for example, if you ask me to talk about film or to talk about voice acting or art or telling stories, then I begin to nerd and when I nerd, I feel like it's such a good release. So yeah, I like to have mental health conversations as well because that also helps people unpack and offload certain things that they otherwise may have been keeping to themselves because they think the people that they would talk to may not understand enough. So yeah, those are my favorite conversations today. And of course, having conversations with my partner, which are usually therapeutic in that sense or in this sense as well because we do have conversations about our experiences and how we navigate our experiences. So if you're watching this video right now on this channel, that's what we do. So those are my favorite conversations. I like them a lot. Which conversations would you say have brought you here? Do you remember one or two conversations that have brought you here in this moment to become a filmmaker, a vlogger, etc. Yeah, the conversation with myself will be the first one. Okay, so let's explore that a bit. Yeah, so the conversation with myself asking questions about my situation back then or my person back then. Back then. That's around 2017 when I started to question what else? Is this an existential crisis or something? You just want to find out what is next from here? Where do I go? What do I want to do? What do I love? What's next in the story? How do I want to live? So in having conversations with myself, I came to the conclusion that I may not want to do the thing I was doing at the time, as in working in the sense of nine to five or four in that general sense. Yeah, like that boxed sense of nine to five. I may not necessarily want to be doing that the rest of my life because I do love a lot of freedom, free will, ability to... I think joy comes from being able to decide or choose when and how things should happen to you and how you react to things. So I had that conversation with myself. And thankfully, the other conversation I had was with my partner and now was to figure out how to come out of that space to witness what I am witnessing now. So it was a journey through conversations. Your career, because I followed your career and because conversations are becoming very... Conversations are a very key part of this intervention.   Or don't even see, yes. Exactly. Let's discuss that a bit. And how you go into the studio and do not lose your mind when you are laughing at your own jokes. Okay, so when I was having a conversation with you a while back, there was something you mentioned that you write for someone.  You have a conversation with the person. It's the same trick for radio. You speak to someone depending on your mood, depending on what you want to communicate. So it's about a serious conversation because it has a lot to do with reverence and respect. You may want to speak to somebody that you see in that light. If it's a fun conversation, if it's gossip, if it's jokes, you may want to speak to somebody you see in that light that somebody you're comfortable with. So getting into the studio, you cite yourself to speak to that person in its entirety. Right. What was the most difficult conversation you've ever had? What's the easiest conversation you've ever had? I think... Why am I sounding so philosophical? Come with the philosopher. The most difficult conversations are the conversations of self. Because there is always the...  There are too many difficult ones. I don't think I've had the most difficult one. You can't share one or two. I think one of the most difficult conversations I've had is what I mentioned earlier. Having a conversation with myself and deciding to leave a space which a lot of people wonder how, why? Why would you leave a brand or a workplace or a career or even an industry as attractive as that to say that, well, you just want to be on your own for yourself. So it was a very scary, difficult conversation. You had to come to terms with the fact that, well, when you do jump, that's it.  But shouldn't those be some of the easiest conversations? Because these are conversations about yourself and what makes you happy. Yeah, but yourself and what makes you happy exists in a world. You don't exist in a fantasy. You don't exist in your mind. This is coming from somebody who was on radio and who created realities. Yes, you create realities. But in the end, when you get up and leave, you leave to the world. So if I was having a conversation with myself about things that made me happy and wanting to pursue those things that made me happy, I think that I will still have to do those things in the world. And the world is where the issue comes in because you may know yourself. You may trust yourself to a certain point. But the things that you do will be done outside of your control in a way.  Now you have to build stamina to react. So in the reaction, because you don't know what the world is going to throw at you, that is where the scary part is. The conversation with yourself is not necessarily a difficult conversation. It's the implication of that conversation that scares you. So that was one of the toughest conversations I've had to have with myself. What is the easiest conversation you've ever had? Paradoxically, it's the same conversation. Could you elaborate? So I know what I can do. I know what I love and I know what I wanted to do. I need to know that I want to do this. I'm going to do this. That's easy. I trusted myself enough, or I think I had enough knowledge of self and belief to want to do what I wanted to do and I'm doing. So that was an easy take that I would bet on myself. That, yeah, I can do this. But then I also had to rely on the external being also somebody I was with that supported me fully and made me know that with the parts of the ropes that were supposed to be hung outside the world where I was afraid to jump, she would help monitor those ropes so that we see that I can land. And even if I fall, it will be okay. She'll be there. I'm picking up back on that. I think I know the answer to this next question but I'm going to ask anyway, who's your favorite person to have a conversation with? Who's your favorite conversationalist? My partner. Okay, go on. Yeah, my partner is my favorite conversationalist because she's very analytical. So, and yes, she's like a mirror, you know. She's not judging. She's only reflecting. So, it's easy to have conversations with her and if you do open up, you get back the energy you've given. I said, if you open up this little, she can only do so much. If you open up a lot, she can give you a lot of information back or a lot of perspective that you wouldn't have otherwise. But there's somebody who is having a conversation with you within a context of being your best friend and being your partner. So, that would change the dynamic of the conversation. If you're having that same conversation with your mom or with somebody you met on the street, it's going to be completely different. Yes. Would you say you have grown to almost require conversations with your partner to make sense of things that don't make sense? No, not almost always. Not almost always. I'm actually still very much reliant on self-conversation. A lot. I think the higher percentage is self-conversation, but I'm opening up and trying to have more conversations outside that. And my favorite person to have the external conversations is my partner, but my internal conversations are still the biggest. Who gives the best conversations? The conversation with yourself? The conversation with your partner? Where do you find? What's the difference? There's no best. Okay, maybe that's the one. There's no best. So, what's the difference? There's more of purpose than what it serves. If I want to go with belief and passion and fuel and propelling myself like euphoria, like enough energy to move, I go with the conversation of self in the things I can do and my abilities but when I have to step out, that's when I look into the mirror. It's just philosophy. The mirror is reflecting you. Yes, but the mirror also tells me the things I cannot see when I look down because the mirror would show you a different perspective. Right. But at the end of the day, it's you. So, are we therefore seeing that in the grand scheme of things by having conversations with your partner, having conversations with yourself? Again, yes. It's an external version of yourself. That is why the choice of partner or the person you end up with is the most important thing you can ever have in your journey.  Wow. The conversation I had with myself and the advice I had with my partner. Who has now become very integral to just you having conversations and you looking out into the world and making sense of the world in general? Yeah. So, knowing my shortfalls or, no, accepting that conversations with myself were going to be one-sided, of course, you have to have perspective and, you know, not to have perspective, you have to respect the perspective or to believe that the perspective was valuable enough, you know, to be had. So, of course, I've always been a partner person as well because I always thought that, yes, I do believe in myself and everything, but I've also had a lot of disappointments and, you know, doubts because disappointment brings doubts in your next thing because you thought, oh, so good, I'm going to do it and then you do it and you're like, ah, why didn't people even... So, where did I go wrong? How do I, you know... So, you need somebody. In my mind, I mean, I've come to admit or accept that you need somebody to be able to give you that other self-prespective. Which is yourself, if you think about it. It's yourself, but it's a more objective neutral self that you can rely on. Yourself nonetheless. Yes. What's the place of conversations, would you say? What's the place of conversations? Do you mean physical geography or what? Today. What's the place of conversations? Generally. In my life? In your life, in the society. What do you think is the place of conversations? Do you think... Then do you think we're having enough conversations? I don't think we're having enough conversations, period. I think that conversations are... Again, the journey is a walk and they open us up to a lot of things and I don't think we have enough conversations because everybody's busy trying to survive. Everybody's busy trying to make sense of their own conversation even before they try to share in the first place. So it's not easy for people to share their conversation with you if they feel that they are not ready one or that you would not understand or that they may not get the answers they want from you or that they may not even trust the answers they get from you. So conversation, for example, I started this channel, specifically for conversation. The conversation of preserving our conversations, promoting our conversations, bringing more enlightenment or fostering more conversations around the conversations. It's just a lot of conversations. Like I said tonight, it's the way we live and the way we live is built on conversation. We're just literally having conversations together as we go through the years. It's just conversation. Which conversations do you reckon would lead to more conversations in our society as you've established conversations are how we make sense of the world and how we can make progress? Which conversations must we have in order to have more conversations? I think we should have conversations about the beauty and the safety of conversations. I think we should make people more attracted to the culture of opening up, the culture of speaking up, the culture of even knowing how to speak. So I think the beauty of that is what we should have more conversations about because if I hadn't found somebody who, for example, understood what the things I would tell her and be able to reflect it and give me perspectives that made sense to me, I would be having conversations with myself, doing things by myself and just hopefully relying on a win or a failure. And if the failures were more, then I would be crawling back into my shell even more, having less and less conversations with myself and then you just keep going into the dark, into the shell, just deeper, deeper, deeper. So we should make it an enticing thing. So we should make it a point to have more conversations and to make it a point to be less judgmental when conversations come up because they are the very fabric of our souls, I think. And they are too deep for you to play with or for me to share my conversation with you and you laugh about it. The next thing is the hashtag.  I think it's fine that people don't understand your conversations. I think the point is that they should not be little in any form. Don't belittle the conversation. It's fine if you don't understand it. You're not at this stage where you understand the conversation. And don't take it out there if you didn't understand it. If you couldn't carry the conversation, I don't expect that you take the conversation. It's not your place to carry out the conversation somewhere because first of all, if you don't understand it, you're going to miscommunicate it. And another person is going to think that that's the truth and then the person is going to look at me with your truth of me, not my truth of me. Therefore, how important is it? How important is the person at the end of your conversation? What should go into a person's choice of who is at the end of their conversation? It's a gamble. I mean, you're going in there thinking that the person you're going to be talking to should understand you, should empathize. But then if the person is not even aware of these elements of understanding, of empathy, how do you even know? So it's a gamble. That's why people open up in bits. It has to be over time. You don't go pouring out your deepest darkest secrets unless it's something you just want to throw out to somebody. You don't go pouring it out to a random person. Conversations do happen over time before you can know that there's somebody who can give heavier loads of conversation too. In my experience, as a journalist, I find that the best conversations happen between strangers. I feel like strangers feel safest amongst each other when having conversations because, like you said, they're not worried about being jacked or they know that I don't know their conversation. They might not see you again. You're going to remain strangers, as Malcolm Gladwell says. He talks to me about strangers. What do you think about strangers and what do you think their value is to conversations? Maybe that informs therapy. When you do therapy for the first time, you don't do therapy with family. Or when you do professional therapy, you do professional therapy with a stranger. A person doesn't know you, so they don't judge you. It's not their place to judge you, except to listen and try to help you understand or figure out what you're maybe going through. That's where therapy comes in. That's where we should make it a point to pay more attention or give more energy or support to mental health institutions and mental health people, people who help us make sense of these things. We should pay more attention to them. When is the right time to have conversations? When is the right time to have conversations? There's no right time to have conversations, in my opinion, but some of the conversations will come. You hit a place where you feel like, the words will come out.  So there's no right time. When is the wrong time to have conversations? Ideally, there shouldn't be a wrong time. If the people around you, the person you're working on the path with, there shouldn't be a wrong time. Ideally, there shouldn't be a wrong time. But I also think that we tend to forget that everybody is having their own conversations as well as having conversations of you and other people and even the whole, what do you call it, all of us connected in conversation as a people. Everybody is bouncing off all this energy, all these energies. So where we are in the fix and want to pull out or have a conversation and the person who may be next to us may not be ready and our inability to see that the person is not ready for such a conversation at the time and sometimes because we feel that the person is by us or has been by us on our journey so we feel that they automatically supposed to take on that conversation at the time is when it's the wrong time because if the person doesn't react in the way that you're used to, then you think, ah, I'm alone. I understand that sometimes you cannot control that you really need a conversation at the time. But you're not entitled to forcing the conversation on somebody. So there is a wrong time to have a conversation. That's what I'm saying ideally there shouldn't be but everybody is having their own conversations. So when somebody does take on your conversation it's a privilege that you shouldn't feel entitled to. Should I have a conversation because I have to have a conversation or should I have a conversation when I'm ready to have a conversation? When you're ready. Sometimes in dealing with people especially people you love you feel so helpless when they can't have conversations with you because they don't feel ready and you feel helpless because you can't hear them and so you can't help them. Talk to me about that space and what to do when you feel helpless that's a tricky one. I don't have an answer to it. But can you grapple with the idea of I understand completely what you're saying that sometimes you want to have those conversations and you want to help the person but the person is not ready and it's affecting your dynamic because the person is not ready to share and you feel like you want to walk that journey with them to offload and the person is not ready to share and I have no answer to that because the person has to give you the room as in open the door for that conversation and if the person is not opening the door and you're banging sometimes it might make them go further into the corner of the room.   I don't know until the conversation happens which means I don't know until they're here What if they're female or it doesn't change anything? It doesn't change It's a human conversation Let's not put gender on conversations No I feel like I have to ask and contextualize using gender because of the society we find ourselves in where there are a set of expectations for I don't expect to raise my I want to finish the question What are the expectations for a male Ghanaian child? There are expectations for an African a male African of course because it's a global village now whether they are Ghanaian or not they are going to face the rest of the world so there are a set of expectations and there are a set of they're going to be seen in a certain lens so I wonder which is why I thought to ask about what they are male or female and what kind of conversations are going to or whether gender is going to influence your conversations with your children Gender is not going to influence my conversations with my children I'm going to try as much as possible to have human conversations because human conversations are that of emotions and every human has emotions and every human has a way that they react to emotions The emotions may be there's love, there's sadness there's hate, there's disgust there's all those things but then everybody has their way of reacting to it and every human has their way of reacting to it I don't want my kids to think that men do this because of that and have a justification for behaving in a certain way behaving in a certain way because of the agenda no, if it's kindness ah, yes I'm going to have conversations with my children I think one of the first conversations will be about kindness kindness to self and kindness to the next person because kindness makes wow philosophical, kindness makes the conversation a walk in meadow it's nice and that's how conversations must be heard yes, it's comfortable it's safe there's no judgement kindness is it it's too rosy, we have to get into some dark parts why do you want to get into the dark part because I'm behind the camera and I feel like I want to take advantage of you anyway, what kind of conversations did you have with your mom not that that's a dark side I'm sorry that that joke preceded it's not unfortunately most of the conversations with my mom or my siblings or my family were not the kind of conversations that I'm having now there were more reactionary or reactional conversations to our realities at a time or our living experiences there were more reactional there were more reacting on the things that have happened and for the most part we were not having conversations about how it made us feel and why we may need to unpack or do certain things in a certain way it was more like it happened or we made jokes about how it happened after that happened those were the kind of conversations I remember having so I've not really been as my current partner in my conversations which is one thing I'm learning a lot of what conversations do you have with your dad almost none it's the reason yeah so how much of that story are you able to share yeah so there's not much conversation with my dad just because he was in a space where fathers and sons didn't have to have conversation he's always been in a space where there wasn't a conversation there was a talking to talking to is not the same as having a conversation he never saw you as an equal or sitting on the same platform and having a conversation so I don't think I've ever had conversations with my father no no that's a very serious thing to say that's a very serious thing to admit yeah I've never had so I wonder what kind of man you are because people say that a man is the conversations he's had with his dad and if you've had next to none with your dad what kind of man are you who is Osekuwami today so Osekuwami is based on the impact of the lack of conversation and finding conversations within self and self-knowledge I also know that I do not want to put that on somebody else so I mean either you become like him or you become completely opposite and I think I'm leaning towards the opposite whereby I want to have conversations with my children as a person why are you feeling this way what is it that I can do for you how are we going to solve this how are we going to fix this so that is also why I'm also an advocate or a staunch advocate for breaking that I call it a generational curse because we lack conversations with our parents or our fathers in that sense I'm currently working on a short film which is literally based on conversation between a father and a son which is inspired by my lack of conversation so I'm using the art as a therapy avenue to tell that story and also to advocate and educate people that we do need to break that generational curse of not having conversations with our sons and daughters and our children so now it says father and son thing in the film but like I said before I'd rather have conversations with my children not gender based conversations but just conversations as humans as how they feel so for you your art is beginning to imitate your life I wasn't going to go there but you brought back the issue of children because of your unique situation in that you know the world people tend to can I ask you questions about race okay so you're going to bring children into the world you're going to have an African father and a European mother as an African father you've had to deal with being looked at in the same way in the same parts of the world do you think about these things when you think about your children do you think that you must have conversations with them to prepare them for how the world is going to look at them because of what they look like yes definitely definitely it's something my partner and I talk about a lot actually we have to have conversations with them because like I was saying conversations of self and belief of self and knowledge of self will always have to exist in an external world so they have to be aware of the external world and how the external world views them I don't think by the time they are born age the world by virtue of these campaigns that we're having or these little conversations we're having completely changed like overnight and start seeing people as people and having conversations with people as a person and not because they're from here or they're a guy or they're a woman or they are a they or whatever they choose to identify as it's not going to get there in the next two generations even I don't think so that's the reality I think in my son pessimistic I don't think the world is going to change in the next 10 years or in that sense that by the time they are 15 they don't even have to worry about being from a Ghanian father and a Dutch mother it's a conversation that they're going to have to or a reality they're going to have to deal with so they have to be prepared yet what kind of conversations do you hope your children are going to have what kind of conversations do you hope that your children are going to have cause I don't imagine that you want them to have or deal with the kind of conversations that you dealt with if it's the reality at the time I mean that's why conversations are there if it's still the reality then we're going to go through it together I hope that they don't have to have those conversations the way I do have those conversations of course it will evolve it won't be the same as I did but if it's still the reality then we're going to go through it together we have to have those conversations together they have to understand they still have to offload, unpack perspectives, new perspectives understanding, okay navigation, yes so other conversations you stay clear of and you say why no, I don't think I stay clear of particular conversations because I think all conversations can be had if the two people are there's an underlying empathy and understanding if there's understanding or if there's room for comfort and safety if the room is safe then there's no difficult conversation in the world as difficult as it is if you know that if I bring it out there's no judgments, they're safe and there's understanding, empathy and yeah people knowing that okay, this is your perspective or this is what you feel, but it's not the truth but it's okay that it's what it is then yeah every conversation can be had here's a final question on conversations for you do you know what your final conversation is going to be if I did, I wouldn't be here that's why I'm leaving the conversation nobody knows their final conversation do you think about it? I don't think about my final conversation why don't you think about your final conversation because between this conversation and my final conversation there's so many conversations and so I'm looking forward to those conversations rather than thinking of what the end is yeah thank you for this conversation we have another conversation I can't believe we actually had a conversation about conversations the philosophy of conversations that's nice I always knew the title of this video yeah


This paper proposes a new approach for bearing fault diagnosis using multi-scale permutation entropy, MPE, which is more effective than existing methods such as single-scale permutation entropy, PE, and multi-scale entropy, MSE. The MPE algorithm extracts features from vibrations caused by bearing faults, and then uses support vector machines, SVM, to classify these features into different categories corresponding to various types of bearing faults. This method outperformed other approaches in terms of accuracy and robustness. This article was authored by Chen Jian-Ding, Chen Qi-Wang, Qi Yuan-Wu, and others.