So the next session we have in this track is my gym materials speaking about 10 design tips for micro services developers. What do you, Jim? There we go. I assume you can hear me? Yes, we can. And then I'll share my window. I assume you can see my screen, and I can see that I'm sharing my screen. So I think we're good to go. All right. Hey, good morning. All right. Let's get this thing going, and we'll do our best to keep this thing on track for those watching at home. Hey, so good morning, good afternoon, good evening. My name is Jim Tyrell. I'm a senior principal solutions architect here at Red Hat. I've been here almost 15 years. Been in our public sector sales practice that entire time. I'm also 25 years a Java coder. And this talk is 10 design tips for micro services developers. This isn't going to speak on any particular technology per se, but it's going to give you some high level things to think about as you're creating micro services. And actually, as you watch this talk, you probably will see that these things apply to other software development you are doing. At the end of this, I will invite you to a workshop I'm doing at the end of the month, which would be kind of a follow-on to this thing where I actually will get into some code, some thinking around how to do domain driven development in the context of micro services, a little bit of emphasis on Quarkus and Java. So just something outside of this presentation. Stream, if you will, that'll be an invite at the end of this. So development and design, I believe, sits at the intersection of science, art, methods, and patterns. I am the founder of Design for Developers, just a website. If you want to go check it out. It's where some of my writings are for this. On social media, I'm known as the design at tick. If you didn't know it, here at Red Hat, we published a library we call Open Practice Library. This brings together a lot of design thinking tools. These are really great ideation tools with my master's degree at the Institute of Design in Chicago. I learned about many of these, practiced with a lot of them. But the end of the day, as a software developer, a lot of them just don't exactly speak to me when I'm writing code, when I'm trying to deliver systems. And because of that design thinking that I have, let me put this out there in the ecosystem. And one of the things that I absolutely love about software development is the fact that it brings together science, art, patterns, and methods. Every day, I'm excited to get up to Sling Code because of that intersection. And with my master's degree, I noticed that, especially the design program that I went to in Chicago, that design is about art, but it's also most certainly about patterns, methods, and science, right? And if you didn't realize that design is a science, it most certainly is. That is some of what I talked to at my website, designfordevelopers.io. Since I'm the son of a math teacher, you can't have an equation like that without the transit of property. And that means that design is development, and development is design. These two things are inescapably intertwined almost like gravity. You as a software developer are making design decisions every day, yet sadly, you probably don't have a lot of design training in your background. And that's what this session is a little bit about. That's a little bit about what the Open Practice Library is certainly about, and then of course, the designfordevelopers.io website. And this is a quote, something that I've put out there for a long time, right? Unless you are impossibly lucky, and sometimes I say unlucky, all software at some point will be consumed by humans for sure during its development, but also for the years after it was delivered as will be maintained, it may continue to be used by humans. In other words, if you're familiar with the Mythical Man Month, all the cost of software is in its maintenance. If you're Britain software for any length of time, you as a developer, if you come back to something a year from now, I've seen jokes on Facebook and other memes that who wrote this thing and when you figure out it was you, it's a challenging endeavor. Certainly it's one of the more complicated things we will do as humans. One of the things that I've spoken about and think about is the user interface notion of software, right? And I think there's at least three, and let's talk in prior, people have talked about test cases, documentation, but I think for us as software writers, we're responsible for any one of these three user interfaces, right? And obviously it's a GUI graphical user interface. That is most certainly gonna be there. Your API is code, right? The methods, functions, variables, et cetera, that you deliver are most certainly gonna impact the user interface for those end users. And then where this talk kind of gets into and thinking about a little bit is the API is a service as a user interface, right? And it was we're throwing around JSON objects at URLs. Most certainly those are user interfaces to someone at some point. Even if the machines go off and do that, have you lifting for a long time? More than likely us as humans are going to have to deal with that writing interaction with that at some point and thinking about the human along the way will pay huge dividends. One of the things that I brought up in this talk is the five E's. This comes from a Dublin talk, a great firm out of the Chicago area in my design community with my master's program. It came about what predated TED talks in 1997. I'm assuming you've probably never heard of this. You'll notice I crossed out the word great. I crossed out the word curated in this. Organically every experience you have, no matter what it is, including this talk will organically actually have a state of enter, engaging and exiting. In other words, you will most certainly enter the experience you will work within it and then you will leave it. And I would argue that that's just an experience. So that's just organic and you're not managing the emotions or any state of that user along the way. The five E's though adds one thing at the beginning and one thing at the end that I think we as software developers don't do a great job of. So the first one in this, and I would argue that every great curated experience has these five steps and you are consciously thinking about them as you're creating your microservices. You wanna think about how you're gonna bring in people into your universe or that's a read me on a GitHub page advertising because you're looking to sell these services out in the wild, maybe webinars or lunch and learns internally, but somehow you need to make people aware of what it is that you're delivering and give them confidence that you can help solve the problems that your solution will provide for them. You also need to think a little bit about how they're going to enter this experience. What is that demarcation or what is that start line if you will for when they get into that experience? You need to think about, as I talked about the engagement, right? What are they doing in there? What are you doing to remove friction, toil and invisible work, which is a term I like to put out there a lot around design of the context of software. Of course, those users are going to exit it. And most importantly, and probably the most important thing to think about to really create a great experience is how do you extend that experience for that end user? We're gonna go through a few things to think about as we work our way through this talk. If you'll notice at the bottom middle of this page, there's entice is in there. So we are still at the enticement step of this talk. I'm still trying to bring you into this narrative, if you will. And we're looking to bring you along on this journey, right? And the other thing to think about is that all journeys should have consistency. So certainly at the macro sense, you wanna think about these five steps, but you probably also wanna think a little bit about these at the micro sense, right? So at the macro sense, let's say you wanna send emails to the world, right?  But along the way, when people are looking to deal with an API, what are you doing to bring them into a specific use case within that? So that's what I'm speaking to when I ask you to think about all experiences having consistency. You know, like all good designers, all good software people, right? We should Google around and find what other things exist in the past around this. Again, another thing from 1997 from Nelson Norman Group. These are just luminaries in the design field. Don Norman is very famous, couple books that are off on my bookshelf here to the left. But this is a great list, but it really spoke to lowercase D designers of colors, fonts, layouts and things like that. I mean, it definitely speaks a little bit to a software developer, but it just didn't quite resonate with me. So, you know, like everything when there isn't a good standard in software, you know what we should do is go create another standard just to proliferate those across the ecosystem. So I came up with this list. It started with just a few S's and I just decided to do the whole thing and asked we're gonna drill into each of these here in a second. And I hope and think that you will have a good list of things to check off as you're thinking about your software. So with that, let's cross that start line. Let's enter this talk. So let's get into 10 design tips from microservices developers. So the first one is avoiding Dr. Bre, right? And as you're bringing people into your experience, you really wanna think about what you're gonna do to help them with getting rid of or creating anti-quick starts, right? That's what's out in the world. The wall of intertwined texts, the challenge of missing steps. And then the last one I call back and forth, right? So anti-quick starts. I'm amazed that today in 2021, in August, I still get to quick start pages that literally have hundreds of steps for me to do. Tens of pages to navigate. And I have no idea how I could possibly do all those things perfectly and accurately along the way to get started with something. You know, I think that just speaks for itself. The wall of intertwined text, intertwined text is probably one of my biggest pet peeves in this documentation game, right? We have Windows, Linux, and Mac OSs are the tools of choice of people that write software. And heavily our instructions might start out great with telling us what to do exactly for these three operating systems. When you get to step two, they might just document the Linux and Windows instructions and hope you'll figure out what you should do for your Mac. And then you get to your third step and you're left wondering, well, what do I do on Windows or Linux? And the worst thing about these steps is that these things are never labeled step one, two, and three. There's usually just a huge long checklist of things to do. The different OSs are interchanged with each of these instructions and more than likely you're gonna fail because you're gonna miss the fact that you needed to do this one nuance thing along the way. Another one, right? The internet meme of question marks and profit in step four, right? Missing steps along the way. Please don't leave your users with question marks about what gaps they need to fill in to run your project or your service, right? You should be able to give people the ability to just quickly get started with your service. And we'll get to those with the nine items of the assessment here in just a little bit. And this is the one where probably you live in day in and day out as you're running the most certainly deploying software, right? And this is what I've called the back and forth. This idea that you're gonna have certain pages of documentation that you're gonna have open.  You're gonna open up a stack overflow page. And then you probably have some notes written down from the last time you did this. You're gonna bring all four of these open on your monitor or across your desktop. Try to put those all together to deliver an experience for yourself to get something installed. My friendly ask is that for these four things to just think about your end users and think about your future self as you have to come back to this maybe in a year to figure out what it takes to deliver the software. So let's get to those nine purpose defining statements or what I call the assessment at this point. So security over slowness, right? And notice if this is kind of enticing your users and as you're bringing people into your experience you really wanna think about what you're doing around security, right? Are you using TLS, HTTPS? Are and what are the rules around password management? What are you doing around tokens and keys and how they should be stored or not stored? Do they, are they one time use and then they're hidden from use for you forever or can I go recover them? Do they time out if I don't use them for 30 days or five hours and are they gone forever if I don't ever use them? Do they time out if I don't use them for a couple of weeks or a couple of months, right? What are the rules around data at rest and or in flight? You know, in the government space that I hang out in we talk about FIPS encryption 140-2 soon to be 140-3. And these are just some of the things you should think about in the context of security over slowness and you don't wanna have security by obscurity. One of the things that I had that happened to me just a few months ago that I was playing with the service, downloaded a software key, tried to use it a month or two later, didn't get any success with that key. It was kind of like, hey, what's going on here? Thought to myself, well, let's go get a new one, got a new software key, went and used it and the code worked without any changes other than that software key. It would have been great if the documentation when I downloaded that key, it told me, hey, dummy, that thing's gonna expire in just a few hours or a few days. Whatever the rule is. I actually have no idea what the rule is. I just was caught up in it and that creates some friction for me as an end user. Scaling over shattering, right? We're living in this web-enabled world with mobile devices where it's not unheard of to have hundreds of thousands of users hit your app if something happens that brings a lot of people to you. At the same time, you also wanna think about disaster recovery and high availability, right? What are you thinking about your services to keep them up and running under the face of increasing pressure? What are you doing around things like K-native, serverless functions as a service, OpenShift, Kubernetes, containers, and other building blocks to give you easy ability to scale up and scale out horizontally the software that you're running in your organization. What are you doing around the saga pattern and idempotency so that services can just keep being invoked and tell something happens, letting your user be able to just keep on firing request at your services. And most importantly, what are you doing to bend but not break, right? It's one thing to have a slow experience. It's a whole nother experience to get the white screen of death which is always a bad thing for your end users. We'll talk about that here in just a few seconds. Support over stumbling, right? Going back to that Dr. Breed question of earlier, what are you doing to provide your users a getting started experience? How can they self-start with that experience? How can they get started or do you require them to give you a credit card or way more than a password or way more than an email address and a password, right? What can give them to be successful as quickly as possible? I'll talk a little bit about documentation getting started experiences here in a bit but what are you doing to get them to be successful as quickly as possible? What are you doing to make them superheros as fast as possible? And what can you do to facilitate that for them and your end users? So here's an example, right? I'll pick on the guys at Twillow since I gave them a little bit of a shout out earlier sort of. So I wanted to send as part of a proof of concepts a few months ago, a text message, right? And a text message on your phone, pretty simple, right? Your phone has your phone number on it, you then pick your friend that you're sending your text message to and then you send them the text message, right? Download this code from their getting started examples, went in there, signed up for a phone number, gave him my phone number, activated my phone number as a message receiver of text messages from this account, ran that code and once you know it, that my phone number was not valid in the context of this example. And you would think, at least I would think that matching the real world going to that Nelson Norman list of earlier would be an important thing, right? And just thinking about how I use my phone, right? A phone has the phone number it is and the message and the two phone number are together. But you go look at the docs for this and it's actually not that case, right? The actual, the two phone numbers first, the farming phone numbers in the middle, the string is there at the end. These are the kind of things that drive users crazy, a little bit of that friction, toil and invisible work. Sanitization over string, right? I think, well, this is an example out of the Swagger ducks in the spring pet store. I'm not exactly convinced that the update in existing pet semantics on the left-hand side match the semantics on the right-hand side. I would actually argue that that put example of updating a pet should probably have the pet ID on the URL. The other semantics as well as other ones in there are updating a pet or deleting a pet. And I just think that having that URL have that pet ID in there makes me feel a lot better about the way this looks and feels from an end user perspective. I also think it gets you thinking at least a little bit about the difference of creating a pet on the left-hand side and updating a pet in the right and changing the nomenclature of what it is that you're passing around and not making any mistakes you as an end user human. Of course, this gets to my next big headache and this is what is ID in this example, right? Is it a capital IND, a capital I, a lowercase D? If you look at the documentation here, right? The curly brackets have an uppercase I, a lowercase D and then the words they find pet by ID all capsed there in the blue get.  So which ID should it be, right? Should it be lowercase, should it be uppercase? I would also say these three IDs here should probably be fully qualified. How many times have I spent some time debugging something just because you crossed up the same word in the same way across different classes or whatnot? I would argue that this should be pet ID, category ID and tag ID, keeping the world a little bit easier for your future self when you're trying to debug or just figure out what's going on as you're decoding these things. I would also argue and add that I think ID should always be capital I, capital D, full stop. That's it, done, end of story. If you disagree, put that in the chat and feel free to argue with me when this talk is over. So since over some and right, this is this idea that as users engage with your software that they have the time and the prompts to do what our next best steps are and they're not requiring them to have huge amounts of training or knowledge. And one of the questions or examples I always put out there are your end users, airplane pilots or nuclear power plant operators or are they the trainers of those who is actually you as a software developer, you actually could train the pilots or the nuclear power plant operators of your offering if that is indeed what you were shipping. At the end of the day, I think most of us are just Homer Simpson, right? We are trying to deliver software or use the software once a quarter, once every six months, maybe once a year. There are very few things that we will do that require the type of training that a nuclear power plant operator or airplane pilot undergo for an event that probably will never happen to them. And of course that begets a question, what happens when a nuclear power plant operator is Homer Simpson and thankfully that's a question for another day. So we'll leave that one alone. Safety over setback, right? As your users are engaging with this, what are you doing to allow them to undo things? What are you doing around eventual consistency, idempotency again, thread safety? What are you doing to allow them to be safe in the use of your offering? You give them a sandbox, do you allow them to play? Do you allow them with immutable architecture or infrastructure to just throw away everything that they did with a database instead of touching anything? What kind of rules do you have around how people touch development systems versus production systems and how do you keep all that safe? What are you doing around test cases around all those things? All right, just some of the things that you need to think about in the context of this.  Think about the fact that your end users do not have the terminal access that you had while you were developing that microservice. What are you giving them when they interact with your microservice in a browser or a postman or some other tool to let them know that something did not go correctly? What are you doing to validate that input? What are you doing to let them know that something did validate or words are crossed up? And the last point here is a white screen of death is never okay. You should never not return at least something to the end user to at least let them know that something is up and running and available at that endpoint. Stewardship over suffering for that long-term user, somebody who has invested some time to play with you. What are you doing to make them great at what they do? What are you doing to document the middle, the thick middle use case of the bell curve of what they're trying to do? Like a lot of examples, a lot of projects out there have some hello world simple getting started examples. They might also have every command line switch documented but where those two kind of meet in the middle is not really documented, might not really be tested all that much and it just drives end users nuts and crazy. My friendly ask would be what are you doing around observing your users and removing friction toilet visible work for them?  Status over surmising, right? At the end, you wanna make sure that as you're exiting the user that they have a clear ending.  You might give them some stats about what it is that they accomplished. You definitely wanna do some metrics gathering. You definitely wanna grab some logging. You definitely wanna gather information for the next step which is statistics and study over speculation, right? As your end user is finishing up this, what can you email them to let them know about what it is they accomplished? How are they comparing to others in your use cases and your user bodies? What are you doing to follow up with them about what it is that they accomplished? What can you do to make their experience easier and lighter weight? And the last thing I'll talk about there is user interviews and surveys. And this is a vendor, a nameless vendor from a friend of mine a few months ago and I was snowboarding with them and they were using a new cloud service in the NoSQL database space. And they were in a beta program and the tooling told the product manager that, hey, this person was having some problems. He got an email from them and didn't even realize that this could should happen. The guy asked, hey, can we speak to you about your challenges or our efforts? And he said, sure. They came together, had a meeting. The product manager brought the program manager and a developer. They met on a Tuesday. My friend showed them and screen sharing some of the headaches and problems he was having along the way. Later on that week, that vendor had fixed those problems. When was the last time you were able to both watch and talk to a user of your software and be able to fix that bug challenge or friction point in near real time? Very, very powerful. So let's just, in conclusion, let's just kind of wrap through this, right? You wanna avoid doc debris. You wanna make sure that you have security over obscurity. It's security over slowness. You wanna make sure that you can stand up to web scale type of traffic and workloads. You wanna make sure that your net new user doesn't have to stumble all over the place. They can figure out what's going on organically or very simply. You definitely wanna think about how you're gonna standardize over these things, right? You wanna standardize on ID and words and nouns and all the words that go around your system. So there's some consistency across the entire ecosystem of your services. For your long-term users, you definitely want to give them the idea that they can sense the next best action. They don't need to summon from the depths of knowledge. What is they're doing or trying to deal with? Safety over setback. You really wanna think about how your end users can use your product safely and not get themselves into any trouble. What are you gonna do for your long-term users to let them know and discover what it is they could do and give them some deeper examples and documentation or use cases or test cases they can peruse to learn more about. Over time, you definitely wanna gather what information is available for your users. You don't wanna just guess and assume that people are doing things a certain way.  And as time goes on, you definitely wanna gather real-world feedback from your end users and see what's going on there. So at the end, these 10 design tips for microservices developers give you a framework to help you remove friction toil and invisible work. You will make your users smarter when you take away their friction toil invisible work. That's definitely a talk for another time. And please come meet me out at designfordevelopers.io. And I'll have a workshop that I'm gonna call 10 more design tips for microservices developers with some Java and Quarkus thrown in. That's at the end of the month. You can register that at a link I'll put in the chat here in a second. And please feel free to reach out to me and all those fun little links up there. Facebook, Twitter, LinkedIn, Instagram. Feel free to set up a meeting to meet with me if you'd like and or see this workshop in a month. And I will put a link to these slides in the chat also. And with that, we're almost sort of back on time. I gave you guys back a minute or two. And if you all have any questions, feel free to put that in the chat or the Q&A. Thank you very much.


