Destroying the value proposition of Bitcoin, which mean you agree on which is like it's censorship resistance You make so you mentioned pay join and mixing. Is there like some simple hygiene practices people can do today?  So if you got a pay if you got one Bitcoin, right a UTX O of one Bitcoin and You owe somebody point one Bitcoin. It's actually a transaction that sends Point one to them and point nine back to you so pay join allows merchants to join in this pool of all these random people making transactions to find the UTX O's that are more efficient and fit together So you'll get a transaction back from someone else and it's really hard to follow the the trail of You know it went in and it came back because it's going to go in it's going to go to somebody else And then theirs is going to come to you. So it's like a really smart way to obfuscate the the trail of UTX O's Wasabi is a way to Properly clean your Bitcoin, you know, you don't want to be leaving privacy leaks everywhere when you're using Bitcoin so you can use wasabi to like join these mixing rounds basically where like lots of people from all over the world are Exchanging UTX O's with each other and you get them back in like point one Bitcoin chunks And if you're going to be using that it's good for your privacy But you got to be careful that you don't leak data In other ways if you're really like if you're in a place where you need to use mixing and you need this for your safety then You don't want to mix a Bitcoin and then pay Pay somebody with some Bitcoin that's tied to your identity and some of your mixed Bitcoin and your clean Bitcoin because Then you're just really you're linking them together and they can just follow all the rest of your trails or whatever so I'm a big fan of like encouraging people to Go to like, you know if they want to get some Bitcoin bull Bitcoin does mixing by default like they clean the Bitcoin and give it to you I like Jaco mozuko's terminology there a lot of people think like Bitcoin that was on Silk Road or that's used to buy drugs or whatever as dirty Bitcoin, but he looks at it like KYC linked to Bitcoin is dirty Bitcoin Clean your Bitcoin and clean off that dirty KYC linkage clean off all those privacy leaking trails Run it through wasabi or samurai wallet or pay join or something like that and destroy any of these leaks because these vultures these chain analysis vultures that will try to like docks anybody who's using Bitcoin and identify who's using Bitcoin and Report it to the government or whoever they're reporting it to Why let why let it be dirty right like in that way it's dirty like clean it up And you and make it nice and clean and fresh and have no links Sure people will call it tainted because it'll be mixed with small UTXO's that are probably related to some sort of crime like a Drug purchase or whatever, but fungibility is one of the most important properties of the money So there's more traces of cocaine on dollar bills and there is on Bitcoin So the more that people use fun like mixing and and think about this as a way to Protect the fungible properties of Bitcoin the more valuable Bitcoin is and the more resistance we can put up when they try to like Put these limits on Bitcoin. I think even More simpler you mentioned something interesting like a lot of these wallets have built-in features It almost makes sense if the whole ecosystem by default has these features built into their services Oh, I would love that man. You're speaking my language.  Yeah, man, like he's a real activist kind of guy and I was Recommending people wear masks and he's like super against COVID. He called me scum of the earth like because I was telling me Master whatever and so but regardless, you know, whatever people want to believe what are people want to do? it's their own prerogative but Even even though I had like me and him have a personal vendetta. I don't really care to talk to him anymore I mean, I gladly sooner just make fun of him if I ever see him But like I 100% believe in what he's doing and so I'll still recommend people go to his website and use his service Even though me and him don't get along anymore I still think it's an awesome spot for anybody who cares about privacy and it wants to acquire Bitcoin in a way that respects your privacy Do you see more wallets like wasabi and samurai doing what they're doing? Well, that's why pay join is exciting because BTC pays the river was an alternative to bit pay bit pay was the Biggest and they still are kind of the biggest payment processor for merchants to accept cryptocurrency But they chose to go on the on the big block side in the 2017 fork war You know, they chose to support the Segwit 2x version of Bitcoin, which was the corporate minor version of Bitcoin and You know, it was like That was the moment when somebody one of the Bitcoiners decided that we're you know, this is not right This is not why Bitcoin was created. So we're gonna create an alternative So they created BTC pay server and allows anybody to accept their own Bitcoin payments Any merchant any entrepreneur who wants to accept Bitcoin can use BTC pay server and now they support this mixing thing So yeah, man, it's a good it's a growing trend for sure And even ETH has that with tornado cash Great service. Yep Hopefully other wallets can incorporate that natively within their UI. I would oh man I would love to see that all the wallets. It'd be great to see all the wallets doing that