There is no formula for investment success. I wish it would be there. But there is a formula for economic success and economic growth. A country's economic growth is the driver of everything else, is the driver of the stock market, is the driver for earnings, growth in revenues. So if we can know which countries will do best in their economies, we can position our portfolios to take advantage of those trends. Lower our risks increase our returns. What I have found is a formula that explains with 84% of correlation what will happen in the economy of a certain country in the next 10 years. Now I haven't invented it, I just have found it on Ray Dalio's economic principle webpage. In his 305 page report that he shares freely with the rest of the world. With the hope that politicians, monetary politicians take it and stop making decisions based on ideology and start using analytics. What he and his 1,500 researchers did. Good luck with that changing the politicians mind. I don't think he will manage. But what we can take from it is investment, strategic data. And that's very, very important. And when it's for free, it's amazing. So thank you Ray Dalio. Let's dig into what he has found. What are the most important factors affecting economies? And what will be the economies that will be the most successful in the next 10 years? So according to Ray Dalio and logically the main driver for an economy is productivity. And then that productivity, economic output can be pushed higher with in-depthness. You have one long-term cycle that takes 75 years to develop and you have lots of small credit cycles every 5, 7, 10 years. We are now also in a credit cycle. So expect it to contract somewhere in the future. Nobody thinks about it except Ray Dalio. So think about it. There will be a recession at a point in time. When? I don't know. But there will be. So what did Ray Dalio do? He tested the factors impacting economic growth based on productivity and based on in-depthness. And he found that productivity affects economic growth with 65% and in-depthness with 45%. The factors that affect productivity are the following. The value of the labor, education, labor productivity, working hard, investments, then the culture, self-sufficiency, savoring life versus achieving innovation, commercialism, bureaucracy, corruption, rule of law. Those are the most important factors in increasing productivity. As for in-depthness, the most important factors are depth and depth service levels, depth flows and monetary policies. And then what Ray Dalio did attached a weight to each factor, looked at the correlations and came out with a model to estimate future 10-year growth rates. So this data is available for free and that's the crazy part. So we can really get the free lunch thanks to Ray Dalio. If you see Ray Dalio off, he has a charity. Please pay some money into that charity for him. He doesn't need your money but it's just a sign of thank you. I will certainly look it up and perhaps share it here online if there is something like that. Back to the correlation, here is what his model does. He analyzed how those factors impact economic growth on 20 countries and checked it 65 years in the past and looked at how that factors impact future 10-year economic growth, correlation 84%. So if you want a good correlation, a good investment trend, then you have to follow this. And to make things even easier for us, Ray Dalio took all the world data, put them into his model and showed us which countries will do the best. So we don't even have to work hard. We have all the data already presented and laid out. Thank you Ray again. Here are the data. India will grow the fastest. China, Singapore, Mexico, Thailand, Argentina, Korea, Brazil, then the first developed country on the list is United States, which will still show the fastest growth of all the developed countries followed by the UK. If we go down to Europe, Germany, France, Spain, Japan the worst, then Italy and Greece even worse. So before this chart, you will do well in the next 10 years with your portfolio. So just for curiosity, let's look at the individual factors and how they affect what's going on. The growth in the working age population per country, highest in Mexico, India, Brazil, more working age population, more money, more productivity. Worse in Russia, Japan, Germany, Greece, Italy and so. US still the best of developed countries. What you pay versus what you get, the value of working hours, India the highest, China still the highest, culture the best one hardworking is in Singapore. The worst culture to work, Italy, Greece. And the most expensive workers in relation to output are France, Germany, Italy and so on. Education level the worst education is in India but still when compared to what what you get from an educated worker is extremely cheap and that's an advantage India has, China still has it, Thailand, Russia and so on and so on. The most expensive workers is France, Italy, Germany, Europe and so on. Why did I resign when I was paid so well for doing nothing? Hmm interesting. Nevertheless let's go on in-depthness, countries that are lowly in-depth in relation to their potential. India can really invest in their infrastructure. Singapore, Mexico still can take a lot of that for the future. US is still there, still strong so very good. Worst countries, Japan, Greece, Italy, La-La-La always the same Spain and so on. Sum it up back to the figure we already saw the strongest India you have the correct numbers. China, Singapore, US the strongest of the developed countries and then down to Europe with the worst expected real growth rates in the future. So this data is essential when positioning your portfolio in the future. How to approach that? Look at valuations is not just jumping into India and I'll make now a video on about how to invest in India. It's not easy. You see the growth but it's not that easy to invest. It's not just putting my money in Indian companies. You will see in the next video why you need to know how to invest in India. Read the economic principles of Ray Dalio. It's a 305 page report. We'll still discuss a lot of things of the report so please subscribe so that we can interact, comment, share our knowledge. But that report is essential to see how the economic machine works, to see how the economy, global economy works, how it is fit, what are the risks and what are the potential rewards. Because that is what the fundamentals, the productivity is what will mostly influence your return in the long term. So really focus on that. Thank you for watching. Leave your comments. Click like if you like the content. Don't forget to subscribe and I'll see you in the next video.


when he came to me and said you know I kept that sign I said you kept that sign and he goes yes and I go well you know it had been kind of nice to know before I went and met with all these teams because I said that's kind of an important fact that it was a thing goes yeah I get it and so it was once he gave me the direction to pursue with how and cash to move to negotiating the final elements of this it was clear to me that he wanted to know everything but in the end he he really felt that you know this is where the the history of the Cole family was and his father and son relationship and frankly where his dream originated from


Left click to select cell A2, hold down the left mouse key and drag to the right to select that range of cells. Then while it's selected, right click to bring up a couple of menus. The upper menu is the formatting menu. We're going to use the field color, click on that down arrow, and select blue to start. Then I want to select the font color, the A, click the down area, and select white. Then I want to toggle on or toggle off, bold, and then we can click the center to center the label, the titles in the columns.


All right, guys, before we start the video, I have a quick notification for you. I just teamed up with Grassland Nutrition. I was hesitant to collaborate with a supplement company. However, Grassland Nutrition is not your typical supplement company at all. Grassland Nutrition is a family company that produces 100% certified organic grass-fed liver without the taste. All their products are sourced from the Australian Channel country, which covers a land space almost twice the size of Texas, where the cattle naturally grazes on over 250 native species of plants and watered by sustainable natural rainfall. Their mission is to provide you 100% certified organic premium source of organic organs for you. They truly live up to their name, Grassland Nutrition, because what you're getting is nutrition from pasture-raised cattle. This is real food and not a simple supplement. And the two products that I'm using right now is the grass-fed liver and the kelp extract. You have it in capsule form and you have it in regular powder as well. The regular powder has no added kelp. It is just organically sourced Australian grass-fed liver, which has been freeze-dried. So now I'm not here to tell you that supplements are better than real food. That will never be the case. The best case scenario for you is still to eat raw liver. But I do understand that people have issues sourcing properly grass-fed liver first and foremost and many are grossed out by the taste and the consistency. Grassland nutrition spares you that trouble. It is convenient, it is easy and it is just freeze-dried liver. There are no additives. Technically, this is not even a supplement. This is food. So if you look into the supplement facts here, you will see that only three grams of the grass-fed freeze-dried liver delivers you 111 percent of vitamin A. True vitamin A, not beta-carotene. Vitamin B12 is at 309 percent. When you're not a vegan, you don't have to worry. On top of that, it comes with folate, niacin, iron and vitamin B2. So if this is something that you're interested in, the link is in the description box.  And now to the video. All right, guys, welcome back to the channel. If you're new, my name is Bobby. Guys, this video is for all the poor schmucks that were cheering on Kai Green for going vegan. Truth be told, I don't think that anybody really believed that Kai Green will be going vegan. However, Kai Green capitalized on the Game Changers wave. Once the Game Changers came out, Kai Green decided to publish his vegan ebook, which he ironiously titled Stranded on the Lonely Island, Plant Based. Anyways, no surprise. Couple of weeks later after the boom was gone, Kai Green publishes this post on Instagram. 40% off free beef for life. So much for Plant Based, dear Kai. And now he proceeds. And today he published his new ebook, which is titled Keto Diet. In the comment section, you can see the true bodybuilding bros. Everybody is happy. They say nice, nice man, post biceps emojis and whatnot. But other people say, dude, you got exposed hard as f***. Here you see people say vegan face came and went.  And I believe this comment sums it up beautifully. Just another ebook to sell to foreigners. It's quite hysterical. Just couple of weeks ago, Kai was fronting, eating beans and bean burritos and whatnot, just to make the sale. What's up guys? The boy here, Kai Green, aka Mr. Getting It Done. I'm sorry. I'm getting it done, vegan bro. So we're at the office, we're eating up. And this is like my day four. No. Listen, the days kind of bleed into each other. So it's kind of difficult for me to kind of keep track. But I'm still continuing my vegan challenge here. This is really cool. Let me tell you what happened. Really cool. I just recently have was really cool is the vegan money. That's really cool. Everybody's cashing in office spaces here and Edward gaunt, Kai Green, no worries. Everywhere I go, animal activists, you know, vegan options that yeah, buddy, loving it would have never even knew existed. Sure. What happened? I was looking at my refrigerator, but I don't look into it vegan patties. Oh, cool. What it is, what's going on? Yeah, baby. It's actually really good. I got here some I got some quinoa, got a little bit of good fats here, some mushrooms and some kale. Wow. Some cashews if you didn't see all indigestible for humans and highly toxic. That is absolutely great, Kai. And of course, Kai couldn't maintain it.  Thank you very much, Mr. Green. Anyways, guys, get ready to see more and more of this. The vegan movement is nothing but a money grab. So-called animal activist will sell you compassion and all of those big corporations will sell you healthier food. And the fitness personalities will sell you the key to gains. It is all a scam. It is all lie. It is all as Arnold said, that's marketing. Exactly. All right, guys, but this video, if you liked it, leave it a thumbs up. If you haven't subscribed already, please do so. And guys, if you want to support the channel, all the links are in the description box below with Amazon links for you. You can head over there by whatever you might want to buy. And it doesn't cost you anything extra. We get a small share that is a fantastic way to support Bobby's perspective. If you want grass-fed beef delivered to your doorstep, butcher boxes for you. And we have CBD links as well. On top of that, guys, consider supporting Bobby's perspective through subscribe star or Patreon. We have a VIP community there where we have Skype group calls every single week where we can discuss any topic, no matter if it is health, lifestyle or nutrition related. On top of that, by joining you straight away receive your comprehensive nutrition guide. It is an ebook that teaches you the basics of nutrition, but goes beyond as well and is catering to your personal goals, no matter if you're keto, primal, paleo or even raw. Alright, but this is it for today. Thank you very much for your support, guys. And as always, much love and peace.