Welcome to the Dr. Gundry podcast. So what if you could unlock all the secrets of the longest living people on the planet? Well, I've got news for you. You can. On this episode, I'm gonna do a deep dive on blue zones. The five geographic reason, let's do that again. On this episode, I'm gonna do a deep dive into the blue zones, the five geographic regions that are home to some of the world's oldest but healthiest people and let you in on some secrets that could help you live the longest, healthiest life possible. And as the only nutritionist to spend most of their career living in a blue zone, I can tell you that these secrets are likely not what you are expecting. So don't go away. In a moment, I'm gonna bust some of the biggest blue zone myths, reveal my number one longevity booster when it comes to diet and share how you can set yourself up to live a long, healthy life, no matter your location. I'll also answer some of your most pressing questions on the matter straight from my Instagram. Okay, topic number one, what is a blue zone? So blue zone is a term that was coined and trademark by the journalist, Dan Butler. And it describes areas in the world that he visited that had some of the longest-lived people per percentage of population and the healthiest longest-lived people in population. And so those five places in the world that he described were Sardinia, Italy, hold that thought because it's actually only a part of Sardinia, the islands of Okinawa, Japan, the Nikoya Peninsula in Costa Rica, Ikaria, Greece, and Loma Linda, California. Whereas most of you know, I was a professor of heart surgery and pediatrics for most of my career. How and when were the blue zones discovered? Well, as I mentioned, Dan was a journalist for National Geographic and he was given the assignment to seek these places out. Now interestingly enough, since he first described these five places, there have been additional what I think we should consider blue zones that he did not visit or describe. And I've written about these in the longevity paradox. And one of them is the city of Attioroli south of Naples, Italy. And also the Katavans in Papua New Guinea. And I've mentioned both of those groups as well and we'll probably come back to talking about that. Okay, so let's get to the big question. What are people in the blue zones doing differently? Why are they living such long, healthy lives? Well, as you probably imagine, diet plays a huge role. But it's not actually as simple as you think. See, the blue zones actually have very wildly different diets from one another. So for instance, it is under a general impression that all of these blue zones owe their longevity to eating grains and beans. And in fact, that's absolutely, positively not the case. Let me give you the example of the Okinawans. The only true study of the traditional Okinawan diet was actually done by the U.S. Army in the late 1940s. And that was the last time, quite frankly, Okinawans ate their traditional diet. The Okinawans subsisted on a purple or blue sweet potato. In fact, 85% of their diet was this purple sweet potato. They had small amounts of soy in the form of fermented soy, which is not tofu. It's more tempeh and miso.  And it wasn't brown rice, it was actually white rice. So when somebody says the blue zone gets their benefit by eating beans and rice, I can assure you that the Okinawans do not get the benefits of eating beans and rice. They get the benefit by eating purple sweet potatoes. Another great example, in my upcoming book, Unlocking the Keto Code, a real shocker that even surprised me, quite frankly, is that the Sardinians who do eat, quite frankly, a lot of buckwheat bread, and the Costa Ricans who do eat a lot of beans and corn, actually both the bread and the beans and corn in these communities are negative factors that are actually offset by spoiler alert, the large amounts of sheep and goat cheeses and yogurts that both these communities eat. In fact, some startling studies show that the Sardinians who have longevity live high in the mountains and comparing them to the Sardinians that live by the sea show there's no benefit in longevity in the sea-dwelling Sardinians, only in the mountain-dwelling Sardinians, and when we break down their diet, the difference is that the mountainous people in Sardinia are sheep and goat herders and get the vast majority of their calories from goat and sheep cheese. Now, I'm not gonna tell you the spoiler of what's in the goat and sheep cheese that makes a difference. You're gonna have to stay tuned for unlocking the keto code, but the same things happen in the Nagoya Peninsula of Costa Rica. It's the goat and sheep cheese that actually makes the difference in their health not the corn and beans. So, sorry about that.  The katavans don't eat any grains, they don't eat any beans, they subsist primarily on coconuts and fish and other vegetables. So, when we look at these supposed blue zones that depend on their health by eating grains and beans, I'm sorry, the evidence does not wash. In fact, even on Crete in Greece, a great huge benefit to these people is actually from a weed, a common weed, that you'll see growing in your sidewalks, called perslane. Many of you may know it as moss rows, it may grow it as an ornamental flower in the summer. The people in Crete eat so much perslane that perslane contains a very high amount of a short chain omega-3 fat called alpha-linoleic acid, and the famous study looking at the effect of adding alpha-linoleic acid to a diet of people who had suffered a heart attack and comparing it against the American Heart Association Low Fat Diet, the famous Leon Heart Diet, or many people know it as the Lion Heart Diet. The people who got the supplementation with alpha-linoleic acid, which is present in perslane, did so much better at avoiding new heart attacks that the study was stopped after three years as unethical to continue. So, the benefit that the folks in Crete got was not eating the breads and beans, was the fact that they were eating huge amounts of perslane, which was the benefit of that diet. So it takes more than just saying, oh, look, are these people eat grains and beans, and that must be it. In fact, there's far more nuance to study the blue zone that a physician can actually extract than potentially a journalist. Now, the other thing that I write about in the longevity paradox and the plant paradox is that there's been numerous meta-analysis of the Mediterranean diet. And quite frankly, the Mediterranean diet has beans and grains as a part of the Mediterranean diet. But when we do meta-analysis of which factors in the Mediterranean diet are beneficial and which are detrimental, it turns out that both grains and beans are detrimental factors of the diet that are offset by the positive factors in the diet, and that's copious amounts of olive oil, copious amounts of fresh vegetables, copious amounts of bitter vegetables, and of course, a rather generous amount of wine in the diet. So it's these factors rather than the grains and beans that are the amazing factor. The third thing I might add, having just got back from Italy, it turns out that Italians are, as a group, very suspicious of grains and beans, and they go through extreme measures to detoxify their grains and beans. They soak their beans, and it turns out that soaking starts fermentation. So when they soak their beans for 24 hours, 48 hours, they're fermenting their beans, which decreases lectins. Plus, they throw the water out every six hours and start again, and water leaches out the lectins, and then they cook them for extended periods of time. Many cultures, particularly in South America and India, always pressure cook their grains and beans before they use them. The other thing I learned talking with some chefs is that almost all wheat flour that is used to make pasta is actually treated with a sourdough starter to ferment it before making it into pasta or even pizza. So when we say, well, they eat spaghetti and they eat beans and they eat pizza not so fast, they're eating fermented grains and beans, and that can make all the difference in the world. And I've written about this in my books. Okay, what else do they do? Well, interestingly enough, as I've talked about in all my books, I think one of the real common denominators of the Blue Zones is that they have a very low animal protein intake. Not necessarily a low fat intake, but a low animal protein intake. All of the Blue Zones actually have very limited amounts of meat in their diet. And what meats do they eat? Well, for instance, the Sardinians and the Costa Ricans actually eat mostly lamb and goat as their preferred meat. The Okinawans actually eat very little amounts of pork, but they use pork fat. So it's not that they're eating huge amounts of chicken, for instance. They do eat red meats, but the amount of the meat is very small. Now, why is this important? There's multiple reasons. And I write about this in all the books. The first, I think, overwhelming reason is that we have a cellular sensor for energy availability, and it's called MTOR or TOR, the mammalian target of rapamycin. We now know it occurs in all animals, so some people call it the target of rapamycin. This sensor actually measures energy availability, and it's very sensitive to certain animal protein amino acids that are not very prevalent in protein sources of amino acids. And when we look at turning off MTOR, longevity is the result. And we've devoted several books to that, the upcoming book, Unlocking the Keto Code, dives even more. So one of the things that they don't use is actually a lot of animal protein. The second thing that I think is very important is that in general, animal protein can be turned into a potentially harmful compound called TMAO, and it's only in animal proteins that TMAO is generated. There's a new paper out today looking at the microbiome, breaking down animal proteins and making more harmful products that stimulate aggressive prostate cancer growth. And when researchers at the Cleveland Clinic looked at over 600 men with aggressive prostate cancer, they found that they had a unique microbiome that aggressively took animal proteins and certain animal fats and produced more of these compounds that actually stimulated prostate cancer to grow. So once again, if we're trying to live a long time, we absolutely want to limit the process of generating harmful compounds, generating, turning on mTOR, and so that really helps explain why the blue zones do have extended life. Interestingly enough, speaking of cheese, having been a professor there, half of the Adventist's calories come from eating cheeses. So if you want to take away anything from this lecture as a shock value, it turns out that eating cheese, particularly certain types of cheeses, may be one of the surprising health-promoting things that you can do and stay tuned. Unlocking the keto code is going to blow you away on how that works. Since we're talking about animal protein, people keep writing in and wanting to know about the carnivore diet. And I've certainly talked about this sometimes ad nauseam. Now, why do some people swear by a carnivore diet for a long life? Well, first of all, let's be realistic. There is actually no society that follows a carnivore diet that has longevity. There isn't one. Please show me one and I'll be happy to change my mind. But there isn't one. And there's again, reasons that I just mentioned why that's probably true. So if that's true, why does the carnivore diet work short-term for some people? And it certainly does work short-term for some people. I've had a number of patients who've had a very good response to a carnivore diet. But what a carnivore diet does is actually provide a elimination diet. You basically are eliminating all sources of lectins from your diet. And in doing so, you're going to actually probably have a good result. The problem with a carnivore diet, as I talk about in Unlocking the Keto Code, is you begin starving the members of your gut microbiome community that are actually going to contribute to your long life. And if you've already read the longevity paradox or seen it on public television, you'll know that it's actually the gut microbiome and what you feed them that's going to promote your longevity more than anything else. Okay, so does that mean you have to give up meat? No, absolutely not. The adventists in general are vegetarians. There are a number of vegan adventists. And there are a number of adventists who cheat, if you will, with chicken and fish. But the vast majority are vegetarians. And again, about 50% of the calories among the vegetarian adventists in Loma Linda actually comes from cheese, from the fat from cheese. So again, keep that in the back of your mind. Now, I personally describe myself as a veg aquarium. I get my animal protein primarily by eating mollusk and shellfish and wild fish. And I may have them several times a week. But most of the time I get almost all of my calories from vegetables and olive oil and nuts. And as many of you know, there are multiple studies in the blue zones that show that a leader of olive oil in Sardinia and in Greece is one of the biggest drivers of those societies having longevity. So don't be afraid of olive oil. Can you get enough protein by just eating vegetables? And the answer of course is yes. All of the largest animals on earth only eat leaves and grass. Sorry about that. You'll not see a gorilla eating burgers. Gorillas and horses have far more muscle mass than you and I will ever have. And all they eat is leaves and grass. So you can absolutely meet all your necessary protein requirements by just eating leaves and vegetables. Now, if you wanna have meat, please, please, please get the highest quality grass-fed and grass-finished meats that you can find. And there are actually many sources now on the internet to find them. There's a local source here in Southern California, Primal Plants in Temecula, California. They ship, they're a great bunch of young people and their efforts should be applauded. There are really good sources of wild shellfish, wild mollusks, wild seafood. Please do not be fooled when you see the term organic salmon or organic fish. They didn't follow these salmon around to see if they're eating organically. These are farmed salmon that are fed corn and soybeans that just happen to be organic. And sadly, these fish take those fats and don't make omega-3 fats. They make omega-6 fats, the harmful fats. So please don't be fooled by a restaurant menu. Okay, steak lovers, how much red meat is okay? Well, moderation is the key here. Remember, not only does steak and animal protein produce TMAO, one of these harmful compounds, but sadly steak and lamb and pork also have a sugar molecule that actually causes us to attack our own blood vessels. It's called Nu5GC. The good news is fish and chicken don't carry that molecule, they carry the same molecule that we do. Okay, let's turn to probably the most important factor in longevity, and that's fasting or time-restricted eating. Now, more and more, as you read each one of my books, you're beginning to realize that it's not as much about what you eat, but knowing Wendy that's probably in the long run, even more important. And we actually have to thank Dr. Campo from the NIH, Dr. DeCabo, I apologize, Rafael DeCabo, who really, I think, flipped our attention into thinking that calorie restriction, that is reducing the amount of calories we eat every day to 25, 30% of normal, is actually the key to longevity. What Dr. DeCabo and others realize, Dr. Mattson as well, realize that it's perhaps the timing of when we eat food, not the amount of food that's important. And those of you who've read the energy paradox know that Dr. DeCabo's work showed that if we could reduce the amount of time that mice were allowed to eat the food that they were given, it didn't matter the composition of the food they were eating. It mattered how short a time period they were allowed to eat every 24 hours. And this was recently reproduced in Italian athletes and that study showed that if Italian athletes were given the same amount of food and asked to eat it in a 12 hour window so that they were eating for 12 hours and not eating for 12 hours versus compressing that window to a six to seven hour window so that they were not eating for about 17 to 18 hours, the athletes who compressed their eating window, even though they were eating the exact same amount of food, lost weight, had improved exercise performance and perhaps most excitingly, they dropped their mTOR levels dramatically as Evans by dropping their insulin-like growth factor. Now, one of the unique things about super old people who are thriving is they run very low levels of insulin-like growth factor called IGF-1. And I measure this every three to six months in all my patients. And I can assure you that all my super old patients who are thriving, including a 97 year old gentleman who drove from L.A. to my office in Palm Springs this week to see me, his insulin-like growth factor sits at 48. He's bright-eyed and bushy tailed. He runs his company and he's 97 years old and he drove to see me. One of the keys is keeping your insulin-like growth factor low. Now, why is that important? Well, insulin-like growth factor, growth factor makes things grow. And sadly, there's very strong evidence that people who have elevated growth factors have much higher rates of cancer and live much shorter lives. Conversely, it's incredibly rare to ever see anyone with a low insulin-like growth factor develop cancer because there's nothing there to stimulate growth. So, fasting, time-restricted eating is one of the most powerful tools all of us have at our disposal to improve our immediate health, our immediate health span, how long we're going to remain healthy and our lifespan. In fact, extending Dr. DeCabo's work is that if we compressed our eating window, we would actually have 10 good years of life even if we ate the exact same number of calories that we do now, just compressing that eating window. And you're gonna learn more about that in the upcoming book, Unlocking the Keto Code. And I'm gonna give you some even easier tricks than we're in the energy paradox to pull that off. Now, a lot of people wanna know, well, what the heck do I do when I'm not eating? I know I'm going to get hungry. Well, as most of you know, during the winter from January through June, I don't eat breakfast and lunch. And I eat all my calories in a two-hour window from six to eight o'clock at night. So at 22 out of 24 hours, I'm fasting. Now, quite frankly, in writing Unlocking the Keto Code, I became so impressed with the research that is ongoing that now, actually starting about a month ago, I reverted back to only eating one meal a day even during the fall now. So it'll be about nine months a year that I'll be eating one meal a day rather than the six months a year because the evidence is so fascinatingly strong that this may be the one tool at our disposal to maximize our lifespan and L-span, the one tool.  And if you're really looking for something as doable, a six-hour window is really great and work by Dr. Massen from Johns Hopkins and Dr. DeCabo suggests that a six-hour eating window may be your maximum spot. So what do you do when you get hungry?  So there's lots of great prebiotic fiber out there. I make a supplement, prebiothrive, that is eight different prebiotic fibers. And so if you're hungry, just have a glass of prebiotic fiber and you'll be in good shape. Don't want to use mine, grind up some flax seeds, grind up some psyllium seeds, get some and just mix that up. You'll do great with that. Now, who is fasting, say, for? The only people I really don't recommend intermittent fasting to is women who want to get pregnant and women who are currently pregnant and women who are breastfeeding because you really want to have calories for your child. And I've seen over and over again that women who restrict their calories or change their eating patterns, your sensors in your body think that there's a famine. And the last thing you would want to do is waste an egg when there's a famine going on. And I have a number of very thin women, many of them athletes who want to get pregnant and we increase their eating window, we increase their calories and lo and behold, a number of them are actually got pregnant and delivered successfully.  Okay, now there are non-diet related factors that also characterize the blue zones. And these are lifestyle factors. One of the unique things about the blue zones in general is that they all live in hilly communities. And Loma Linda actually means beautiful hill. These people walk up and down hills. They walk against gravity all their lives. And just two weeks ago, I posted on Instagram, my wife and I visited Capri, the island off the coast of Naples, which is really hilly. And I was so impressed to see the number of people walking these hilly hills up and down the steps. There's one walk we did that has over 1,100 steps. And if you saw it on Instagram, I posted a gentleman, an elderly gentleman who walked, we were coming down the steps, walked past us. And I stopped and it was so amazing because it wasn't even huffing and puffing. And I can tell you it was steep. I stopped and turned around and he realized I was taking a picture of him and he waved at me. And this is the sort of thing that these people do all the time. When I was in Acciaroli two years ago, sheep herders, goat herders are up and down these hilly hills around the community. The same thing with the Sardinians, the same thing with the Okinawans. These are hilly communities. So the more you walk hills, the better off you're gonna be. The other thing that these people do is they garden. They work the fields. And gardening is a great exercise. Most of us don't like housework, but believe it or not, housework is great exercise. None of these people ever went to a gym. None of these people had machines in their house. These people worked against gravity. And I think that's one of the best examples of longevity I can give you. The other thing these people do is they're primarily farmers. And they wake and go to sleep with the sun. They follow their animals. One of the things I've learned having lots of dogs is that dogs work with the sun. And when the sun rises, my dogs, our dogs are in our faces going, let's go. When the sun is going down, the dogs look at you and say, hey, it's time to go to bed. And that's what these communities do. They work with the cycles of light. And getting the proper exposure to dawn sunlight and dusk sunlight as they talk about in Unlocking the Keto Code may be one of the hidden secrets to these long-lived societies. The other thing that they're not exposed to is blue light. We are constantly bombarded with blue light from our phones, from our computers, from our TVs, from the lights in our rooms, all the LED, all the fluorescent light. Blue light is one of the most damaging things to our eyes, to our brain that anyone's ever discovered. The other thing that these communities have is an incredible tight-knit social network. And I think the thing that impressed me most about the Adventist was that this tight social network coming together every Sabbath to meet having support groups. And interestingly, in these elder-based communities, elders are sanctified. They're held in incredibly high esteem. And so many of the elderly people I meet in these communities, they tell me that they know that they have to stay alive to teach younger generations the secrets. And they feel devoted to their community and they feel devoted to staying healthy and active and participating with the younger members of the community. And I can assure you that these people are not shuttled off to assisted living and nursing homes. They're multi-generational families, either living in the same household or living right next door to each other. And I think it's really one of the lost arts of longevity that perhaps we need to rediscover. So having a purpose in life, having a purpose to help your community, having a deep social network is the other big defining part of these blue zones. Okay, that's a lot of information, but I wanna get some of your most pressing questions about blue zones. The questions I'll be answering today come straight from Instagram. Okay, the first three questions are all anonymous. Number one, what surprised you most during your time in Loma Linda? How have you changed your lifestyle since living in one of the blue zones? Well, I think the sense of community, like I just mentioned, was one of the most striking things about living in a blue zone. The other thing that really surprised me is the amount of walking that was done in Loma Linda and the neighboring town Redlands where I live. And I actually took up hiking and running when I lived in Loma Linda, because I was so impressed with what people did. The other thing that shocked me, really shocked me, was the amount of dairy products, particularly cheese, that the people in Loma Linda ate. It actually, when I met with the nutrition group in our hospital, it just blew me away with how much cheese they at Venice eat. And you're gonna see why I think that's so important in the upcoming book. Second, many people living in the blue zones don't rely on taking supplements. Why is it that most people outside of the blue zone should take them? Well, there's a lot of really good reasons. First of all, these people don't live in depleted soil communities. Our soil is barren. It's been destroyed with pesticides, herbicides. There is no top soil in the United States. And our food has like 70% less than the vitamins and minerals than our corresponding food had 50 years ago. They don't have that problem. Their soil is living. And so all those important vitamins and micronutrients are present in the food that they eat. Plus, these communities have not been exposed to glyphosate. And these, which absolutely destroys the microbiome and destroys our ability to use nutrients. That's one of the exciting things when I go to visit these places. The other things that these communities do is they have a wide range of foods that they eat on a rotating basis. Now, most people in this country eat a very few forms of food. And a ton of our food, whether we know it or not, is derived from corn and wheat. And our corn is mostly genetically modified and our corn and our wheat is sprayed with Roundup. So we have absolutely no way of getting the vital vitamins and nutrients that these blue zones get on a routine basis. And that's why, at least for us in the West, supplementation makes so much sense and is actually so much needed compared to the blue zones. What are your thoughts on cultivating or growing a blue zone? Well, it turns out the blue zones as trademark, Adventist Health, have partnered with RPC legacies, hotel and residencies to begin construction of a flagship well-being and medical facility in Miami, Florida. And I really commend them on this. I think this is really an exciting thing to try. Recently, I've been approached to have a community in the Northwest partner to have a Gundry blue zone in that city. And we're just in the initial talks, but who knows? Very soon you might visit a Gundry community where this is going to take place. Okay, we'll have a lot of other questions on a next time we're gonna do this. They're really good questions, but I gotta wrap up for today. So thank you for sending those in to me. And like I say, we'll get to them as soon as we can. So let's move on to the review of the week. This review comes from Free Mandela. I was suffering from asthma for years. In the last four years were not easy. I tried to eliminate gluten, lactoceram. I was using my Hoover all the time, sleeping with special bed sheets. I did not try to sleep without them yet. 45 days of electing free diet and my asthma is gone. I don't even need to take my inhaler shots anymore. Modern classic medicine is always saying asthma cannot be healed. Well, now we have the evidence to say that this is not true. Dr. Gundry, I don't even know how to thank you. You are one of the very few people who has helped me the most in my life without a doubt. Well, thank you, Free Mandela. Unfortunately, we've been sold a bill of goods and our health is in our hands and it's in, quite frankly, the food we put in our mouth. And just this week on Instagram, I posted a picture with me and Adam, who came running across the parking lot in Palm Springs. He's a pipe fitter working on one of the buildings in my complex and check it out. Adam had such soreness in his hands that he couldn't work and he adopted the plant paradox three years ago. He and his wife and he says, oh my gosh, how do I thank you? He's working full time, take a look at him. He's radiant health and this is why I show up to work every day and this is why I do this because your health is in your hands and I'm here hopefully to guide you in making choices that you can live with literally and figuratively. So that's all for today. Thank you, Free Mandela and I'm Dr. Gundry and I'm always looking out for you. We'll see you next week. Before you go, I just wanted to remind you that you can find the show on iTunes, Google Play, Stitcher or wherever you get your podcasts because I'm Dr. Gundry and I'm always looking out for you.