Okay, so hi everyone, I am Himanshli, I am working as a tech lead DB engineering at Inmobi. So today I am, as already he told, I am going to talk about that PostgreSQL as NoSQL. So PostgreSQL that is a powerful open source RDBMS, right, and we are using in our company for many critical application there as a master database for that. And there is other one that is sitting there that is NoSQL. So if you see both are like just conflicting terms in there. So actually this NoSQL term that always confuses me, because if you see PostgreSQL if its history that it was also not using SQL, there was something called QUEL that it was using. But we cannot tell PostgreSQL as NoSQL database, right, because what is the modern NoSQL DBs that is being different from existing RDBMS, right? So what I think that is main thing that there is a freedom of your data model, how you are defining that, right? So is schema less, that is the main thing that is NoSQL DBs are providing. So actually my talk is about PostgreSQL as schema less database, how we can use it. So what I am going to talk today that is what was the requirement of schema less database in our scenario and what data type and volume that we had to handle and how we can use our existing setup that is already there instead of migrating to a new NoSQL DB. And what performance this guy was providing to us when we were adopting this option there. So first of all what is schema less data, right? So normally if you see schema less doesn't mean something that is not structured, right? When we are talking about a schema database there is thing that we have already a predefined data model. You define your schemas how you are going to store your data, but in this case you get that freedom there, right? So but still it is like here you have instead of how in schema DBs you are, your data is row based, right? Each rows that you have already defined on that basis it is being stored there. But here you have a document based store, right? Where you have a key value pair and that can be a hierarchy of arrays there, right? And the thing is application needs to be aware about what kind of data you are going to store there. So and it even if it is like it can be dynamic whenever it is being stored as document because one document whatever data is inside that can be completely different with for example if you have five keys for a first document in second it can be like 25 keys, right? But yes your application that should be able to handle that thing. So it should be whatever how you are writing your application it should be about it should be aware about what keys you are going to store in your document, right? So yes, so back to what the requirement that came to us in our team. So there is already there was an existing application that that was running on PostgreSQL. Now they came with some requirement where they introduced one new entity that is called margin, okay? Now for that they were the data was not what we are generating the data was going to come from the client. And here they were not sure about that for now they were knowing that there can be maximum like a 15 filled that they were known filled, right? And even this data was not standard for all merchants. For some merchants there can be only five that data can come for some merchants it can go to tail. So in that range it was varying and this will only be known when the data is coming from that client side, right? So for that now they came that, okay? So this is the requirement. And in existing a schema in existing DB how you are going to use that? So there was some solution came, right? Just define a schema for that maybe just define a table for that in which maximum keep 15 columns there, right? And after that if tomorrow if something new comes we will go and add one more column. So it does not look that clean, right? Tomorrow maybe if something again you for older merchant you may have to go and again update the data for that new column that you are adding. So whenever it was something hacky that we could have done in there. But we thought, okay, it's not that clean way, right? So and also the data was not that small that we were expecting. So it was like for start to start with they were telling that data can be like a one million per hour. So this like I already told the problem with the existing thing that it was schema was predefined and so many null value chances were there. Whenever you are adding any new column, so you will have to do a schema change. And that will be costly if your data size is used there. And in case if you have to update the existing values. So we were thinking, so should we this report thing should we change it to a separate module and should we think about some nos equal debits where you can just go and dump your data because that was the requirement it was looking like. So we thought, okay, because we have read about it that PostgreSQL is providing you a document store that you can use there. So, but we were not using it. So there are three types of option that this is this guy is providing there. That is one is XML, second one is called HStore and third is JSON. So normally I'm not going to talk about XML because I have not tested upon this because the application that is running on Java and normally they will be I mean JSON format will be better for them. So what we have tested that HStore and JSON that we tested that if how it works there just we did some benchmarking on that, okay. So this first HStore, okay. So this is not part of core PostgreSQL, okay. This is a country module that is giving you this feature for storing the document type, right. So this is giving you a where you can store your is not like normal databases. How you store in the role level, you can store your data in a document level, right. That's what we wanted, right. And only the better one plus thing that you are getting, that what our DBMS feature that is it compilancing there. And you can map is whatever keys and values that are being stored as strings there. And they are even providing you some rich functions where you can to process over data. First you just insert under two different kind of processing they are providing for type just pasted here some examples like if we actually have a document there, so A is your key. So if you can just see that what, sorry. So what is the value of A there that you can get? In second it is some if condition if A is present in a document that there is like if A has the key has value two is present in that. So such operators it is providing there. And there is even it is giving you indexing feature there. There are two types of indexing that is it is providing that is just engine. So we have tested the both indexing how it works and when you are fetching the data from there. And whenever you create this indexing so it is not like you have to go and create over particular keys there. Whenever you are indexing it creates indexing is being done over a document level and it creates indexing on each keys there. So even if normal text indexes if what in normal rdbms how you create there in post case if you have a text field over that you create expression indexes right. So same indexes also if you want you can use it here if you have such requirement there. It is I have just pasted some example like how I mean it is a normal extension. So there is a very simple command you just create extension hs store and now that extension is created you know in your database. And now you can use it say this is just like how you create table. How you are creating the index there and some queries how you perform there. So using normal SQL you are you can retrieve those values on the keys and giving some filter conditions like that. Second thing that we tested that second approach that post guess is providing. So JSON that is like I think very famous these days. So normally it was introduced in 9.2 version that was the last stable version currently we have 9.3 that is there. But in 9.2 they just introduced it as a normal JSON but internally it was being stored as text only. Only thing that what it was providing it was giving you a validation layer when you are inserting the data into table. So it will just validate it is a proper JSON format. But internally it was storing it as a normal text. So it is not that good in performance and all it is like a normal text storage. So whenever you are retrieving that query becomes very costly. So that is what the problem was with 9.2, 9.3 they gave some more new features for fetching the data and do different operations on that JSON type. But it is still due to the storage how they were doing it is that is what because I have tested next slides I will show you the performance so I have tested on 9.3 only. So the performance was not good due to its storage thing how it is doing. So that is what they are going to fix in 9.4 actually where they are introducing that JSON binary format. So now finally they are instead of storing it as text they are going to store it as a normal JSON format there. So in that case even they are giving you a more indexing features there where retrieval is going to be better there and even some more functions are being introduced there. And other than this for even in H store of JSON if you want your performance to be some better what there is some unlogging feature that PostgreSQL is providing. So that was also we have tested. So normally if you know that there is some data that is you do not there is two thing right if there is whatever data that is being logged in something called axe log there. So if you want key my queries should be faster I do not want that my data should be that like if your server going down and you have some backup and you do not want that whenever my server is coming up my data should be like you know available there. So in that case if you are thinking about performance more than reliability you can use your unlogged feature as well. These are some function where you can to migrate between H store to JSON if you want like first you introduced you just started using H store and now like if 9.4 came and now you want to move to JSON. So these functions are being provided where that will help in fetching from H store and migrating to JSON format. So here is some testing that I did there just to convince them that if we can go with this approach there. So what data I used that I just created on CSV file where I generated this two million data and it was a normal laptop with 8 GB RAM there and on that it was being tested. So PostgreSQL was installed there and Mongo was installed there. And if you see the first thing was being test that what is the right speed there. So for this this is for 2 million. So if you see the graph that how many records per second it was being inserted there. So there was one normal H store type there was there was other was with just index with gene index and then JSON and then Mongo. Mongo has that index on primary key there. So this was the result that it came there. So I think here gene was the slowest in this insertion part there. And next was what volume it was taking on the disk. So if you see is why the gene was slow in the writing if you see how it is how it is stores the data. So in that indexing size is much more than what indexing size is this. But JSON was as normal as just here just when you are miswriting is ok there. Mongo DB size was if we compare it was too much for I mean I am not sure how they store that data there. And then the some selection queries were performed first one I tested on giving the filter condition on primary keys and other was on some text key filter. So this is the result that came there. So yes so when I am querying on primary key the just and the gene they were not good in that condition if you compare with JSON on Mongo. Next one was when the query is being faced on any key filter if whatever is present in the document. So in that case this was doing good if in comparison to if we are comparing with Mongo's time that in milliseconds. So yeah what conclusions we got from all this testing. So yes it we can handle schema less database here I mean sorry schema less data here. And its storage is really very efficient if we are if you talk about that with gist indexing there and even you have that some build indexes you can build indexes on expression as well. And the basic difference that we found that what is between that gist indexing because finally JSON we did not find good with this version. So we thought for HStore and in HStore you had two options. So gist was looking better for when you have the data dynamic in that case because retrieval is much faster in that gist indexing. So we decided to go with HStore gist there. So yeah what you are getting in PostgreSQL here you are normally we didn't do much changes there whatever was existing system you just install the extension there and now as normally you were using your SQL your transaction your constraints. Yeah constraints is also that you can use like normally you even you want to more more layer of validation there you can use check constraints over your that column there and even you can do normal joins and you are getting that is key malice features as well and we saved our migration cost and new set of of no SQL DBs and only problem here is that these all are not RDBMS given feature but it is only for PostgreSQL. So now if you tomorrow you want to migrate to some other RDBMS or something so that is not possible in that case you need to move to no SQL for it at least this reporting part yeah thank you any questions. Quick question so you spoke about HStore and I saw in one of your initial styles you had one million row per second or something something that said one million per hour sorry per hour yeah that was that is the production requirement when the application came that came that this will be the data that they were expecting okay this is what our graph I show I'm showing I'm showing with the when we tested that with this much data okay so your HStore is going to require some storage system right because looks like you you're probably getting a lot of data and how do you how do you store it is it backed up with sand internal disk or internal disk and what do we for managing that much data even we introduce their table partitioning right hourly thing normally it is like every hour we have one partition there okay so normally the data comes and for like the data is coming in format of CSV file so we are managing that that CSV file should have that our mention and normally it is directly going to into that partition there okay and when you need to do your cleanup because you're talking documents store now right it's not like any RDBMS system where cleanups are very easy to work on how how easy are you know are there challenges in keeping your database cleaned up right so in our case it is normal like it is like you want to keep data for seven days and in that case you just go and delete the old partition that's what we are that's all okay it's it's basically date range partition system that you maintain okay cool thanks till what volume of data have you seen the performance to be stable till what volume what how many GBs of data have you seen the performance to be constant to be predictable so as I told already we are just keeping data for seven days there and normally the query that this time is happening you have indexes on each partition there so till now actually it is working good we have not so for seven days around how much data would be there it will be around 75 GB 75 GB