How's everybody doing welcome back to my channel this week I'm gonna be doing one of my priority designs that I posted on my website and I am excited I am so happy. I'm ecstatic because I've been waiting for someone to book this design. So with that being said Let's get this day started. Let's go. So this is the project that I'm gonna be doing this week It has color and it has a whole bunch of detail and I'm gonna be using today the revolution ink by Nick Hortado Definitely want to give them a try that look very Thick pigment which does something. I really like I'm excited.  So I'm excited and I cannot wait to get this started. This is your first tattoo. Yes. I'm weak No, it's good, it's good. I just I didn't know I thought you had it more I'm glad you're starting off with a good piece. Oh really also you drew it from California.  I'm stationed at 29 Yo, you're a cop, bro. It's my arm chill.  They say this is the best part of the tattoo and then everything else. Yeah, that's our facts right there Everything's down here after this Nice What happened so you'd edit my toes out if I didn't have socks. Oh, probably not a focus on that So mean look at that. What is this? Not much. I think it's very what's that where I'm looking for a very Kenny, how does it support our support? How do you say so portable in English? Supportable So what is it manageable is manageable. Yeah, is that a word? Okay good Manageable I was trying to I was about to say it's very affordable. That's just makes no sense. It makes no sense Yeah, yeah, yeah, I've been making up words sometimes like it's my favorite thing So we have my client here. It turns out that it is his first tattoo and which is insane to me He just came in. I didn't know it was his first tattoo So that's gonna be super dope that turns this into a whole different experience because I thought you had tattoos But you don't so this is gonna be a two-day project day one We're gonna be doing the astronaut here with the score a whole bunch of color a whole bunch of details second day I do have already a designed already But I definitely want to see how everything goes and how everything's placed today That way I can figure out where I'm gonna put the planet just because he has a huge muscle here on the thigh And that can definitely affect the weight He's just it's just the muscle does there just skip you shouldn't just skip leg day until you got a tattoo, bro but The thing about this muscle is that it can definitely affect the shape of any circular shape or any square Because once you put it there, it's gonna seem like it's not straight or it's not perfectly Circle so definitely we got to move things around to make sure that everything looks perfect. So yeah, you ready? Nervous excited scared a little nervous. Yeah, I ain't scared. I booked it for a reason my dude One thing I do want to do with this area of the skull is I first want to apply my solid black before I even put Any color and the reason why it is because I want to see how dark I can make the skull look before looking way too dark So first I'm gonna do all my contrasts on on the inside here on this area this area Anything wherever I see that is solid black. I'm gonna apply it But I'm gonna fade it out with my round liner Which I'm gonna be using my 14 round liner with a voltage of a 5.0 So as in right now, I'm just applying my brown here and I really like this color because it doesn't look like Burned brown, you know what I mean? It just looks more like in the reddish kind of side and which I really really like And I'm gonna slowly just do that my scribble technique where I just do here and there, you know textures and Map it out because I definitely want to layer it with my orange. Definitely like the way this is Looking on skin So as you can see, I'm slowly transitioning into a Lighter brown. I just dipped it in my yellow That way I can get like a brighter orange So as you can see now my yellow starting to show a little bit more Which I really really like Want to make this a little bit darker. So I'm just gonna layer it I am running my machine of 5.0 voltage with my 14 round liner With a low voltage like this a I can definitely take my time Really look over everything that I'm doing instead of running it at 10 And because if I was running it at 10 with my style, I wouldn't be able to do it Just because it is way too fast for my hand speed and that is something that as an artist you have to figure out Sooner than later because knowing your hand speed and being connected to your voltage It's the key to everything, you know, you're gonna be able to do a lot more and it's kind of hard to say how To find That with you know, it's all practice and experience. I wish it was a like a shortcut to it It's just trying new things trying new things is one that is gonna help you figure out faster What you're capable of and Once you find it explore that and keep going at it until you get really good at it Then after that sky's the limit As I get closer here, I'm gonna mix my brown with my black Dip it once just enough to make it a little bit darker. There you go. See that and Yeah, that's a really really like the way that turned out right there. So I'm gonna do it one more time. Oh There is a highlight around this area, so I'm gonna leave that open too All right when with this I'm gonna continue doing the same thing across the whole entire school It's just layering going back and forth until I get the tone that I really like Yeah, exactly and then I'm a branch it out. Yeah to the top you came here to get tatted now You but your handling is super good though. You're good You'll be able to take it tomorrow. What is it because I've just been like Do what you got to do my guy. Just have your breathing just Yep in the background a whole separate YouTube video Just a video my clients breathing What do you expect on your first? What is it?  I'm like, bro I don't want this and the thing is that if I watch it for half a second. I get nothing but that Yeah, I'm like, you gotta scroll quick and you gotta scroll quick like you cannot think about it How has been your experience so far today? Oh Down here with a breeze. Yeah, and then up here not a breeze.  Yeah, the shade here. Okay, it's starting to hurt a little bit more I can see it. Yeah in the school and the colors. Oh, yeah, you're like I this is it. This is not good But you handle it really good though, you're chilling Now you're very for the second day Not ready for more tomorrow very for more tomorrow bigger area and And the back of the knee in the back of the knee All right, this this line right here. There's two lines that I'm about to do they cook They're gonna be a little painful. All right, all you got to do is just Relax gonna be long I'm not too long Long enough No That was the truth That was the truth. It was the truth All right second line coming.  I was like, I didn't really know what I was getting myself into No, I'm like, yeah, that's just gonna hurt bad But it's okay, but it's okay. How'd you sleep? I think I woke up at like four took me a little while to fall asleep And I don't think I moved around very much either So and you cleaned it up really good though. Yeah, it wasn't bleeding at all. There's no plasma Nothing That's like a bump That's like a bump What is that what The original idea was to put the planet here on the bottom and then have the meteors on the top But instead I'm gonna switch that around because if I was to put that planet right here this This area here is gonna make the the planet look like it's not a circle anymore So you definitely don't want that and it's all about placement, you know So that is why I'm I ended up switching it up. Let me see. Yep. That's the one perfect Dallemambo now we got the meteors down here.  All right, relax turn towards turn. Yeah, there you go. Perfect. Thank you.  Honestly, I'm looking forward to that meteor right there That's just gonna it's the beginning of the right on the knee and then like So we already got the stencil on What I did I ended up placing the meteors here on the bottom The meteor is gonna move with the body and it's a great placement Which I really really like you got to think about those things because if you place something With the shape or with the face or something like a portrait on this area once they sit They is gonna change the features of everything, you know So you got to think about what to place on this area So whenever they say or they stand up they lay down they do any activity This area is gonna still gonna look amazing. So that's the reason why I ended up putting it here And the colors that I'm gonna be putting on this piece is same colors as the skull to make a match We have the orange. We have the yellow. We have the the bright white highlights and making sure that it stands out like fire. I Hope I'm not scaring you with this explaining this What else are you gonna do and lastly?   They put the next two days I could I would be destroyed. I think your leg will fall off Damn, how do you feel bro? Crazy did you think that you were gonna make it through? Yeah.  Where's my where's my cartridge right here?  Oh my bad. I know. Yeah, that's that's burning That's why I left it at the end my guy That way you had no choice, but to take it because it is the last five minutes motivation So the 18 hours of you taking ink. This is the first time you make a noise Like a real noise. Yeah That one was that one was sharp. Yeah, I want a sharp little spicy It's a wrap it's a wrap that's it


Welcome to these case studies in clinical microbiology. Your course in clinical microbiology will encompass a study of the microbiological characteristics of infectious agents. The disease of infections they cause and the laboratory diagnosis of these infections taking relevant specimens to the laboratory for investigation. The course will also encompass the treatments of these infections. And most importantly, the control and or prevention of these infections. These case studies in clinical microbiology will be an adjunct to the lecture notes you will obtain in the didactic lectures. You can use them in one of two ways. You can have a read at these case study notes before the lectures so you'll be able to ask relevant clinical-based questions in the lecture. Or after lecture, when you have understood these, you then go back to these case studies and read them, compare them to what was presented to you theoretically in class. It is hoped that these case study notes will bridge your theoretical knowledge in class and your clinical practice. We hope you make very good use of the case study. Thank you.


Welcome to Agile Roots 2010, sponsored by version one, Rally Software, Virio, Amirisys, Agile Alliance, and Xmission Internet. Before we begin, who here is a developer? Okay, who's here? Who's a tester here? Or fills in as a tester role? Um, product managers? Okay, UI guys? None. Not surprised. Um, more or less, you know, this makes up the makeup of a team. You have stakeholders, you have designed people, you have testers, and there's other roles, but more or less this is kind of the makeup of a team. And, uh, cucumber, well, acceptance testing I think in general, offers, um, offers a way to address challenges based by teams, um, challenges that are joint and also specific to a specific role. The versus requirements. Now, Judd Patton, um, brought up one of these, brought this recording as keynote, and that was at the chaos report, right? Um, this is an older report, but fifty, fifty-six percent of all bugs are introduced in requirements. And the flip side to that is also that 45% of functionality is never used. And so all that effort you get put into the software is, it's never used. It's like the weights that you buy and put in your home and you never really use it, right? It's, um, and when you do use it, you only use about 20% of it. Now, I'd only admit that, um, you know, Jeff kind of alluded to this in his talk, that this report is fine, it might be somewhat dubious, but I think it, um, the reason I bring it up is I think everyone who's been involved in software can relate to this. I think everyone who's been on a team has seen feature devotion within their projects. Um, the idea that we get so wrapped up in creating feature after feature would forget the actual outcome that we actually want and that's to make our users happy. So, in Agile, we're very familiar with this card, it's a user story, and I won't go into the details of it because this is an Agile Roots conference and I'm guessing everyone knows how you use these. What I'm going to say is how Cucumber picks up on this. You have a story like this and to make this into a Cucumber feature, you take that card and you drop it into a plain text file and you give it a name and that's the beginning of your Cucumber feature. Now, um, Cucumber won't actually execute any of this part. This is purely for documentation reasons. Um, what Cucumber will automate is the acceptance criteria that follows this and the acceptance criteria I view as essentially the conversation that comes from the user story. Um, so you have this user story, you have a conversation about it and what you do with Cucumber then is you record that conversation and you record that in a language called Gherkin. Gherkin is a type of Cucumber and it's a natural somewhat artificially structured language to record requirements. It looks something like this. You have a scenario, um, you have a given some context, when some action, then some expected outcome. And the nice thing about these scenarios, I think, is that they're just fairly sufficient for what you need to describe the needed functionality. Um, in addition to these, you can also have injunctions and disjunctions and they all do the same thing under the hood. Um, what's really important is the words that follow those keywords. Um, so if we take a scenario from our previous user story about, you know, as an inpatient buyer searching for stuff, we might get a scenario like this. And the thing I love about scenarios is you don't have to explain to someone what a scenario is, you just say, give me a scenario and they'll give you more or less something along these lines. Um, and so you could, you start with a scenario like this, you move on to another one where the context is different, because the context is different, you have a different outcome. So this is kind of 101, uh, gherkin language. Now there's some advanced stuff as well. Um, one thing that I think, the key coverage is really well is it encourages this workflow mentality. Um, this is how designers think, this is how most people think when they think about software. Um, and it, I mean James, you can make me dispute this, but for my understanding was it wasn't really geared towards that, it was geared toward more towards the, the domain model. Does that mean more or less the case? Versus, versus workflow? Workflow. It had support for both, but it was better at doing domain model. Okay. And one of the things that did really well though is, is tables. And so we've taken that idea and also rolled it into a cucumber. And so there's a number of different kinds of tables. The first kind is a step table where you essentially only be explicit upon the data that a step gets, for example. So here we're providing, instead of just saying we have moved it by Steven Spielberg, we're explicitly listing every data that's in the system at this time. And you can use these tables in a number of ways. Um, with this example, I'm saying I should see this table on the Ui, on the Ui. And you know, to prevent the curriculum that you can actually constrain this, so it only checks those cells and doesn't, you know, blow up if more cells are actually added. Um, the other kind of, um, table addresses the issue where you have a, you have a certain scenario and you have, um, essentially variables that you want to change. You know, what happens if you type in Steve? What if you type in Bird? What will happen? To address that, we have scenario outlines where you, um, replace those, uh, those strings with these variables. And so what it does is it loops over each one of these rows in the table and executes that scenario. And from the programmer standpoint, you don't have to do anything different. Um, as long as you write these original steps, then it works under the hood. Um, another notion is the background. Oftentimes you'll have scenarios that have the same context. And to get around that duplication, you can promote that up into a background clause. In general, you want to keep these to be context and not any action-specific steps. Um, the one final thing, kind of a side note is you can also do multi-line steps. So in the case of, like an email, for example, you want to make sure it's being personalized exactly. You can easily do that, um, with, um, multi-line steps. And we're using, like, the, the Python lock stream type notation there. Um, and also the side note, um, since it is supposed to be for, um, customers, these features can be written in over, like, 30 different languages. Um, so there's no, really, there's no filing there as far as communication. So congratulations, you're all now Perkin certified. Um, and I'll be selling these for $500 after the call. Um, that would probably sign a T for you. Um, so what now? I mean, what does that, doesn't really give you much, right? So I'd like to explain now the process that I've used, um, with my, with teams of using Kube Company. Now, this isn't a hypothesizing, copium world. This is actually what I've done. Um, let's start out with a user story. We're using, we have a little tracker, um, to store our, our backlog. And so we pull a, a story off the stack and we take it to the whiteboard. And that usually involves the designer and the, um, myself and the product owner. And we talk about what those requirements are. I then typically, um, transcribe that conversation to Perkin. And then I go back. And this is, going back is probably the most important part, because I say, this is why I understood what was the requirements. Am I right? And more often than not, I'm, I'm wrong. And more often than not, I've included functionality that doesn't need to exist. And so this back and forth is really example. And that's also where the scenario outlines are really helpful. Because you can just go line by line in the, by example, in each row and get a lot of mileage. After that, we begin the outside in development process that we follow with Cucumber. And so now I'm going to stop there and go into how do you really automate this Perkin? You have these plain text files, but how do you make them run? And it, um, first off, every project with Cucumber has a features directory. In that features directory are the plain text feature files also with the support directory. In the support directory, you have an environment file, which is akin to a test helper. It boosts your actual environment. There's everything you need to do to get that, your application up and running to be tested. Then you have the step definitions. This is where the rubber meets the road. And you have to actually make those plain text lines executable. And they look, so you have a step, a step definition would look like this. You'll see here we're using regular expressions. So we're essentially training regular expressions into method and vocation. And for the variables, you define them with regular expression capture groups. And those are then yielded to your method to be executable. And now inside the step definition, you can use whatever you want, whether it's web graph, you're in the Ruby land or web drive or water, HTML unit, J unit, anything. So Cucumber is not specific to any language or framework. Because as you see, this is obviously in Ruby, but we can address, we can actually test a lot more applications. So let me just curious, who here is a Java developer? Okay, we have a few. Okay, Cshar. Okay, wow. I signed in most of my talk to Java. I probably should have done this instead. So there's a number of ways you can use Cucumber to test applications. Now if you're using something like Selenium or water, you can obviously apply that to any application. Likewise, there's libraries for testing swing applications in Ruby. So that's one way. The other way is to use what's called Cucumber's Wire Pro call. And we actually have that for .NET and it allows you to write your step definitions in .NET. And Cshar, sorry, I hope it doesn't really offend anyone. I did use Cshar back in 1.0. Apparently we had lambdas now, I found out. So this is how you do it. Now this uses the Wire Pro call, which means it's sending over some JSON responses. I've never used it. My feeling is it might be a little, not as pleasant to work with as the native Ruby version when you're using Ruby code. So thinking around that, there's other tools. I don't know if it works with Iron Ruby. It does. It does, but I haven't heard great performance reports on that project. That's certainly inherent to it. Yeah. So gyrkin, the language itself, it's not tied to Cucumber. We have these parts that are written in a raggle. We define this as a finite state machine. It compiles down to a number of languages. And because of that, certain frameworks, specifically spec flow, have picked up on that. And this is a BDD framework written in C-sharp that uses the gyrkin language. So if you know gyrkin, you can just pick up this tool and it will integrate it nicely in Visual Studio. And I imagine it's probably a very nice experience as far as debugging and that sort of stuff goes. Kind of the third rally is through something like Iron Ruby, but JRuby. JRuby is actually very mature. It's kind of being the fastest Ruby implementation currently, if you exclude the one in mind versions. So it's very fast, and because of that you can use it to test any post-language on the JVM. I'm currently doing a closure project, and it's actually working quite well with it. And to give you an idea, this is how you translate those Ruby steps into the various languages. So it's more or less the same thing. It's your keywords and regular expressions. The job you have to use is allocations. What if the job is over rows? It's not that bad. There's only one more line, right? Double the lines. On a serious note, if you are doing, unless you're really investing in Java, using something like Ruby or Ruby, the integration is so tightly within Java there's not a whole lot of effort in having your acceptance testing compiled. So you might be thinking, this is a lot more work for me. I have to now write these step definitions instead of just getting down to work. That's true, but there is some overhead. I won't lie, but I think that overhead is paid dividends. And going back to the talk about requirements, I don't often take a story like this and show my business, state analyst or whatever, and say, does this look okay? And they'll say, no, you don't need to do this, you don't need to do this. And so off the bat, you save a lot of time not worrying about edge cases or functionality that doesn't really need to exist. And so you're only focused on writing the software that matters. Additionally, you also know where to begin and where to end. When that queue comes in turns green, you're done. Likewise, when it turns red, you broke something and you have to fix it. So it provides a safety net. And kind of going back to this whole theme of this conference of building great software, it turns out that thinking about software from a user's point of view turns out to be a good thing. And as developers, at least speaking for myself, it's really easy for me to think they get lost in the code and the inner workings and forget about the user experience. But when I'm focused on writing requirements in English at the higher level, and I'm really actually going to interact with it, I find that I produce much better software. And so to produce a software, we use something called the outside-in process. Now, traditionally, we'll often start with the database schema initially. Work up to the models, go to controllers, view what you're doing like a view of your web app, and eventually you'll do the UX. Well, outside-in puts this around and goes from the very outside and works inward. And so the feel of how this works is you start out, actually, I'll back up a bit. I like to describe this outside-in process as kind of bite gear. You have cube gears, the outer gear being cube cumbers.  So cube cumbers will tell you you need to write step definitions. And when you do that, cube cumbers will go red and say, you're failing, you need to go write the code to make this pass.  And the reason why you do that is, if you're operating on doing end-to-end tests with cube cumbers, you're going to get zero design benefit. In fact, you'll actually carry design if all you do is end-to-end testing. So you really need to fine-tune the innards with traditional PDD, regular factor. But once you're done with that and you're green on that level, you can actually take it up and see where you're at. And typically, you're at another pending step. And so then you repeat that process until you're green all around.  So that's the kind of typical process. So I have an example of this. And these slides were taken from Azak Helisoy's slides, who was the creator of P-Cumber. And I saw these slides from him because he had some job examples. Because for some reason, I thought that everyone in the room was going to be a job programmer. I could skip them if you'd like. But it's still probably going to give you an idea of how it would work. So you start with this feature. This is a teach feature for the mastermind game. And I also should point out, when you're using Java or any compiled language, the step definitions can't live in the features directory. They have to live in the test directory. Now, typically, when you're installing Qtumber, you would just say Gemisoft Qtumber. But in Java land, you'll probably want to use Maven. Or if you're using Ant, you can do that as well. But Maven, I use Maven, and it's pretty easy. You use some XML pushups, and you're there. It uses Tico container for the dependency injection. You can also use Jiz or Spring if you're already using those. And what happens is, when you first run, it poked into the integration test task, when you run it the first time, you set the property to install gemstru, that will automatically install JRuby, Qtumber, and all the dependencies you need to run. And it will run it, and you'll see something like this. A couple of things to point out is, on the far right, you'll see that we have a stack trace. We know exactly where these steps are lining up to for this feature. And so what it's saying is, you need to go write these features. It actually does more than that. It doesn't say you need to write them. It actually writes them for you. It doesn't write everything, but actually it gives you some pending step definitions. And so if you're not too friendly with regular expressions, you'll be okay to get started because it fills in the gaps.  You have to implement the step. So you go down and, well, if you look at it, if you look here, there's a location. So you go to that location and you write the step. Again, this is the regular expression being yielded to this function, the secret code is function. So write it. We say our intention is we're going to create this new game object. So, of course, when you run that, it will have a compilation error. So you create the game object, and at that point that step is green, and you move on to the yellow step.  At that point, you add more scenarios which will then break, but then you keep going this process until you have this entire feature delivered. Now, since you're all very concerned about it, you should see the problem of these scenarios is that they're doing the exact same thing. The only thing different is the names of the variables. So you can extract that out into something like this. So if you have a little more tricks about cucumber, that is the tag. I think tags are really one of the best features of cucumber, and I think every testing program could have one. Here's an example of how you might use them. We've tagged this feature as using Lucene. We're saying that we need this dependency to be there for this feature. Additionally, we're tagging them on a workflow basis. This scenario is a way to work in progress. This other one is proposed. It's pending UI or whatever. And we can also tag long-running ones as nightly ones because you're only going to run your acceptance tests all the time. If certain acceptance tests will give you enough confidence to deploy, then certain ones that are long-running, you can kind of delay those executions until night time. And so you can tag things like that in any arbitrary way that you see fit. And then to use it, you can say, don't run everything but the ones tagged, or you could say run everything with the ones tags. And one thing about the whip is cucumber kind of promotes a compound workflow mentality. And so you can limit the number of scenarios in progress or in flow. And you can also say, if this does pass, then blow up because this is a work in progress and I'm expecting failure and not success. And so that whip tag is actually helpful on CI builds so you can prevent false positives. Some other things you should do. Where about hooks? You can hook into the platform if you come before a scenario, after a scenario. The world is really to provide helper methods. Now the hooks, since the customers can't see them, they're really best to put in something like a database like if you're truncating a database, that's what you want to put in these hooks. Something really low level, not something that provides context or a feature. And you can also do tag hooks. So if you're using Selenium or something and you only want to use Selenium on a few features, you can tag it to Selenium and you could then use a hook to switch out the driver for whatever you're using to drive the browser. So one thing I want to touch on really quickly is the notion that acceptance tests have to be end-to-end tests. Now the way I've been talking, I've certainly given that impression and the way cucumbers mostly use is with them being end-to-end. That being said, I don't do that all the time. And there's, I like to get into this with a scale. On one side you have a slow to fast and on the other side you have nicely integrated. Now when you're writing these tests, and actually when you're even writing step definitions, you can pick what level you want to operate on. For example, when you're filling in the context steps, you can just stuff things into the database. Those are going to be under code level. You can go through UI data in. Likewise, there's some other intermediate levels. Before you go full-blown and do the water or whatever, you can use stuff like headless browsers like HTML unit or VA-driven tools that will actually manipulate the DOM that aren't quite as heavy. And so what I technically do is I'll write one scenario that's happy path that goes through the entire stack but then I'll have a whole series of edge cases that will just hit my domain models. Because I know that it's all wired up and hooked up correctly, there's no reason to incur additional cost of having every single edge case going through the whole stack. So that brings us back to testers. Because developers, at least in my mind, should be in the testing process intimately. So what do the testers do at this point? Well, they do what is really important. Well, I think it's ignoring that exploratory testing. And oftentimes, so when we're on path projects, we would always hand off to people to do exploratory testing and they would always find things I missed. And that gets just fed back into the cycle add a new scenario and then I would address that and then we keep doing that until we're done and we have the feature that we needed and hopefully, because we've thought about the user experience from the beginning, we'll get a happy afternoon step in addition to just output. The other event that I see of using a tool like Cucumber is you avoid this problem of dead documentation. Dead documentation I found is not only useful, but it felt to be harmful. And so instead of dead documentation, you have living documentation. You have executable documentation that you know describes how the system is actually working. And really the notion of it being executable ensures that as the system involves, this documentation will evolve as well. So to me that's really a key benefit of Cucumber. A few subtleties I'd like to point out. When you're writing scenarios, it's very easy to, it's more of an art than you would think. For example, we have this scenario that I listed above. This work, this is very high level, it's very declarative. I have these movies, when I search for this, I should see these movies. Now, you could rewrite this same scenario in a very imperative style. I mean, the intention of how the implementation is supposed to be is in line with that scenario. And there are certain trade-offs through these styles. I've worked with certain designers that really like this. They like being able to say, look here, I see this, because otherwise they don't really know how the UI is going to count out. But there's some trade-offs because what you've done is you've shifted all the maintenance to the plain text stories. Whereas before the declarative approach, you will be writing more declarative step definitions. But when you're writing that code, you'll be on the code level and you can have all these instructions to reduce the application. When you're on the plain text level, you're really setting yourself up for some pain in some cases. As an example of that, you take this login example. This login example of itself is fine because you're talking about logging in, and if you want to describe the process, that's fine. But if you add a new scenario, changing the process, and you simply copy and paste that, what you've done is you've really confused what this scenario is about. All of this above is incidental to what this main scenario of changing the password is about. And so what you can do with Cucumber is you can hide that noise and wrap those steps into another step. So the steps can actually call other steps within the step definitions.  You can go, Coup's info is the main page. And you can also, on GitHub is where all the code is, especially the Coup for Nuke and Duke is up there. Anyways, that's it. Do you have any questions? I know I went through that really fast and after a following path presentation, it wasn't too hard to follow. I'm just a little bit not getting how you would take these Cucumber specs that you write and test like a Cocoa app. But at least you have like an iPhone app on there. That's really interesting to me. So like, I don't know, there's something I'm missing.  So as I said, Cucumber is really a thin wrapper and it relies on third-party libraries to drive those things. There's actually a project called iCook, which will, what it does is I think it installs some sort of driver within your iPhone application and you send an HTTP request. Well, yeah, you don't have to worry about this. The library does that. But then, essentially, it will drive it.  So these drivers tell you what's going on. Yeah. So it's i, c, u, k, e. I like Q. Yeah. And really, I mean, those things, I think those are nice, but to a certain extent they're somewhat of a novelty because you're, for the web, the web is slightly different because you're developing your whole UI. There's a lot more ways you can screw up unless you're using something like Wit, perhaps. But with the iPhone, code goes fairly set up, so it's harder to mess up, essentially. And so I think those, slot like iCook may be valuable for a couple scenarios, but I would go, I would do everything through iCook, for sure. Yeah. Mac Ruby runs it as well. Any other questions? Yeah. Has anybody made what seems to be the obvious correlation between link as far as the syntax is concerned? So, I never used the link. I know what it does, but I mean, that's really for data. I mean, you're talking about, I mean, the focus is completely different, but as far as the syntax is concerned, it seems obvious that it's very common. Yeah. Like I said, I don't know. Just having, because you said you can write these in C sharp or whatever, since it's obvious that it would be better to write it in more of a link style. Well, I mean, I don't know C sharp at all, or Mac community at all, so I've never thought about that. It's interesting. If you know who is running that project in C sharp. Yeah. So, well, if you go to specflow, think specflow.org. Yeah. I got a guy by the name of Richard Lawrence runs the Cooper Nuke stuff. But yeah, I don't know if anyone's really explored that at all. I know there is high end in specflow within Visual Studio, so maybe there's some sort of something happening there. Yeah. So, I have a question on when you should use it versus when you shouldn't. You talked a little bit about that. But, you know, a web application example will say, we have a bug, right? I click this form, and then I've seen cucumber specs where it says, you know, I fill out the form, I click go, and I should not see a 500 response in return. I mean, is that an appropriate use for this, or? Yeah. So, especially talking about rails, I mean, that's probably the best level to do it at, like the 500, to really make sure that we are seeing that. I mean, I would say that you have to balance the maintenance cost of these tests with the value you're going to get from them. There's certain times where, you know, adding a certain test on a new one just makes a lot more sense and it's a lot cheaper to do. So, it really is really valuable. It's really context specific. I just said, well, what you've done, what you should do is use cucumber 100% of time. That's what I do. You really need the lower level examples. I don't know if that really, that probably doesn't have to be it. It's one of those hard questions in software. I'm looking for you to say you should not test response codes in cucumber. Well, so I do test response codes, so I can't. Oh, of course. But also, I mean, you can do, like, I should see a successful response or something. But, so I'm actually, right now, I'm giving a, so I'm doing a project, I'm working on it now with a web service, and we decided to use cucumber to test that. I mean, it's in closure, but we're still using Ruby and cucumber to drive it. And we did certainly test response codes because as a consumer of that web service, you really care about whether or not that code is correct or not. And the other thing, I really like how the metaphor of starting with the story and going all the way down through your test driven development, coming all the way back up and kind of cycling up and down, I think that's really helped me understand, you know, where this fits. And I think it's terrific. Yeah, I've worked with some really smart, I'm going to call them hackers, that don't really subscribe to many processes, but when you send down to write one of these things, they really like the kind of the mood that puts them in, not the mood, but the mindset. Because when you sit down, have to write something in English and articulate something, it really changes how you think about things. And it kind of just, yeah. Can you talk again, I kind of missed out on why you're saying you don't use it for testing and what I like response codes. He was saying that. I was saying that. He was saying, go ahead. It's like, I don't know, you start testing for edge cases in it and it's slow and slow overhead. I think those are better tested somewhere else. Well, so we want to argument this. You typically want to keep, for normal scenarios, usually using the web case doesn't care they got 200 response. I mean, that's really incidental. And so you should be saying, you know, when I searched for this movie, I should be at 200 response and I should see this. By virtue that you're seeing the movies you're getting, kind of in furs you're getting at 200. And so, the idea is that you don't want to pollute a scenario with details that aren't really key on what it's trying to accomplish. Well, I guess it depends on what scenario you're actually testing. Exactly. And that's why the web service I'm doing is basically giving this JSON, I should see this JSON and I should get it, you know, 402 or whatever. Because that is something that is relevant. At that high level of detail. Because it is part of the API. Right. And there's actually been several people, like so there's a company, for example, called Chargeify, and they have all of their cucumber features are their documentation for their API. You go on and look at how they use their API and it says, given this, when I send this JSON, their XML, I should see this response. And because it's executable, you're guaranteed that that's how the system works and the burden of updating documentation is then, you know, removed or mitigated. Any other questions? No? Okay. Thank you. Thank you.