The Equitable Life Assurance Society presents This Is Your FBI. This Is Your FBI, the official broadcast from the files of the Federal Bureau of Investigation. Presented as a public service by the Equitable Life Assurance Society of the United States and the Equitable Society's representative in your community. The Equitable Life Assurance Society It can happen to you tonight. You're sitting right where you are now listening to this program and suddenly... Yes? This is the Radio Checking Bureau. Is your radio turned on? Why, yes, it is. Do you know who sponsors that program? Sure I do. It's the Equitable Life Assurance Society. I listened to this equitable program last week and heard about the Equitable Society's fact-finding chart for fathers and mothers. My Equitable Society representative brought me a copy, so naturally I know that this Is Your FBI is sponsored by the Equitable Society. In about 15 minutes, I'll be back with full information about the Equitable Society's fact-finding chart for fathers and mothers. Tonight's FBI file, The Mercenary Mother. The current crime wave in the United States. A wave which is proceeding at the unprecedented rate of nearly 5,000 major crimes every day is composed of an infinite variety of illegal actions. Behind every one of these crimes, there is a reason. A reason which might be revenge or passion or just ordinary greed. Whatever the rational explanation might be, the underlying motive in many cases is easily understandable. Not that any crime, however minor, can in any sense be condoned. But there are times in the lives of men when the pressures of society and their own basic weaknesses drive them to break the law or to take that law into their own hands. However, there is one breed of criminal for whom there can be no possible excuse and on whose behalf not a single word can be said, for his crime is vicious and venal. He is the criminal you are about to meet. The night's file opens in a shabby corner saloon located in one of the poorer districts of a large Midwestern city. Seated at a table toward the rear is a thin, tired-looking man holding his head in his hands and gazing at the drink in front of him. Another customer approaches to Peter. Hello, Peter, my boy. Hello, Cap. Well, you seem to be engaged in serious talk. I am. I'm in a jackpot. Perhaps we can arrive at some solution, Peter. Mind if I sit down? No, go ahead. Thank you.  Okay, I guess. You guess? Don't tell me there's trouble at all. I off count. Don't worry, I have no desire to pry into your personal affairs. Peter, you know that. Okay, forget it. It's merely seemed to me that I might be of more solace to you than with me. I got trouble, count. Oh, Peter, you know me well enough to know that it is anything I can do. Nobody can help. I have performed some astounding feats in my time, Peter. Have you got a red-headed kid? Well, I don't happen to have one on me, but I'm sure there must be one available. Well, that's what I need, sir.  Yeah. Well, what would you do with one if you found it? Well, Marion figured out a new racket. She got a list of rich families who want to adopt a kid. We're acting like the middleman. I see. We did fine with a kid last week, but now we got a customer who wants a redhead. Why? I don't know. But she won't take no other kind. Peter, you're a very fortunate young man. Me? Why? It's purely coincidence, of course, but I happen to know of a child who is redheaded and who can be purchased quite reasonably. Are you leveling? Most assuredly. I know it's mother. When would you like to deliver it? Won't you need to talk to her? I'll speak to her this evening if you'd like. Okay, go ahead and make a deal. How much should I offer? How much do you want for yourself? My commission should be, oh, let us say, 100. Well, okay. Splendid. Offer a dime, 150. I suppose she wants more than that. Oh, count. I can't afford to spend more for a baby. I'm not getting this kid for pleasure. Babies are my business. I understand perfectly, Peter. I shall call on you tomorrow at noon. Marion. What? Can I have another cup of coffee? What's the matter with you? I got a terrible hangover. You didn't get drunk last night. You wouldn't have a hangover. That's the first thing you said that I agreed with. You were supposed to be working yesterday. Well, I was working. You sent me out to find a redheaded kid, didn't you? I didn't ask you to find him in a saloon. Well, I got the kid. You what? Yeah, I hired the count to get one for us.  He knew where he could get a redheaded kid for 100 and a half. I don't believe it. Honest. I promised him 100 for swinging the deal. Why should we have to cut him in? Marion, we're going to get 1,000 for the kid. Into the door! Okay. Good morning, Peter. Hi, count. Come on in. Good morning, Marion. How'd you make out, count? Then did the high close the transaction within an hour after you had commissioned me. Where's the kid? Up on 78th Street. When can you get him? Immediately. I could have gotten a little tight last night if I'd wanted to. Well, why didn't you? Peter said that I could spend as much as $150 for the child. Wasn't that enough? Yes. Well, then why didn't you get the kid and bring him down here? Unfortunately, I didn't happen to have $150. Can you get the kid now if I give you the bill? I shall deliver the child to you within an hour after the money is deposited with me. Okay. Where'll I get my foot? Have you seen the kid? No, but Mrs. Price, that's the child's mother, has assured me that he's a splendid physical specimen. Good, why, count? There's nothing there, is there? Okay, count. Here's a hundred and a half. I, uh, hate to bring this matter up, Marion, but, uh... But what? I have something coming, you know. He means a hundred. You get that when we get the kid. That's very fair of you.  A short while later in the local FBI field office, special agent Jim Taylor is greeting a friend of his, Sergeant Ray Kimberley at the local police. Well, I'm a cheerer, eh? Thanks, Jim. Even you're busy? Yes, it's what I want to see your agent in charge about. Oh, what have you got? Well, I'm not sure it's an FBI job, but he asked me to check with you in case it turns out to be. Kidnapping. Kidnapping? When? Where? Right here in town, 7th Avenue and 78th Street.  Yeah, that's right. Who was kidnapped? A baby named Martha Price. Mrs. Price caught us less than an hour ago. Any motive? It couldn't have been ransom. Most of the family's up there can barely buy enough food. Yet, child's only eight and a half months old, he couldn't have walked out by himself. Any alarm been sent out yet? Yes. Ray, what's the story on the family? Well, it seems that Mr. and Mrs. Price were divorced shortly after the baby was born. Court awarded her the custody of the child. Well, then it's barely possible that Mr. Price did the kidnapping himself. Is he in town? I don't know, Jim. I'll have the office check on that, OK? You've been to see Mrs. Price yet? No, I thought you and I'd take her on a bed together. Fine, let's go. What do you want? Who are you talking to? When? On the phone. Oh, that was Joe Green. What did he want? He located some kids and he thought we might want to buy him. How does he know we're in the market for kids? I saw him last night. Oh, I guess I told him. Why didn't you take an ad and a paper? I'll lay you off, will you? What time is it? It's, uh, 3.20 twice. Your friend, the count, has been gone over an hour. Well, maybe the kid's old lady wasn't home. I got a hundred and a half invested in this deal. I ain't interested in maybe. Relax.  Open the door! OK. Hiya, Count. You got the kid, huh? Yes, yes, I have him. He's apparently wired for sound. Well, come on, bring him in. Thank you. Hey, look, Marion, he's got the kid. Let me take a look at him. Hey, he ain't got no blankets on him. He must be cold.  Hey, wait, we got a baby blanket around here. I'll get it for him. Uh, get something that will make him stop crying. I'll take care of that. Oh. I'll give him some of this medicine we've used before on other kids. That should keep him quiet. It's the blanket. Wait a minute! I'm giving him some medicine. OK. There. That's that. Now, look at that. The little creature is calming down. Yeah, I guess he likes her. Why, you chowderhead.  My good lady, are you addressing me? I am. What's the matter, Marion? Look under the baby's cap. Take a look at the kid's hair.  Oh, dear, so it is. I had no idea the little fellow's hair was black. I told you, Count. You remember I said we needed a red-headed kid? Well, I thought this little chap's hair would be red. Why? I've seen his mother at a saloon on the west side on frequent occasions, and she has red hair. Oh. I assumed the child would have red hair, too. Didn't you ever think maybe the old lady dyed her hair? Hardly.  Before I resort to such a drastic measure, I have a suggestion. What? Assuming that the child's mother did dye her hair. What is there to prevent us from doing the same for the child? Hey, that's a good idea. Great. Brilliant.   Now take him back. All right. Go ahead, Jim, slide in this way. Okay, thanks. I didn't mention anything about that phone call I got up there because I didn't want a standing in front of Mrs. Price. I figured that. Well, the office calling me. They look at it Mr. Price. He's out on the west coast. We can drop him as a suspect. I think the story Mrs. Price told us was nothing but lies, Jim. Yeah, I agree with you. I wonder what she's hiding. I don't know, Ray. That neighbor you spoke to, she said she saw a tall middle-aged man leave with the child. Yeah, that's right. Any more specifics on his description? No, she was pretty vague. She did give me a fill-in on Mrs. Price, though. Said she spends most of her time in saloons. Yeah, to guess that. Well, the lights changed, Jim. Oh, yeah. You know, I wish they'd pass a law that no unascorted women could go into a salon. A law like that would put half the places in this neighborhood out of business. Make our job a lot easier. If we knew what the tall man really looked like, we might find him in one of these saloons. Well, at least we got a picture of the baby. I'll have the office make copies and send him out. Okay, Jim. Then we'll just have to wait for a break, Ray. Soon as we get one, we go back to work. What is it? Hiya! What do you want? That kid the count brought down here. Didn't you say his name was Price? Said he was from 78th Street? That's right. What about it? He never bought that kid. He snatched him. What? He was just on the radio. The cops are out looking for the kid and for a tall man one of the neighbors saw leaving with the kid. Well, what are you worried about? The count's on his way back up there. Don't nail him. That's what I'm afraid of. Marion, I don't get it. First you wrapped the count. Now you're worried about him getting nailed. I don't care about him. I care about me. You don't think I trust that old stew bum, do you? All they gotta do is take away his bottles of five hours and he'll tell him everything. Answer the phone! Okay. Hello? Yeah, hello, count. Yeah, I know Marion heard it on the radio. Well, that's fine. Don't worry about it, count. It's the best news I had all day. Go on. Yeah, right. I told you. You had nothing to worry about. That was the count. Yeah. Well, where was he? I don't know, but he wasn't with no cops. And we got no trouble. Why not? He ain't got the kid anymore. He lost them. We will return in just a moment to tonight's file which shows how your FBI promotes security for the nation. Now let's bring this question of security closer to home. Last year on this program, the Equitable Life Assurance Society offered members of the audience a special fact-finding chart for fathers and mothers. It sounds interesting. Can you still get one? Yes, Fred. A new and enlarged fact-finding chart for fathers and mothers has just been published. I have one here. Well, just what's it all about, anyway. Fred, it answers a question every man who loves his family ought to ask himself. That question is, if I should die, how much money would it take to keep my family well-fed, well-housed, and well-closed? You know, that thought has worried me for years. Well, that worry is over now, Fred. With this Equitable Society chart, you'll have the answer in five minutes' flat. Look, you're guided every step of the way by easy-to-understand pictures which illustrate the rock-bottom expenses your family will have to meet. And when you're finished, you'll have a clear, accurate, and complete picture of just what income your family would need during the critical years. Now, just a second, Mr. Keating. What do you mean critical years? The years before your youngest child finishes high school. Years during which the home must have a minimum income to keep it together. Okay, I don't need to know anymore. Where do I get one of these fact-finding charts, and how much does it cost? Well, it doesn't cost a cent. The Equitable Society representative in your community will be glad to bring you a copy.  There's no obligation, and get a true picture of where you stand. Phone him tomorrow to bring you an equitable fact-finding chart for fathers and mothers. Or send a postcard care of this ABC station to the Equitable Society. That's E-Q-U-I-T-A-B-L-E. The Equitable Life Assurance Society of the United States. And now back to the FBI file. The mercenary mother. There are no readily available statistics on the number of decent families in the United States who, for one reason or another, would like to adopt a child and to accept the many responsibilities that go with the raising of that child. Such an adoption is possible today through the offices of many reputable organizations. Organizations which take great care to see that the new parents are fit people financially, physically, and morally. But sometimes that procedure takes a period of many months. Months of waiting and hoping and waiting again. Not every family is willing to go through that period. And so they seek their relief through one of many un-moral baby brokers. And buy their child over the counter. Buy him as if he were a puppy in a window. Buy him in one of the last remnants of wartime life. The baby black market. Tonight's file continues one hour later in the apartment of Pete and Marion Sheridan. Ain't you going to tell me to answer the door? Go ahead. Okay. Hello, Peter. Count, what are you doing here? I just naturally gravitated. May I come in? Yeah, come ahead. It's a count, Marion. What do you want? Just returning to our home base. This ain't home base. What happened to the kid? I told Peter on the phone. I lost him. Where? In a saloon. Naturally. How could you lose a kid in a saloon? Well, I was standing at the bar when I saw a friend passing by outside. I left it at a hike by a pretzel bow. When I returned, he was gone. You mean the kid met a friend too? Don't be absurd. The cops are looking all over town for you both. Yes, yes, sir, I've heard. That's why I came here. I need your assistance. Since you were the cause of my present troubles, I feel it no more than right that you should finance a trip out of town. What? It might prove awkward for both of you if I were to be arrested. What are you driving at? I need about a thousand dollars. You won't get it here.  I think we ought to give the council a dope. Where are you going to get it? Joe Cream told me you could get three kids. I'll go get them and you sell them. I've got some good news. The price baby's been found. That's fine. Where? At a place called the Three Star Saloon. Who found him? The cab driver went into the saloon for a beer. Saw the baby in a cardboard box. Have you spoken to the cab driver, Ray? Yes, he says that when the bartender said he didn't know whose baby it was, he suddenly remembered the story of the kidnapping in the papers. I see. How long ago did all this happen? Four by an hour ago.  Have the child been harmed? No, no, one of our doctors examined him. It's all right. Just a little hungry. Have you seen Mrs. Price and the baby who has returned to her? Yeah, I just came from there. And? She admitted under questioning she thought she knew who took the youngster. What did she think it was? It seems that a man whose name she doesn't know came to her and offered her $150 for her child. A man she doesn't know did that? Well, she says she's seen him around the Three Star Saloon a couple of times, but she doesn't know his name. At the same place the baby was found? Yeah, that's right. Did you give her any description of this man? Yes, but I'm afraid it's too sketchy to do us any good. Well, she turned the man's offer down as she claims. How does she account for the baby's disappearance? Well, she says that at first she accepted the offer, then after thinking it over, she told the man she wasn't going through with the deal. Well, she sounds like a fine mother. Yeah. Look, will you have these prints run through your identity section, Jim? Sure, sure. Where are they from? There was a rattle in the cardboard box with the youngster that Mrs. Price fortunately hadn't touched. I got these prints over, but we don't have anything in our files that matches. I'll send them down right now, Ray. You get any other leads? Yes, there's a pink blanket in this package here. Pink blanket? Yeah, the baby was wrapped in it when he was returned. It's not his blanket. Okay, I'll have a lab check-up for loan remarks, and then he'll say fine. Thanks, Jim. As soon as I get any report back, Ray, I'll call you. Would you mind if I have another drink, Marion? Go ahead. Thank you. Should I mix one for you? No, thanks. Hey, I do hope Peter is able to do business with his friend. He shouldn't have too much trouble. The kids are for sale. A toast to your attitude, Marion. It's so realistic.  Marion, I'm sure that not even your worst enemy could accuse you of being sentimental. Hello, Peter. How did you make out? I saw the kids. They're real scrawny. How much can we get them for? Including a hundred for Joe. All three kids are cost us four fifty. Sounds like a rare bargain. Be quiet, will you? I told Joe I'd call him if you wanted the kids. He can pick them up and deliver them. I think I'll go down and get another bottle of whiskey while we're waiting. No, you don't count. I want you getting picked up. Pete. Huh? Go in and call Joe and tell him to get those kids up here as soon as he can. I got you a message when I came back from dinner. I have a report from the IDent section on that rattle. Oh, good. What did it show? Those prints belong to a woman named Marion Sheridan. Marion Sheridan? I don't think I know that name. Well, there's no reason why you should, Ray. I don't think she's ever worked around here before. Let me see. But we've been looking for her and her husband, Pete Sheridan, for some time now. Oh, before? A swindling charge down south. I guess Pete Sheridan was the one who made the offer to the infant's mother. No, no, Ray's not. I got his picture out of our files and went up to show it to Mrs. Price. She claims that the tall man she told us about doesn't look anything like Sheridan. You think she's telling the truth? Well, I don't know why she should start telling the truth now, but somehow I think she is. The odd thing about all this is that a study of Marion and Peter Sheridan's records show that they never worked with anyone else. It's always been just the two of them. There's nothing at all in either record that would supply a clue on the tall man? Nothing that I could find. Oh, how about the blankets? You have any report on that? Yeah, that came in, too. There's no laundry marks of any kind on it. No, that's too bad. And it's such an ordinary type of blanket. I checked and it's sold in over 150 stores, right here in town. That takes care of the blanket, then. Except for one thing? What's that? Well, the blanket was rather liberally stained. The lab is analyzing the stains now. Well, have you sent out any alarm when the Sheridan's here? No. No way. I'd rather not send one out if we can help it. So far as we know now, they don't have the slightest idea that we're looking for them. Oh, excuse me. Flashlight's in Taylor. Yeah. Yeah, just a minute. We're out. I want to get a pencil. Okay, go ahead. Attachum citrate. Aspirin. Keisha. And all right. Syrup of Orange? Yeah. All right. Thanks very much. Bye. That was a lab, Ray. Here's a breakdown on the stains around the blanket. Take a look. That's quick work, too. Well, this fellow's in the lab. Oh, wonderful. They break open more cases and they get credit for it. I think maybe they're giving us the late we won on this one, too. Let's make some phone calls and find out. Oh, that's not bad, Count. Two phone calls, two customers, two baby souls.  Jay, thanks. Pete. Pete. What do you want? The cops found the price kid and returned it. I just heard it on the radio. Well? I don't like it. Why not? It takes the heat off us. It might not. Mary, now that you've forgotten some cash, wouldn't it be a good idea if I... If you went under for a while, that'd be a great idea. Exactly what I was about to say. Now, if you'd be kind enough to advance me, let us say... Save it, Count. You're not getting any dough. But, Mary, if he gets picked up, it might be trouble. He's right. There is always a chance that the police might make me talk. Don't worry. Hey, Mary, what's with the gun? What do you think?  It's gone, you count. But you can't get away with this. Oh, no. Drop that gun, Mr. Sheriff. What? You heard what he said. Drop it. Now, walk over to that wall.  The police, I presume. I'm a special agent of the FBI. Of course you realize I have nothing to do with these people. I merely stop by here for a drink. He's lying. I think we can let a judge decide that. Now, come on. Let's get out of here. The count whose real name was George Bedford, together with Peter and Mary and Sheridan, were turned over to local authorities for prosecution on charges of obtaining under false pretenses and conspiracy to violate the state kidnapping laws. They were each sentenced to 10 years in the state penitentiary. And thus, another evil combination of criminals was broken up by the combined efforts of a local police department and your FBI. Special Agent Taylor was able to find these criminals because the pink baby blanket had a number of stains on it. Stains which the FBI laboratory analyzed and found to be a prescribed baby remedy. All drug stores in the neighborhood where the baby was found were checked. And the records of one revealed that such a prescription had been filled for Mrs. Sheridan. And so, with such a slender lead as the stains on a baby's blanket, your FBI was able to close another case and to close it with one word written across the file. The word convicted. In just a moment, we will tell you about next week's exciting case from the official files of your FBI. Now, one more point about the equitable society's back-finding chart for fathers and mothers. Believe me, Mr. Keating, that chart is just what the doctor ordered for a man like me. From now on, I'm through guessing. I'll know what my wife and kids will need and once I really know, I'll do something about it. Just let me get my hand on one of these charts. Well, Fred, the man who'll see that you get one of these back-finding charts is your Equitable Society representative. No charge or obligation, of course. Make a note to phone your Equitable Society representative soon. Or send a postcard, carry this ABC station to the Equitable Life Assurance Society of the United States. Next week, we will dramatize another case from the files of the Federal Bureau of Investigation. It's revealing the operations of a transatlantic criminal. Its subject, crime on the high seas. Its title, the round-trip murder. The incidents used in tonight's Equitable Life Assurance Society's broadcast are adapted from the files of the Federal Bureau of Investigation. However, all names used are fictitious and any similarity thereof to the names of persons living or dead is accidental. Tonight, the music was composed and conducted by Frederick Steiner, the author was Jerry Lewis, your narrator was William Woodson, and special agent Taylor was played by Stacey Harris. This is your FBI is a Jerry Divine production. This is Larry Keating speaking for the Equitable Life Assurance Society of the United States and the Equitable Society's representative in your community. And inviting you to tune in again next week at this same time when the Equitable Life Assurance Society will bring you another thrilling story from the files of the Federal Bureau of Investigation. The round-trip murder on this is your FBI. This is ABC, the American Broadcasting Company.