So I just saw this the other day and I'm super late to the party because this happened on July 10th but I have to share this with you. I posted this on my Instagram as well. There's a link below this video but it's something that's near dear to my heart. It's something that is a rampant disease. I call this the disease. It's a psychological disease among humans for as long as we have existed and that is something called the tall poppy syndrome, envy, one of the deadly sins where people have a very very difficult time of accepting other people's success. So in this case this individual calls out on Elon Musk for being a billionaire like it's a negative thing. Like it's a big negative thing that he put up his capital all the risk working 80 to 100 hours a week blood sweat and tears. God forbid he earns a return on his hard labor that he has to now share it because this individual doesn't have anything therefore he has to share it.  So basically this I'm going to read it from top to bottom. I think I have an image here. You literally are a billionaire. Literally, it is not ironic in any way.  If you think it's a negative label maybe it's because it means that you are hoarding money and resources from the rest of the world.  So Elon replies. No, it means I created jobs for 50,000 people directly and through parts suppliers and supporting professions 250,000 people so quarter million people indirectly thus supporting half a million families. What have you done? You know there's a Greek saying for every finger that you point at somebody three point back at you and it's always I find it always amusing. It's always there's a repetitive pattern. It's always people who have nothing attacking people that have something and yes like anything in life there are good people and bad people. I always find it funny people think just rich people are evil. How is it just rich people are evil? I call money an amplifier. It's an amplifier of a behavior that's pre-existing in humans.  At the exact same time I've seen money amplify very negative malicious characteristics in human beings. So it doesn't matter if you have money or if you don't you're either a really good person or you're not a good person and that can change that can change as well. Lately there's been a massive increase in people playing the victim card and one of my favorite books is from Victor Frankel Man Search for Meaning. I recommend that you read this at least 10 times. It's that good. In fact I have it on audible on replay. I re-listen to it every quarter so every 90 days. The whole fact is like once you understand that you're not a victim that you understand that you have the power to respond to any stimulus in your life once you understand that it is on you that is the most empowering feeling an individual can have. Because at the end of the day if you read Victor's book he went through Auschwitz he was in a concentration camps.  But the one thing they couldn't get from him is his response to the situation. They wanted him to crack.  I control my reaction to this situation and I'm not going to become what you want me to become.  The haves and the haves not and so I think depending on where you are in your life depending on what you want to do I'd really recommend to audit your life right. It's usually the people usually the people that have time to attack other people don't appreciate time itself because time is the most non-renewable resource you can't renew time and so people who exert energy to attack others right to attack for example Elon Musk to attack I don't know any other human being that's a big red flag right away that you should see.  I'm a firm believer if once you understand that you have the power to do everything that you can in your life that you have the power to master your wealth that you have the power to master your health that you have the power to master your relationship once you understand the onus is on you the responsibilities on you and how you respond to your environment it's a very liberating feeling very liberating because then you can make plans in your life you can make systems in your life you can track your progression and you can quantify and analyze exactly the direction that you're going and so I wanted to make this quick video talking about this I find it funny always people hating on rich people hating on people to have something and it's a growing trend even now with the rise of democratic socialism here in North America which a complete farce you know it's very immoral and unethical to steal people's labor it's simple as that you know my family comes from former Yugoslavia where we were socialist states and we've lived the first hand we've seen it in Venezuela we've seen it in Russia we've seen it well how it was in China and that's why China is prospering right now because they have controlled capitalism it's not it's not you know American capitalism but at least it's capitalism socialism just doesn't work you know you can only raw Peter so much until Peter says fuck you or Peter is broke then there's no more money but there you have it guys listen stop playing the victim hood card stop you know negatively calling out people and exerting energy that could be used on improving yourself if you guys have any questions for me leave a comment below the video and I'll talk to you guys soon peace