A long time ago, I decided to curate my own art exhibition. It would be a solo exhibition, and my first. I had previously curated another artist's exhibition several years prior to this, and I must say it was a resounding success. One problem that kept nagging at me about the impending event was that I wasn't an artist. I had never produced any expressive content, and now I had to do it all alone. I had loads of expressive talent, had great success as an architect, and an even larger hunger for storytelling to go with it, all of which I was extremely confident of. But regardless of these facts, doubts crept into my mind anyway, up to the opening night. Was I talented enough? Would I be able to do everything by myself? Would it be up to my expectations? That moment of question that I went through is a phenomenon called impostor syndrome. This phenomenon is not a mental disorder, but is a psychological incident where doubt invades our being, regardless of how much knowledge, talent, experience, or confidence we might have. People who struggle with this disorder are typically those who excel in their fields, be it business, healthcare, or the expressive arts. Yet nonetheless, a fear is born when they feel they might be exposed as frauds, despite all the historical real proof and tangible success present, that would prove to them otherwise. This isn't a circumstance of glass half empty or half full. The glass in this case is certainly almost full up to the rim, but even with all that hard data looking you in the eye, you still manage to look at that thin sliver of emptiness that plays with your mind, telling you that you're not good enough, compounding its weight of doubt on your shoulders, your knowledge, experience, and confidence, all these powerful tools that you typically stand on as your foundation of excellence at this moment seem distant and trivial to you. This is the point when your perception overcomes the reality, but why? To answer this question, we should identify the personal behavioral traits that lead people to struggling with the syndrome. These are the five characteristics that are experienced. The need to be the best, the need to do the most, the need to not need others, the need to always feel competent, the need to feel that you know it all. The reality of the matter is that all these traits start with so much positivity. This is the delusion. Every single trait, whether it's wanting to be the best or do the most, all suggests that you are exceptionally good at what you do and work very hard for it. There is so much strength in this syndrome that must be recognized. Wanting to feel competent means you're already very intelligent. Even the need to do things on your own means that you can do things on your own. Doing things with others will just take you to a new threshold of achievement. Now that there's a clear distinct line between the facts and the fiction, let us reveal the three things that can help you confront, marginalize, and overcome your imposter syndrome moment. Question Yourself Criticism Separate yourself from your negative thoughts. Challenge them by asking yourself about the realities of your self-criticism. Exercise the emotion and look at the pure thoughts that are crippling your ability to act and do. Do they hold water? Self-criticism is weakest once disassociated from fear and emotion. Review your own achievements and successes. Come back to reality by performing a mental recollection of your various wins and accomplishments. Go in detail about how you achieved what you did. It's not about tooting your own horn, but with this practice you will regain your fundamental footings and stand firm while confronting your moment of doubt. Instead comparing yourself to others. What doesn't help is when you look outside yourself at moments when you're about to perform. It doesn't matter what she or he did. It's what you will do that makes whatever you're about to do unique to you. As in any other previous positive outcome you've experienced, your successes came from within you and only you. Doubt is a natural part of our being. The challenge or aim is to minimize the amount of time that doubt manifests within us, to consume its oxygen quickly so that its destructive flame is extinguished before it has any time to wreak havoc on our ability to perform and produce.