Hi, my name is Jabari Evans. I'm assistant professor of race and media at the University of South Carolina. Found that when I started entering my early 30s, I was doing a lot of work with youth, mentorship work, as well as community activism. And that work led me to pursuing grants for my own not-for-profit and really trying to see solutions and helping Black youth utilize their creativity in ways that can change their life trajectories, whether that's financially or just making them better people. Well, I think the greatest thing about what I study is that I get to always put a little bit of me into work that I do. And I think when you study race as a Black person, for me as a Black man, you're able to see not only that your work is impactful to society at large, but I'm able to see how my work is impactful for those who are my friends, who are my family and my own children. Communication has needed this level of diversity and inclusivity since I was an undergrad. And I think when I was an undergrad, I wanted a professor like myself. And so I'm really just trying to be the change that I wanted to see. And I think that's kind of the necessary void that needed to be filled. And so I kind of have fashioned myself into that space.


The flag we fly here at the during the evening parades is unique. It's a replica of the National Incident that would have flown here in 1801. Originally named the Star Spangled Banner. It has 15 stars and 15 stripes. We're authorized to fly the Star Spangled Banner because it gives an authentic experience to the audience here on the Friday evening parades. To be a part of the flag luring team was very honoring and a very humbling experience. When the narrator says please rise as we honor those I've fallen before you, I get chills every time.