Political Thought on the Just Rebellion Part 6 Last week we looked at the Maori rebellion in New Zealand, and we began looking at the nature of syncretic thought, thought from different cultures put together to establish a framework from which rebellion might be possible. I want to continue that particular theme this week by looking at a number of rebellions that you might loosely call magic rebellions, mythologically based rebellions, but all the same looking at mythologies that are either genuinely very old or which have been especially created for the purpose of rebellion. We can begin at the very start of the 20th century with the Boxer uprising against foreign rule in the great Chinese cities. Imperial armies of the emperor had failed to dislodge the foreign occupation. The use of boxes, or what we would today call kung fu fighters, was an artifice devised not only by the ruling elite in China, but something which had great popular support among the rank and file of the citizens of the different Chinese cities. These fighters who were recruited from the streets were promised that if they undertook certain forms of magical training, kung fu training, then they would become invulnerable. The weapons of the foreign occupiers could not harm them. So the uprising turned into something which was simultaneously extremely brave, but also extremely tragic, because tens of thousands of boxes were of course slaughtered by the guns of the occupying powers. I begin with the boxes because curiously in Uganda, many years later, one of the surviving boxes, or rather his spirit, surfaced in the head of an African rebel who rose up along magical lines to challenge the rule of the government in Uganda. That person was Alice Laquena after the fall of Idi Amin, after unsuccessful interim governments, after a bloody successor government led by Miltanobote. Rebellion and war returned to Uganda, and it was won by a faction led by the current president, Moseveni, who all the same was unable to unite the country. And the Acheoli people thinking that the historical privileges would be taken away from them rose up underneath a prophetess who adopted the name Alice Laquena. Her head was said to have been inhabited by a high command of spirits drawn not only from Africa, but from all around the world. There were scientists, one of them was a doctor wrong element. There were field marshals from previous great battles. There was a Chinese spirit, Qing Po, who had survived in one way or another the slaughters of the box rub rising, and now inhabited Alice as one of her advisors. All of this might seem to be the stuff of mystery and nonsense, but Alice also had an extraordinarily well-organized side to her rebellion. She wrote a military manual for her soldiers. She wrote a health and safety manual for proper conduct during war. She infused her people with the suggestion that they too, if they adopted certain magical practices advised by her high command of spirits inside her head that they too could be invulnerable. Of course, they marched forward, and of course they were slaughtered by Moseveni's soldiers. The descendant, the spiritual descendant of Alice Laguena is Joseph Coney, who continues to be active today, continues to be the survivor of many attempts to bring him to justice or to kill him, is very, very much the survivor of all kinds of false dawns in terms of negotiated breakthroughs with Moseveni as to how to end the conflict. He's also, of course, an atrocious person in terms of the depredations and destructions that he has brought to northern Uganda, but he's also a very strangely ecumenical person. His spirits are drawn from more faiths. Coney himself celebrates every one of the major religious festivals, whether they are Jewish, whether they are Islamic, whether they are Christian, as well as a number of African religious festivals, all in an ecumenical desire to have as much spiritual power from as many sources as possible on his side. These things would seem preposterous, had they not been so effective, because the rebellion of Coney survives to this day, and this is not accomplished only by atrocity. It is accomplished in part because he has followers who believe in him and a population who, for many reasons, and despite many misgivings, might still see him as some kind of hero for their cause. The complication of thought and the bodies of thought that one requires for successful rebellion are many-fold, so that in a country like Zambia, for instance, shortly after independence, there rose up a Christian church, a so-called Christian church, led by a prophetess, Lenshina, who gave Kenneth Kawunda the ecumenical, the abrasive, the communalistic president of Zambia, a huge amount of difficulty and a huge amount of trouble. She raised up her followers along some critic Christian but also local religious lines and declared rebellion against Kawunda's Zambia. So that even the embracing, accommodating, inclusive Kawunda was forced to fight a war in which the church of Lenshina was crushed. And this was the first and probably the only war that Kawunda fought with arms. He did not fight the armed raids of the Rhodesians and the armed raids of the apartheid South Africans, but he fought Lenshina with his own army. And this is very, very odd for a man who was very, very much brought up during his early adult years on the thought of Gandhi. So we turn now to the thought of Gandhi in India, the thought that made such a huge impact on the liberation struggle in that country in the 1930s, the 1940s, before independence finally came in 1947, thought to do with nonviolent resistance. But Gandhi himself had been formed by experiences in more than one country, in Great Britain, in South Africa. In all of these places, he gathered the ammunition of thought and strategy as to how best he might take his struggle forward. Of course, Gandhi was famous for the image of Gandhi, the image of a simple man, the image of a man at his spinning wheel, the image of a man who was in touch with the spiritual heritage of India. Of course, all of this to a certain extent was true. A lot of this was also something which flattered to deceive. It meant he could leave the hard political work to someone like Nehru. By hard, I mean the often vexatious and compromising negotiations and discussions which had to take place with the British. And of course, the drawing upon Hindu mythology, the drawing upon Hindu legends, meant an exclusion of the Islamic participation in Gandhi's struggle for a new India. Who's India? How can you develop a united India where one part of the community is excluded from the foundation thought of rebellion which is meant to lead to an independent country? All the same, the mythological nature of Indian history has made its way past Gandhi into the body politic in India today. The whole idea of Hindu faith, the whole idea that there is a cosmic justification for the Indian nation, for the Indian state, is something which still informs Indian politics today. In a sense, none of us after successful rebellions ever get over our founding mythologies, our founding legends. A lot of this, however, has to be contrived. A lot of this has to be exclusive. Some people are kept out of the founding mythologies. And a lot of this is quite inclusive in a way which would only be possible in the 20th and 21st century whereby the thought of many nations is brought to bear to achieve the successful rebellion of one.


So how do you go from doing one-day service design workshops to doing bigger service design projects where you get to work on actual bigger challenges that may impact on the company and its customers? That was one of the questions I got from Eleonora who's part of my selling service design with confidence course and that's exactly the question I want to answer in this video because I see that there is a big misconception on how to scale up service design work and the misconception is that you by starting small it's much easier to scale up in the end well the truth is starting small and keeping it small makes it really really extremely difficult to scale up so the trick or the way I try to approach this is even when you are talking with a potential client about doing a one-day training session make sure that you always talk about the bigger picture and the bigger picture in this case is where does a client want to be in a year? Where do they want to be in two years and how is this workshop or training contributing to that because if you know what the bigger picture is if you know what the end goal is you'll see that the workshop or the training program can never be the end point so what usually happens when you just talk about the workshop after doing a workshop somebody has to think again about what the next step is and if we should take the next step well if everybody's clear on the bigger picture why are we doing this the chances are less likely that they will actually stop after the workshop because you haven't reached the bigger goal so it's much natural to transition from the training to the next step which is again the next step to achieving the bigger goal so if you want to scale up service design work if you want to scale up your service design work my advice would be always make sure to talk about the bigger picture the bigger goal that your client wants to achieve even if you're pitching for a one-day session I'm really curious what your strategy or tactic is for scaling service design work and making it bigger working on bigger projects make sure to leave a comment and let's learn from each other and if you enjoyed this video make sure to grab the link and share it with somebody who might benefit from it too thanks for your time and I'll see you in the next video