Welcome to module three of this course, which is on the topic of modeling of software modeling and what we'll cover in this is a recap of the UML diagram types So this course assumes that you have already knowledge in that so it's really just a Quick recap of what the different options are in particular one thing that we will discuss because it's often skipped is The UML component diagram, which is a really important diagram for example for architecture descriptions So that's why it's important to look at it. It's quite similar to the class diagrams in many ways But we'll dive into that for shorter time then we discuss What is actually a model because again many courses introduced to different diagrams You can draw and you have to draw a class diagram. You have to do different things But on a theoretical level it might be important to actually discuss what the model is what it should be and especially also what is in other areas of software engineering, but also other disciplines then we get into the context of diagrams Versus models, so what is actually the difference between having a diagram and what is the model Next up we will discuss the purpose of modeling like why should you do this? Again, there are many courses that Tell you to do it, but as very little reflection on what is actually useful. What is the purpose of it? Why should you do it? When should you do it and we go then a bit more into depth on When to model and when to skip Because this course is on software engineering it has a lot to do with managing software products with achieving the right quality and It's really really important There is no clear answer and you need to understand when this comes in handy and otherwise you should skip it You should not just blindly follow the idea of always do this or always do that Everything depends on the context. So these are things we'll cover and Next up we go a bit into the different UML diagram types just a very quick run through what we have