for personal use and therefore we're not going to put it into some type of expense but instead into the draws. So the owner took money out of the business for personal use shouldn't be decreasing net income then it should just be taken out of the equity section. So we're going to go ahead and decrease or increase dark draws decreasing equity and note that's a little bit confusing for us to first wrap our head around what is a draw and how does it affect the equity section. So the equity section has a credit balance. You can think that draws are kind of like a contra equity account meaning they're going to be an equity account with a debit balance which is contra to the norm or the winning accounts in the equity section which are credit balances and that's because it will bring down total draws. So it acts like an expense in terms of total equity in that it goes up in the debit direction brings down the total equity balance but it's not part of the income statement it's not something that's going to be calculated in the calculation of revenue minus expenses. It will be decreasing however total equity. So let's go ahead and record that it's going to increase in the debit direction. So we're going to copy the draws we're going to put that on top in v 15 right click and paste 1 2 3 we're going to go ahead and post that out now we're going to post the draws first so in order to do that we're first going to freeze the pains scrolling up putting our cursor in a J1 we are in a J1 then we're going to go to the view tab up top we're going to go to the windows group within the windows group we're selecting the freeze pains and the freeze pains then we're going to go to draws draws is going to be our first light blue or equity accounts in order assets liability and then equity then we'll scroll to the right until we find that equity account here are the asset accounts here are the liability accounts and orange here are the equity accounts we're looking for the equity account of draws there it is we want to be in cell BG 15 BG 15 we're going to select equals within BG 15 and point to that $100 which should bring this balance up from zero by 100 to 100 that same 100 then should be on the trial balance scrolling all the way back to the trial balance to see if that is indeed the case there it is now note that that is decreasing equity because if we take the total equity this is going to be a debit that's a credit and if I highlight all of that that's all equity and it has a credit balance of 158 47 therefore that debit is increasing that total balance however it's not part of the net income calculation here next component will be the checking account there's our checking account here here's our checking account there we're bringing it down we're going to find that checking account on the general ledger here's the general ledger we want to be down here in an 18 an 18 an 18 we're going to select equals and then point to that $100 that will bring the balance down from 99 117 down by 102 99 17 that balanced and also found here 99 17 and we should be back and balance down there looks good next item now we're going to record the service charges that was a $15 service charge the bank just took out of our account we're going to say okay we're going to have to record that on our side when I get that back so we're going to say it's 228 the checking account here is going to be going down that's a debit we're going to make it go down doing the opposite thing to it a credit so we'll copy that we're going to put that on the bottom right click and paste 123 going to go ahead and indent that go into the home tab alignment increase the indentation we will have the dollar amount the dollar amount is $20 it's $20 for the bank service charge and then we're going to debit something for that same amount at the $20 of the bank service charge and what will that debit be it's going to be some type of expense I typically like to put it into an expense called bank service charge although the amount is small at $20 and some companies might put it into some other account such as miscellaneous or some other grouping that's going to be on the decision of the bookkeeper we note that all the expense accounts are debit balance accounts they only go up in the debit direction and therefore we will increase the debit balance expense account with another debit so we're going to copy the bank service charge we're going to put that on the top of our journal entry in v 18 right click and paste 123 here is our amount here on the journal entry we need to now post that to the general ledger here's where the account is on the trial balance it's going to be in the same order on the general ledger let's locate that now we have the assets first on the general ledger then we have the liabilities and then we have the equity we're looking for the bank service charges I believe they're on the bottom they're down here in bk 39 bk 39 what we're going to do is select equals scroll up just a bit and point to that $20 let's do that now we are in bk 39 we're selecting equals we're scrolling up just a bit and pointing to that $20 enter there's the 20 there's the balance of 20 that should


The most important I consider is any sudden change in the behavior of the child you notice, that he is now behaving differently what you are used to it and a same feedback can come from the school or the class teacher, the child is now behaving very differently as compared to earlier. Irritability, but the child is getting very angry or irritable, not cooperating with the normal routines which he used to do. And then crying spells, excessive crying spells, stubbornness, refusal to eat food, not sleeping properly, not mixing with the peer group or the kids who wants to go to play and mostly sulking, throwing tantrums.


Okay, I guess we can start quickly. So this is the coupling Drupal modules into PHP libraries, a commerce to the text primer. My name is Bon Jovanovich, I'm Bon Zee on Drupal.org, and I'm the Commerce Development Lead at Commerce Guys, which basically means that I work full-time on commerce to the text, our rewrite targeting Drupal 8. Commerce Guys is the company behind Drupal Commerce and Platform.sh. We have offices in Paris and Arbor, Michigan, and London. We also have a booth in the exhibition area, so come by, have a chat, look at the platform demo, or let's just talk to Commerce if you want. So we built Drupal Commerce from scratch on the then-new Drupal 7, making use of its new technologies. We used Entity API for the data model, we used views for our listings, and rules for our business logic. And by doing that, we created a system that was immediately familiar to Drupal users and developers. If you knew Drupal, then you already knew Commerce. Commerce aims to be minimal, making minimum assumptions, so it allows you to take the parts that you need, change what you don't like, and simply build your project. And three and a half years later, we now have over 56,000 report installations, which is a current record for e-commerce and Drupal in general, powering many important sites from Olaj to Ryan's RealMilkCheese.com. And he's not here to appreciate that joke. So in the past three and a half years, the world around us changed completely. PHP 5.3 happened, Composer happened, Symphony 2 happened, and Drupal 8 is happening. And if we want to repeat our earlier success, that means starting from scratch and re-evaluating everything while still keeping our old values. And doing that actually gives us an opportunity to re-evaluate our problem space. You will notice that there's no such thing as the e-commerce problem, just like there's no such thing as the content management problem. Instead, it's a collection of connected problems each with its own complexities and its own tradeoffs. And when you look at it, taxes or addressing or payments, these things are not really tied to Drupal. And if they're not tied to Drupal, maybe they don't need to be done inside Drupal at all. Maybe we can do it outside of Drupal and by doing that, get additional people on board. So that's what we decided to do. We decided that instead of starting by writing Drupal code for commerce to the text, we would start by writing libraries. Then commerce to the text would depend on these libraries and pull them in via Composer. And that's it. By doing that, we gain additional exposure, we open ourselves to non-Drupal communities, and we validate our expertise. CommerceGuys.io.pl was the first library that we created. We needed a source of currency information that was kept out of up-to-date because we hard-coded the currency list in commerce1.exe, so it kept getting outdated every few months. We found an up-to-date source of that information in CLDR. So CLDR is this big project that provides locale data. So it has currencies, and it even has translated currency names and symbols in all languages. It has a list of countries, Drupal core uses it, languages, and a lot of other data. And it's maintained by big companies such as Apple and Microsoft and Google. So we decided to build a library that would take parts of the CLDR data set, and then it would provide these entity classes that would represent that data, and then we could use that from commerce. We also needed a way to format currencies according to locale, so a euro amount is not formatted the same way in France and in Germany. And the only previous way to do that was with the PHP IMTL extension, which is good, but it's not available by default on many servers, which meant we couldn't depend on it. Even Symphony couldn't depend on it, and their user base is much more technical. Luckily we found the formatting information in CLDR again, which allowed us to re-implement their number formatter in 300 lines of code. So when you add all of that together, you get commerceGuys IMTL. And we had great success with that first library even to the point of influencing Symphony IMTL. So Symphony IMTL started its life as a library that just provided the English fallback in case you didn't have the extension. But once they saw our library, we convinced them to follow the same steps. So they copied their approach and our generation scripts, and they started shipping CLDR data themselves. So right now if you're using Symphony 2.3 or even 2.6, you have the same functionality in the sense of currency lists and country lists and so on. They still don't have the number formatter, but we are working with them to merge that into a future release as well. So with our first library, we actually managed to influence Symphony and connect with them and start cooperating with them, which was a pretty nice win to start with. The second library we created is called Addressing, and it's the library version of Address Field, basically. It handles postal addresses, their storage, their validation, their formatting. And when you think about it, every country has its own postal requirements. So these requirements tell you which fields you need to show in which order, how they're labeled, how they're validated. So we needed to introduce this concept of an address format and then use the loaded address format to generate an address form or to validate an address or to format it for display. Of course, this also means that the library needs to have a data set to be truly useful. And luckily, we didn't need to create such a data set because we found it in Google. Google created a data set for 200 countries along with their lists of administrative areas because they needed it for Android. So we contacted them and got their permission to release it under DMIT license. And by doing that, we created a truly unique PHP library, which got over 300 stars in one week. So it made us the trending developers in all of PHP on GitHub, and it connected us with the Cilius project, which aims to create an e-commerce solution on Symphony 2. So Cilius decided that they want to use our addressing in zone and text libraries inside their own system, which is a pretty big win. Now I should mention that that hasn't happened yet because they don't really have full-time people working on it, and I'm afraid that we will have to be the ones to help them do it if we want to see it happen. Then we created the zone library, which introduces the concept of a zone as a geographical grouping. So a list of countries, a list of states, including or excluding postal codes, which is very useful if you're doing any kind of shipping or taxes. So for example, you might have one shipping price for California and Nevada, one for the European Union. And it's very useful for taxes because you might have tax rates that only target a specific zip code or a country plus some zip codes, which is common in Europe with German VAT, for example. And then there's our crown jewel, which is the tax library. The tax library holds over three and a half years of our tax knowledge. And we learned this the hard way. We actually had to spend more than a month listening to David Kitch and our tax expert explaining this over and over to get it right. No e-commerce solution gets this right. So we decided to do it right and to create the library that others can use. This tax library has a data set with predefined tax rates for all of the EU. And we hope that the community will help us by adding tax rates for their own countries. Then it has a really smart data model that takes into account that tax rates can change so they need a start and end date. And finally it has this system of resolvers that allows us to write pluggable classes for each country. So we have one class that handles EU specific logic, one class that handles Canadian logic, and so on. And these classes can be units tested and they handle the differences between B2B and B2C physical and digital products. And all of the other complexities that we can think of. And this library really attacks the whole issue of EU VAT changes that targets people who do digital commerce. So from 2015, you need to start charging the VAT of the customer. And this created huge ripples in the community. We addressed this with the library. And by doing so, we did not just get the attention of other e-commerce solutions that are open source, but we also got the attention of SAS solutions. So Foxycard, which is a host of e-commerce solutions, is now using our tax library. And Kong, a British SAS solution, is also using our tax library. And because they are using that library, they found bugs in our tax rate data, they found edge cases, and we fixed that, and together we made a lot of progress. I'm really, really happy about that. And more welcome. We are working on libraries that are on pricing, so the interaction between taxes and discounts, payments and shipping. But that's not important. The point of this is that we now have enough examples to look at the actual problem space of creating libraries and what can go wrong. Of course, before we do that, we need to ask ourselves, why should we go through all of this effort in the first place? Well, first, it's a good chance to re-examine your problem space. If I'm writing an addressing library, then I'm suddenly thinking about the addressing problem. Where does it start? Where does it end? How do I need to solve this properly for my library to be truly useful? So I don't really have a chance to do it in a half-baked way, like I might do if it was a part of a much bigger application. Of course, for us, one of the main reasons is that you get additional exposure. Suddenly, many other communities are using Commerce Guys libraries, which means that I can tell them, if you like this, there's more where that came from. And it also means, of course, additional developers and additional help, additional people coming to Drupal Commerce. It gives us a chance to validate our implementation. Commerce 2-point tax won't be ready for other six months, but people are already using our addressing and tax implementations in production, which means that I'm getting fixes for edge cases all the time. Someone will open up PR saying, your postal code validation is not precise enough in China for Taiwan. I say fine, we'll fix that. Or someone says your tax does not account for a U.S. company that's registered for UVAT, I say fine, we fix that as well. So that means that when I release Commerce 2.0, it will have many of these edge cases removed and it will be much more battle tested than it would have been if I had kept it under wraps. It's a big win. And you get more maintenance help. You will notice that these are hard problems, maintaining address formats for every country, maintaining tax rates for every country. It's a really big maintenance burden and no one really wants to help, because as I said, that's the most boring part of e-commerce. But if I gather maintainers from other communities, if I work with the silliest maintainer and other maintainers that may be together, we can solve all of these problems and just leave more time for solving the fun problems. And finally, it allows you to back forth this logic easily, because the library is isolated. It means that I can plug it into Drupal 7 or Drupal 8 into a symphony app. Wherever I am, whatever kind of a project I'm doing, I can count on my code, which is also a good thing to have. The not so hidden cost of this is time. Remember how much more time it takes to create a contrib module versus just doing something for your own site? Well, the same kind of a trade-off exists between creating a module and creating a module and a library. For us personally, it's been months of additional development. We would have had a beta of commerce two-point text if we hadn't gone to library routes. But as I said, for us, the additional exposure was worth it and it was something we really wanted to do all along. One cost that's a part of it, well, let's break down the time cost. The first problem, of course, is learning how to make the library in the first place. I can help with some of that. The other problem is the fact that you're looking at more edge cases and solving the problem in a more complete way. It's also fine. But the third problem is that your library needs to appear native to developers of all kinds of systems. So symphony developer, a larval developer, a triple developer, all of them should find your library easy to use and integrate. Code should not be weird just because it uses an external library. If it is weird, then you've already lost because the developer experience has suffered. So doing this is actually hard. So think about all of these systems and all of these developers and how they're going to proceed your code. And we'll look at some tips and tricks on how we can actually solve that. Let's look at how a library looks like. Let's say I want to represent currencies. So I start by creating a currency interface. The currency interface describes how a currency behaves. So a currency has a currency code, a name, a numeric code, a symbol, and the number of fraction digits. I can get all of this data and I can also change it. This is the contract for the currency. Now at the same time, I implement a default currency object. This is the default object that I can use, for example, if I'm loading data from JSON. So if I'm taking JSON data inside the library, I will load it into the currency object. The currency object is also used by symphony systems that use doctrine. When you're using doctrine, you can add an additional mapping file that describes how such an object is persisted and loaded. So you can reuse the provided object by just providing the mapping separately, which is really neat. However, systems like Trouple and Laravel cannot do that because they require entities to extend their own base class, which means that for Trouple, you create your Trouple entity types like usual, but you just implement the library interface, which means that the data that Trouple loads and creates can actually be used by the rest of the library. And we'll see how that looks. Of course, an entity might not just be a bag of getters and setters and empty properties. It might have some kind of logic. OO purists will say that an anemic data model is not a good thing, and at least it will have some kind of helper. So for an address format, there might be different ways to get the format information, which fields are used and in which layout. So what we do is we use traits to accomplish this. Who here knows how traits work? One, two, three, four, five, six, OK. So a smaller portion of the room. Traits are basically language assisted copy based. They are a new feature of PHP 5.4. And you write a trait the same way you would write a class. And then other classes reference that trait. They use the trait. And so that way, both the currency default class and the troop entity use this trait, or the address format one, doesn't matter. And they share the same methods. That way, I can share a code between different classes without needing to extend a base class. So that's good. It also means that we can unit test this trait in only one place, and we don't need to repeat our unit's tests for both the library and the triple integration. So traits are a really useful tool for writing libraries. And they're the main reason why I went with the PHP 5.4 minimum requirement in the first place, though since then it has become normal since PHP 5.3 became unsupported. Entities frequently have references, relationships. So a node has comments, for example. Now with the triple, you would get an array of comments. But doctrine would actually give you a collection. Now a collection is an object that behaves like an array. But since it's an object, it means that you can lazy load stuff. So the collection can load each comment only when you first access it, which is a really great performance optimization. Now, luckily, doctrine collections are a separate project, a separate repository that has only two classes with 200 lines of code, maybe less. So you can easily pull in collections inside your own library, which means that you can make your own code in the library more elegant. And since you're using doctrine collections here, it means that doctrine can still use your default data model without changes. So it can use your class with the separate mapping. So that's really a useful trick. And it doesn't really affect your triple implementation. It just means that you're more accessible to symphony people. Once we have entities, we need a way to load them. In Drupal 7 terms, that means having a controller class. In Drupal 8 terms, it means having a storage class. The outside world calls this a repository. So that's how we're calling it here. And if you look at this code, it's a repository interface that loads one or all address formats. And that's all that we need to know. And then we can provide a default repository implementation that loads data from the JSON that ships with the library. But then Drupal can have its own implementation that loads entities. And you can introduce a caching layer or anything that you want. And of course, finally, now that we've described our data model and our data set, we, our library actually needs to do something. It has some kind of business logic, something that it's doing. We call this logic in these kinds of objects services.  There's nothing special about them. They specify the requirements in the constructor. They don't assume the presence of a dependency injection containers. It might be used or maybe the dependencies will be passed manually. So look at a zone matcher. It requires a zone repository, which will be used to load all available zones. It type hints the zone repository interface, which means it doesn't care which repository it's getting, the Drupal one or the library one from JSON or from the database as a source. It just wants some kind of a repository that can give it zones. And then it has a match method, which will load all of the zones and match them against the provided address. So simple. And all of our services work the same way. Simple small objects that do one thing and do it well. Validating an address, formatting a price amount, deciding on a text type, resolving a zone. As I mentioned, the library has the problem of having to appear native to different kinds of developers. And that's not always easy because no matter how much closer we are in architectural style, Symphony and Laravel and Drupal still do things differently. And you need to account for that. So let's look at some of the problems that might appear. The first problem we have is the problem of translatable strings. Now, don't get me wrong. You can have entities that have the concept of multilingual baked things. So you can assume that a currency might exist in multiple languages. That is not it. What I'm talking about is simply translating some strings that might appear through the library. So for example, if I'm outputting an address form, I need to translate the string state or province. So we basically cannot do this. Why? Because different frameworks do this in a different way. So the way Symphony and Laravel do string translation is to force you to create your strings in a separate file, keep them IDs. And then your PHP code just calls the string translator with DID. So they say, translate the string with DID, commerce guides addressing province. But Drupal, as you know, has the T function, which always requires the full source string. So that means that you cannot have a single unified way of dealing with translatable strings. And what our libraries do is actually not translate strings at all. Instead, we use constants. And we tell the implementing application to replace the constant with the translated label. So let's say that we have three different labels for the city field, the locality field. It can be a city. It can be a district. It can be a post town. We simply define three constants. And then the Drupal module is the one that maps the constants to a label that was passed through T. We have this neat streak where we don't add the constants to the interface. Instead, we create an enum class.  So it has the constants that you're using. And then it has a bit of sugar that allows you to say, this is the default one. And these are all of them, which is really useful if you're building a UI. So for example, a Drupal UI for creating an address form can now list all of the available options. We have a commerce guys enum library for that. So it's a good thing to keep in mind. No translating strings. It's not so bad if you know your strings in advance. Then there's the problem of pluggable implementations. So let's remember how resolving a text type works. We have multiple resolver classes and we call them one by one until one of them gives us an answer. Now, other libraries or modules might provide their own implementation. Someone might provide a Serbian text type resolver. The question is, how do we discover these implementations? Well, on the library level, you don't do that. So the text type resolver engine does not do any kind of discovery on its own. It just assumes that it is past all of the discovered resolvers. And how the discovery is done is not the library's concern. Different systems have different ways of doing this. So in Symphony, you would register all of the resolvers in the dependency injection container and give it tags. So you'd use tag services. And then the Symphony application gets all of the resolvers with the specific tag and passes them in. Drupal, Drupal 8, uses plugins for this.  And that's what Drupal uses to discover which classes are available. So you want to use plugins if you're using Drupal. And Drupal Core actually has certain places where tag services are used, but I would argue that's not really a native thing to do in Drupal. And I'm not sure how much you can see this, but in the bottom, there's an example of how Drupal Core integrates Symphony constraints. So Drupal uses the Symphony validator, but it makes the constraints discoverable as plugins. So what Drupal does is it declares the plugin type and then it creates plugins that extends the constraints that were provided by Symphony validator. So we would do the same thing here. I define a text type resolver plugin type and then I create a DOM plugin class for each of the resolvers that ship with the library and that's it. I extend the library class, I maybe replace the message with something that was already localized and I add the annotation on top that is used to do the actual discovery. The important thing to note here is knowing when to stop. This means that there are some problems that are simply not worth solving in the library. Why? Because the different parent systems simply vary too much. For example, forms. Each framework has a completely different way of doing forms, Symphony forms, Drupal forms, Laravel forms, whatever the way that's done. So it means that the library simply should not provide forms. It's easier if you don't do it. Now you might be tempted to say, okay, I will build my own form builder that will create some kind of generic form structure and then I will create class that will transform that structure into a Drupal form, a Symphony form, and so on. But don't do this because it's complexity and it means that your implementation won't appear native to Drupal people or Symphony people. Suddenly you have a form that you cannot alter or you cannot understand how it's built. It's weird. So that's also one thing to understand. Know that duplication is not always a bad thing. For example, the addressing library has a formatter class. So the formatter class takes an address and it outputs HTML with the rendered address and that works great. However, if you're writing a formatter inside a Drupal, then you would expect to have a render array. So to appear more native to Drupal people, we simply implement our own separate formatter duplicating about 150 lines of code. But it means that the developer experience is better. So let's talk about which problems we should actually tackle. We now know why we would want to do a library. We know what can go wrong. We know how we can fix some of those things, but which problems do we actually start tackling and what do we handle in our own libraries? Well, the first problem is the one that I like to call hard problems. So hard problems are the ones that require domain knowledge to get right. These are the things that require experience and you can often see other systems doing them completely wrong. So a good example of this is taxes. Many systems do taxes in a wrong way or the interaction between taxes and discounts. If you are solving a hard problem, then you're basically turning all of your experience into a library form so that it's available to all of the PHP community, which means that you're providing great value. Then we have boring problems. Boring problems are the ones that have a lot of edge cases. So think for example, addressing. Addressing is not hard, but every country has its own address format. So you need to gather all of this information. It's not easy to do this alone. So if you're doing a library, you can do this with more people and you can tackle a boring problem. Think also about logging. You really don't want to reimplement logging, but for example, monologue does that for you and that's why it's useful. So in this kind of cases, you usually start by thinking, oh please tell me, I want to spend a week doing that and then you find a library. But if you don't find a library, then you will save many other people the same efforts and that means that your library will be very valuable and if no one is using your library, then it's not very valuable. The main question to ask is, are you saving anyone time? When I talk to e-commerce maintainers and we talk about libraries, they say, yeah, sure, libraries are a great idea. Let's create a cart interface. Nobody cares about your cart interface. Why? Because a cart interface is something each of us can think of in 10 minutes and then we're done. If a library can be reinvented in an hour, then it will be reinvented in an hour because everyone has their own opinions. If you want your library to be widely used and if you want to go through all that effort, make sure that it's saving someone days and weeks and months of effort. That way, it's more bulletproof. So definitely don't just provide a data model. A data model is great, but you usually want to have some kind of business logic, some kind of data set, something that you're doing. And we'll look at Drupal examples in a second. That second has passed. So let's think about what we can decouple from Drupal and release to the outside world. It's a big conversation to have. I only have my own personal opinions, so I cannot really provide definite answers. But for example, there's Migrate. Migrate is an awesome tool that I haven't seen anywhere else. Many projects would benefit from having Migrate, having that kind of pluggable architecture that really allows you to load, extract, transform the data and do what you need. So I think there's great value in providing some kind of an ETL library like that. And then there's our Darling Views. I don't know if you've noticed, but many projects have started to imitate or duplicate views. So in the symphony world, Celios has started a bundle that's basically views. An Auro platform, which is this really great business framework that's used to build Acchia Neo and Auro CRM. They are also building their own views thing. And the way they do it is they create the view in YAML. And then they load that YAML and they build the HTML from that. But it's not as dynamic and it doesn't have the architecture of Drupal views because we've spent so many years perfecting that. So if we could actually spread that kind of architecture with pluggable fields and displays and extenders, that would have great value. There are many other examples we can talk about it. I mean, for example, we are talking a lot about how Drupal 8 has this insanely great rendering and caching with this kind of intelligence that other systems don't have, always knowing what is cacheable and what the cache contexts are. So maybe we can export some of that to other communities. The point is in spreading our own gathered knowledge outside of Drupal. Why? Because it simply makes sense. We've already spent the time figuring out these problem spaces. So if we are doing that, we might as well reap some more benefits from that. Just take into account the differences between systems. Drupal is this dynamic introspectable system that's configuration-driven. Symphony and Laravel are code-driven and static. So that means that you need to think about different expectations. Drupal people want UIs. Symphony people want to write YAML. You need to account for everyone. But if you're smart enough, then your library will hit the sweet spot and it will be truly useful. And I'm looking forward to having this discussion in the community and then figuring out together how we can do this in an easy way. Okay, so we have a good 15 minutes for questions. So let's start the discussion. What did you find confusing? And what are your thoughts on this matter? I know there's at least one question. You're just shy. Oh, there we go. Okay, sorry. My question is, was there a reason why you took the approach of making completely separate libraries rather than the symphony approach where they created subtree splits that were read only? What was the decision making behind that? Well, that's just a code organization thing. What symphony does is they're basically one huge library and then they split parts off as separate repositories.  It's just an organization thing. We certainly wouldn't be able to automate splitting off that if it was inside the main Drupal commerce repository. You need to make the separation between Drupal commerce, the module, the Drupal application, and the library, which is this small, powerful piece of code that doesn't have any dependencies. That's the trick. Our libraries only depend on each other. They don't have any other dependencies. I have two questions. The first one is, in Serbia, do you refrigerate your eggs? Yes, I refrigerate my eggs. I just needed to know that. And two, you talk about maybe views or, I don't know, maybe panels. Some of the really things that make Drupal great. So I guess there's two parts to this question. One, I get a little scared if we're gonna give views away to everybody because I think it makes Drupal awesome. But two, I think big parts of what makes views awesome is the C tools integration, being able to have the UI. That would be really hard to separate out from the Drupal implementation, no? Yes, sure, it's not easy. But the main point of my idea is that we take at least the knowledge that we've accumulated over the many years we've been doing this as a community and then allow others to benefit. We keep talking about how much Drupal it has benefited from using Symphony, but we actually have a lot to give ourselves. And even if we are not using a library directly, which we would, at least by creating a library, you allow others to make use of all the knowledge you've gathered. So I don't think we should be afraid of spreading knowledge. As I said, people will look at it and then we'll be able to tell them there's more where that came from. So what else is on the roadmap for commerce libraries going forward? What else do you plan to break out into these separate? Yes, so the main one we're currently working on is the pricing library. The point of the pricing library is to have calculators that can figure out how to apply a discount to a price that contains tax. So that means applying percentage and fixed rate discounts to one line item or the entire order or doing some proportional calculation. So all of this is common with discounts and shipping. Other systems get it wrong. So there's a lot of value in sharing that. We initially tried to also do this kind of a price value object, but turned out that cannot be integrated back into Truebolt, so we are focusing on the calculators now. And Nik Fahalik, my colleague, has a great architecture in place for a shipping library which also doesn't exist elsewhere. So I think that we can provide a lot of value by doing this. Thank you very much. Discounting is and couponing is a huge debacle. So we really appreciate that. Yeah. So this is a question, it's just a comment. So this approach of building libraries is actually really useful, even if you're not building those libraries to be shared outside of your company, right? So we're doing that now in Drupal 7 with complex Drupal sites. Building shared libraries is actually a lot more powerful. You can do unit testing on them. You get a lot more test coverage and those kinds of things. So it's definitely an approach that I think everyone will be doing in Drupal 8. Yeah, I agree. I've actually heard stories about certain French projects where they had to use Drupal 6 or 7, but they elected to build all the logic inside the decoupled libraries and then connecting that with Drupal so that they have the benefits of unit testing in clear code and the ability to more easily migrate to a different Drupal version or even a different framework. And Frederick Moran, FGM, has been doing a lot of that. He had a session about that at Dev Days. He's at Drupal.com. So if you see him, you should ask him about it. So you see, I knew you had questions. So in any case, if anything else pops into your mind, I will be at the Commerce Guys booths all week so we can continue this discussion. The point of this was just to make you curious and get you thinking and then we can go into more details. Thank you. Thank you.


One competitor called his communication with dogs hypnotism or unnatural control. Also emphasized was the mutual confidence between Sepala and Togo. The mushers sometimes relied on Togo's intuition and sense of smell when his own vision failed him. This was because he was Sepala's favorite dog. In the film, Balto makes a brief appearance. He is the lead canine for Gunnar's team. Gunnar gets the lion's share of credit because he is the one who really brings the serum to known. This largely describes what occurred, though some specifics have been changed. This explains the disproportionate amount of fame that the real-life Balto has attained. In addition to media attention, there are also movie deals, a tour and a statue. All of this is not to suggest that Balto didn't deserve the credit. Gunnar's crew had to drive through a blinding storm, and the cruelest miles claimed that Balto's sense of touch and smell were what kept the squad on trail. Furthermore, despite the fact that Sepala appeared unperturbed on his own behalf, as he had applauded Gunnar, it was said that he was furious because Togo had not been given the credit he deserved.


I haven't done a board setup video in a long time, so I got a new board. It's a hockey, John Fitzgerald pro model. It's eight and a half. I wanted to go with a wider board because I got the A38 last time and I'm not really flipping my board anyway, so. I'd rather have the stability of a wider board. So that's what we're doing right now. Got a fresh razor blade, so I don't ruin the grip tape. Gonna set this up and hopefully get a couple clips at the park. But yeah, let's set this board up. I always love the smell of the new deck, which is weird. I got this board from Overcast Skate Shop in Temecula. So if you have a down that way, go and check them out. Support the local skate shop. I just got this haircut too. It was eight bucks, opposed to spending like 50. So this was done in like 15 minutes and it's not too bad if I must say.  I kind of roll up the grip tape so I can transport it easily and then it creases like that and looks more ugly. It's not a good start. So hope I can still do this. Fresh razor, freshy. Let's make it easier for myself. I only have to cut one side of the board, see? I'm in the grip. I only have to cut one side of the grip. So I'm gonna put it on this half. Drop the razor.  It looks like my grip is dirty already. I haven't even skated the board yet. I think it's this one. The one that has the air for me. Just met up with Dan in Long Beach right now. Apparently I've never known this park existed, but it looks like the most perfect skate park you could ask for in Southern California. It literally has everything you need apart from a quarter pipe. Never in my whole life did I know that a park this perfect existed. And the flat ground's really good too. It's darn near the perfect skate park. My only qualm with it is I wish it was a little wider. Like if this went out to the sidewalk, it really gets like one person can go at a time. It'll be a little wider. You could skate both sides of the ledge. Yeah, it is true. I think some people were like, oh, well then I'd want a quarter pipe on each side. This sort of forces you to not hog the skate park. Yeah. Like it's not wide enough to turn around right quick. So I do like that about it. Let's see some tricks, dude. Hi, Mom. Hi, Dad. Stay and watch this. My mom watches the videos. Does she? Yeah. You okay? He literally did that first try earlier. Now that he slammed on that, he can slam on this. He also did that first try. Dead stop, but.  What do you mean? You do a shove it into a 50. Back, uh, front, backside? Let's do both. Hell. Well, first you do a backside. I can't shove it. Yes you can. Watch my shove it. That was a good shove it. That would have gone right into 50-50. This is my body weight. Yeah, that's perfect. So secret to shove it's 50-50s, aim for nose grind for the first second. Really? Yeah, don't aim for both trucks. Think your front should be first. Yeah. Oh yeah. Try front side, or backside I mean. So front shove, back grind. Yeah, the secret to that one is to baby the shove. Like don't think so much about popping high and getting into it. Just front shove towards the ledge, you'll get high enough.  Keep scaring myself away from the. Yeah, that was it. I keep missing.  I'm too, I'm jumping too far this way. Yeah. So Dan, he's found the secret. He did it second tee. I did it. Okay, here's what happened.  I front shoved at the ledge, missed the coping and then like shuffled into a 50-50.   I didn't even do the trick yet. That was a trick. I'm five tries deep. I haven't done it yet. But he, he just. The secret is I don't pop. He doesn't pop. I miss pop. But he has more control over the pop than I did. No, I know that, he's had more commitment. You reckon? Yeah, cause your front shoves. I'm wide putting it. They spin flat, they're like control. Mine are like quick and don't pop. So, my lack there of is what I can do on my thing. See? Maybe I'll just go to back spin. He just scoops it. He doesn't have to pop and it's so controlled and easy. I'm making it harder for myself. I haven't even done one yet. Yeah. Closer than I am now. I think. Okay, I'm gonna try to pop. You did. Yeah. See, when you pop it, it overshoots you. The anti-Oli man. He doesn't like to Oli this guy. I slap you into my front shoves. Kind of weirding me out now that I think about it. Cause I understand mis-popping a flip trick and it working. Yeah. Because you have this motion. This and then this pushing down. And it goes, yeah. This, it makes me, what am I like, oiling and then this foot sliding down and then back. How am I doing this? I think you're just in the pocket and you just kind of. But what's making it go in the air? I'm so, it's like wet now. Your front foot, I think. It's like dripping.  I kind of chopped away at it with scissors and it kind of made it worse. I think Dan's gonna get the trick before I do, unfortunately. Unfortunately. That's God's will. It is God's will that I reign supreme. What part of a hundred thousand subscribers don't you want it?  He has, he has a sense of balance, dude. I have an advantage cause I don't use excuses like height.  Dan's right battling my phone. Yeah, we should probably double check his theory of relativity. Cause if he's wrong about one thing. You're gonna do a switch. I didn't change any, I didn't change my angle.  He probably equals MC Hammer. Like he doesn't know what's going on. Oh yeah. That was like the right idea though. It looked like you were going for the 50. It was just that pop was wrong. Is this even skating? I feel like this isn't even skating. It's not, not skating. I think we all have these battles where it feels like it's just not getting any easier. But why was it so easy at Lincoln that day? I had a, I had a skinny abort. I think I had a 338. I honestly think it was just your mindset. You're probably just trying all the tries. These you're not.   Just go get the slam and then you'll land it or slam. Damn it. Dude, I've done like three of those. Rat Cowboy. He's pretty sick. So Rat Cowboy sitting out there now. Shout out everyone from the last video that cop some evening mob stuff. That's like the main way you guys can support me. So if you guys want to support your boy even further, head on over to eveningmob.com, pick something up. And yeah, cheers for watching the video if you guys have made it this far. I'll catch you guys in the next one.


Good day, fellow investors! I recently listened to an interview with Monish Pabrai and he said that in 2009 from the peak in 2007 to till 2009 his fund was down 65%. Now what kept him alive and okay was that he knew he owned value, he knew he owned great value, great businesses and he knew that somewhere in the future those will rebound and that was the case. By 2011 he was back out of his loss of 65% so he was knowing that it will happen somewhere in the future and he was willing to accept that volatility. However to have such conviction on your investments even if they are down 65% you must own great businesses, you must own value and you must buy it at a fair price with a margin of safety. Today we're going to discuss a great business and then it's about you whether it is value now and whether it has the margin of safety required for long-term sustainable investments. For some it will be for some not yet but it's also a stock that I'll put on my watchlist. I'm talking about the Intercontinental Hotel Group and I'll give an overview of the company and I will finish with a valuation, a pricing valuation to see okay what kind of return can we expect over the long term at a certain price that we buy the stock. Let's start with the overview. So the stock is listed on the London Stock Exchange and there are American Depository shares managed by JP Morgan on the New York Stock Exchange. So Intercontinental Hotels is an asset-lite global hotel company, asset-lite means that they do not own the hotels, they only manage and franchise them. So if the company, if the hotel goes bankrupt because there are no customers, they don't lose much except for their fee of their revenue. The pipeline, if we exclude room closures, implies a growth rate of 30% over the next few years as the hotels are being built and contracted. So you're probably familiar with some of their brands from Intercontinental Crown Plaza, Holiday Inn etc etc and they are creating new brands to cater to them in new millennials etc etc. So they are really doing well and this is their brand value, this is what they are selling to their franchisers and this is how they are gaining fees. Their current exposure is really highly weighted towards the Americas but the Chinese pipeline is growing at double digits. Consequently most of the profits come from Americas too for now but China is also profitable, Europe is also profitable and as they grow the number of rooms there, as there is economic development, it is expected that profits would also grow from there. Consequently Asia is the future and that is why in 2017 their number of rooms there grew 16.6%. 2015 presentation shows that they are focusing on those markets still on the US, Greater China is the second market, Middle East is the third market, Germany, UK, Canada, India also, Russia, Mexico and Indonesia are the key 10 markets to focus. Now when it comes to investing in great businesses the key is the business model. With Intercontinental hotels it's all about the fees as they don't own the hotels there is much less capital needed to develop to grow therefore the asset light business model. Further they are also less affected by business cyclicality as the margins are high and their revenues come from the fee on the revenue of the hotel not on the profitability of the hotel, on the revenue of the hotel. So if there is a recession and a hotel loses 20% of revenues Intercontinental hotel will have a 20% decline in the fee and the margins are really high so 40% so even in a deep recession they can protect their long-term profitability which makes this a great business. Even in 2009 Intercontinental hotels with 15% revenues on the global hotel industry still remained profitable when many hotels went out of business. So these are the financial highlights you see total fee revenue is 1.7 billion operating profit is 763 million which is a 42% margin so even if there is a decline of 20% in revenue Intercontinental should still be profitable of course and then you have to weather the storm the stock will probably bleed but that is what I call opportunity. Their margins are increasing in a good environment their free cash flow is very very high and stable at around 500 million they are able to reinvest parts of that cash flow at a high return on capital which constantly increase the cash flow that cash flow is then separated and shareholders are rewarded and this is the dream of every dividend growth investor this is the ordinary dividend progression of Intercontinental's dividend so you can see that they have been growing their dividend for 11% over the last 15 years and this is the ordinary dividend there have been many many special dividends and as they were selling their hotels and rewarding again shareholders so they didn't do stupid things with the money that they have been left over they returned to shareholders and rewarded shareholders now on the risks as always it is important to look at that a company has the net debt is 1.8 billion and most of that is in UK pounds however there is also an interesting lease obligation of 3.3 billion which I always like to see what it is about because some companies don't have that but have a lot of lease obligations short-term ones which are similar but this 3.3 billion in this case is an 88 year long lease for the Boston Intercontinental Hotel which is not material for now as the yearly payments are around 15 million so that's really not material even if it looks like a big deal as a three billion dollar liability so great business great management low risks however there are also other risks we have seen the security breach at Marriott now that will hit the company expected cost of a billion but when you have so much cash and cash flows you can weather that then there is a potential recession that we discussed in the stock market news video on Friday how the yield curve is inverting and yes a recession would hit intercontinental hotels but it will not bring their profitability to below zero they will still be able to perhaps pay their dividend it will not grow but hopefully the stock market the stock price could crash and give us a better entry point but before we discuss the better entry points let's discuss the industry and then see how to go about investing in this that is this is pretty simple there is inflation global GDP growth and developing Asia keen on travel while the developing countries are aging which gives more time to travel this leads to global industry growth and the current situation is much higher than where it was in 2008 it's highly likely that the number of tourists across the world will increase over time even if the growth might be volatile due to recessions etc another risk is airbnb but okay that's a low cost option and the industry is growing that fast that even hotels and airbnb are able to grow at the same time for now we'll see how it will end up but these hotels let's say a hotel is a different thing than an airbnb and there will be a market for everyone probably now with an investing perspective as i said the asset business is light which allows for high dividends which means there is a lot of free cash flow for shareholders and that's nice when you're an investor you want to be rewarded the key is to try and understand where will this company be in 10 years what will be the possible returns given the structure of the business i would dare to assume the dividend growth to continue at 11 percent over the next decade because they are not paying out that much money yet plus there is a lot of special dividends coming when there is more money so let's assume 11 percent growth there if the ordinary dividend grows at 11 percent over the next 10 years the current is 1.04 dollars the 10 year forward dividend will be almost three dollars so as the current ordinary dividend requires 200 million where the cash flows are 500 million the 300 million reinvested should allow for dividend and profits growth in the future so when i put this into a small x shell spreadsheet just to make things easier to comprehend if i lower the current valuation which is 15 to 12 just to be more conservative i add an 11 percent earnings and dividend growth the stock should trade at 93 with a dividend yield of 3 percent in 2028 in the meantime you get dividends between one and three in the next 10 years this means that at the price of 55 which is now the total return should be around 7 percent 2 percent from the dividends and 5 percent from the current earnings yield that's good for some people much better than most of the stocks in the market will do so that's why this is a great business but if we can get the opportunity to buy this at a cheaper price look at the 45 price for a great business 3 percent yield plus a total return of around 14 percent and then if there is a bull market and it goes back to 55 then you make 30 40 percent in two years which even increases your portfolio return however i think that there will be an earnings contraction in the next recession which might give us an opportunity to buy into a great business for a higher return as i said the 45 looks really tempting and it wasn't far from 45 in 2016 2012 it was below almost close to 20 and it was close to 10 in 2009 look at what happened to the stock price from 2007 or above 40 it went down to ten dollars in 2009 for a 65 75 percent downturn so even if it is a great business it can get into trouble on the stock market and this shows how the markets are irrational so let's put this on the watch list and wait for irrational markets if you want to see more companies like this that we watch and we wait for irrational markets please check my stock market research platform there is a 40-day money back guarantee you see my complete research what i did over the last just six months since we started the platform you can expect something similar for every next six months because that's what i do that's what i love doing i love researching stocks and finding the best investment opportunities out there looking forward to your comments any other similar great business ideas please share them in the comments and i'll see you in the next video


This 2019 Ford F-250 Supercab Short Box is stock number 12299Z. We're here at Summit Automotive in Fond du Lac, Wisconsin. You're new and used heavy duty truck headquarters. This 2019 Ford F-250 Supercab has the 6.2 liter V8 engine. This truck has been fully-safetyed and inspected by our service shop for the state of Wisconsin inspection process. It has a fresh oil and filter change. All the fluids have been checked and topped off. And this truck is 100% ready to go. Magnetic. Metallic is the color. We shoot all of our videos in 1080p, 60 frames per second. So if you have HD capabilities on your computer, tablet, smartphone, or television, turn them on right now. Because it is definitely your best way to check out the quality, condition, and options of the truck before seeing it in person. And if you like the video and would like to subscribe to our YouTube channel where we do videos of our new and used inventory each and every day here at Summit Auto in the lower right-hand part of the screen is a subscribe button. Click that and then click the bell notifications and you'll get updates every day we do videos here at Summit Auto. It comes with the chromed 18-inch alloy rims and it has the Goodyear Wrangler all-terrain adventure tires. These are LT275 70 R18s and they have, I'd say, a little bit over half the tread left, maybe 60%. Frame and underbody is an exceptionally nice clean condition. Driver's side front fender is in excellent shape. I didn't see any dents or dings in there. Headlight lenses are crystal clear in that front bumper and lower valance are in excellent condition. No dents or dings, factory fog lights. The hood is in pretty nice shape as well. You get that chrome trimmed grille. Passenger's side front fender looks really good too. No dents or dings on there. And the passenger side rim, no scuffs or scrapes. As you go down this side of the truck take note of how clean the body is, how reflective and mirror-like that paint is. We take these HD videos so if you are far away or even if you're close by and just cannot make the trip down but you're still interested in purchasing the vehicle you can see the truck, hear the truck and have confidence in the vehicle that you're looking at before you even get here. So when you do get here there's absolutely no surprises and you can make a smart and informed buying decision from wherever you are at. Very clean down that side. I didn't see any dents. I didn't see any dings. It does have the chrome step bars. Back rim, absolutely perfect. Back tires, just as much tread as the front tires. Frame and underbody, absolutely perfect. It does have the camper package which gives you those anti-sway bars there and the frame and underbody on the rest of the truck looks really, really good. Cab corners and lower rockers all look good and those chrome step bars are in nice condition. FX4 off-road suspension package gives you the skid plates. Chrome tipped exhaust, rear bumpers in great shape. Back up parking sensors, full towing package which includes a receiver hitch, four pin and seven pin wiring. The tailgate is in very nice shape as well and it does have an access soft roll up tonneau cover. That looks pretty new. I didn't see any rips or tears on it. Very nice shape. Comes with a sprained bed liner. You also have LED bed lighting back here. Fifth wheel and goose neck prep package and you do get seven pin wiring back here as well. Tailgate step assist. Tailgate shuts nice and solidly and as you go down the driver's side just as clean as that passenger side no dents or dings on the box and for full disclosure this back rim is in very nice condition too. Down the rest of the side of the truck looks really good. It does have the driver's side door code entry. If you want to figure out how to find your door code on your 2017 to 21 Super Duty in the upper right hand part of the screen we did a video on how to do that. Heated mirrors, directional signals. These are the power scope mirrors. They power fold in, power telescope out and in. Inside the XLT package gives you the grey leather interior. There are no rips or tears on the seats. Really nice condition. Power driver's seat, weather tech floor mats, auto headlamps. That's for the lights. They have LED side lights, power pedals, tilt, telescopic steering wheel, power windows, power locks, power mirrors. So these mirrors do power fold in. As I show on both sides as you know that both sides are working properly and they do telescope out and in. You can see that one is working good too. We'll hop inside, turn the ignition on, check out the radio and the miles and everything that the interior has to offer. So you can see that this one has 10,998 miles on it. You do get a digital speedometer right there. Instrument cluster is very nice and clean. You get cruise controls and information center controls on the left, volume and Bluetooth controls on the right. And it does have the six speed automatic transmission with the optional tap shift. This one has the sync eight inch radio, AM, FM capabilities. It also has Sirius XM capabilities too. This is also where your backup camera shows up. And then you have a Bluetooth of course. And you can also do Android Auto and Apple CarPlay on this radio where you can project your cell phone to the screen. So if you have a navigation system on your cell phone such as Google Maps or Waze, you can project it to your screen. And it's like you have nav right on the screen. So it's a pretty cool system.  Does have 110 volt, 400 watt max plug-in and a 12 volt power point there. Passenger side format and seat are in excellent condition. No rips or tears, smells very clean inside this truck. I don't think it's ever been smoked in. And the headliner is in really nice clean condition too. You do get map lights up there. We'll take a quick look at the back seats and then we'll start it up and take a look under the hood. These new super duties, the doors open up all the way. Back seats are just as clean as front seats. No rips or tears back here. It does have the latch child safety system for any child car seats. Fixed glass rear window with the built-in rear defrost. These seats do fold up for a little bit extra storage. You got some tie downs back there as well. Back here you get a 12 volt power point 2 USB chargers and then another 110 volt 400 watt plug-in. Very nice and clean. You get a weather tech floor map back there as well. These doors just kind of spring closed like that. I've been told to show these stickers so read them. There you go. All right, let's start it up. Take a quick look under the hood. Starts right up. No check engine lights or anything like that. Let me know that the hoods open and doors are open. So that's working properly. I would like to thank you for checking out the video today. And hopefully from this HD video, you've been able to tell just how clean this truck is all the way around inside and out. Under the hood we have the 6.2 liter V8 engine. Engine maze is very clean, runs very smooth. Once again this truck has been fully safety and inspected by our service shop Wisconsin inspection process. Has a fresh oil and filter change. All the fluids have been checked and topped off. And this truck is 100% ready to go. There's your emissions sticker.  Lights working. I would highly recommend this truck from a quality and condition standpoint. And to see more pictures of this truck or one of our other 450 new and used cars, trucks, SUVs, minivans, wranglers, halftones, three quarter tons, one tons. You name it, we got to go to that website right there www.SummitAuto.com Full pictures and descriptions of every single vehicle from two locations all at SummitAuto.com. And if you'd like to check out more HD videos, you can go to youtube.com. Remember to like, subscribe, and share on this video and all the videos that you see there. In fact, in a second you'll see a link to subscribe to our YouTube channel and the upper left a link to more F-250 videos like this one, the upper right. There's a link to this vehicle on our website on the lower left and a link to one of our latest YouTube videos on the lower right. Click those, check us out and we're super excited to help you with this Ultra Clean 2019 Ford F-250 SuperCab Short Box XLT FX4 and Magnetic Gray Metallic. Thanks again for checking out the video.


Hey everyone thanks for joining me on today's podcast. Today I'm going to be speaking to you for a few minutes about a bad experience I had in Switzerland on holiday with my family recently what I experienced online fraud and the beautiful setting we were in was contaminated by what happened there and I'm teaching you in this podcast about how our experiencing self often overrides our remembering self and a beautiful experience becomes a bad memory because of what happened there and how that we need to manage that better. Enjoy leave a comment let me know what you thought about this hope it helps you. Cheers. We recall events in life two ways we have an experiencing self and a remembering self and these two ways that we engage with life determine what we take away from anything that we go through our remembering self simply remembers the experience where we were what we did how we felt what we saw and so on our remembering self does that that's its job but our experiencing self overrides our remembering self if while we are remembering something a particularly negative painful traumatic experience occurred in that memory like me on that day on that beautiful island and fraud occurs and comes into my life on my cell phone and I spent a good hour on the phone dealing with that internationally of course and the stress and the trauma of that that then bled into the day and spoiled the whole memory of that place in fact I jokingly said I don't remember the name of this island because it was a name I couldn't recall easily but I said I'm gonna forever now call it fraud island and we laughed about it and I thought afterwards how it ruined my day how it affected all of our day my experiencing self that whilst it was there in a great place I had an incoming negative experience that then soured my experience of being there and everybody else's time there and after I left of course as many of you know with that kind of experience of fraud it sort of carries on days afterwards and stills going and as I speak to you now because we're in this two-week window that the bank says all you've got to recover the money and so when I got home that night and the following days in Zurich it's kind of still ongoing I'm on the phone I'm still making calls and so the memory of that part of my week was ruined and lost and overridden by my experiencing self and I'm sharing this with you all because I'm interested in your experience around this what have you gone through have you gone through something you guys that has been like I'm trying to describe to you have you gone through something that actually if you just remembered it for what it was it was great but whilst you were there something happened and what happened has made it memorable for all the wrong reasons as it were because our remembering self that is attached to our emotions and our feelings overrides our psychological remembering and the feeling lingers longer than the memory does and the feelings always come up first when that place is mentioned and the feelings are triggered and the trauma is triggered when that place is mentioned and we lose something we lose something in life we lose experiences and events and people and relationships we lose it to surrendering to our remembering self instead of editing it and taking charge of our experiencing self and not allowing that to rewrite our experience that we had there you know two people can go through this same identical event but have very different experiences like a surgical procedure that's common and many people may have that kind of procedure and two people could be in the same hospital on the same day having surgery a few minutes apart by the same surgeon and the same anesthetist and so on and so on everything's identical but if one of them has a particular painful experience or if something happens on the way to the hospital like a car accident or something occurs whilst they're in recovery that's unpleasant or uncomfortable or unexpected that then becomes lodged in that experiencing self and the other person in the next room perhaps that had the identical procedure who thought it was brilliant and had a really successful surgery and had a good experience and remembered it well and reported it that way you wouldn't think it was the same experience both people were speaking about would you because one had a negative experience one had a good one so the memory is tainted and contaminated according to the experience you have whilst making that memory and I think what happens is later on as I said even now you are still processing the negativity and negative emotions the pain the trauma attached to what happened years ago this can be guys years ago decades ago even generationally because the experience in self took charge of controlling that memory the way it was lodged in the brain and the amygdala hippocampus won't get into that too much but I've talked to you guys before about my observation and interest and fascination about those two pieces of our brain the amygdala is the drama queen that records emotion it is the smoke alarm of the brain if you like and brings a chemical toxic dump with it once those feelings are evoked and the hippocampus is what I call the librarian of the mind that takes that memory and then files it forever in the way it was experienced so when it's ever triggered in the future it always comes back with the same reoccurring emotion first and the memory of where you were what happened second so I'm appealing to you I think I'm encouraging you guys to give thought to and let me know what you feel about this of your own experiences around this have you had something like this that can help the community understand it more beyond what I'm saying can you articulate this in a different way to me from something you're experiencing in the past or right now today and you became aware today as you went through something like I did on the day that your experiencing self is hijacking or otherwise was a great day for others or could have been a great day for you everybody else's experience was contaminated by mine that's what I hated too everybody was saying we're so sorry and can we help and don't worry about it and I spent my day apologizing for for ruining their day and it bleeding into the rest of the week do you have something like that because what's going on to give language to it is your experience in self is taking precedence over your remembering self so what we have to do is we have to redeem the memory we have to reclaim the memory and we don't deny that we had a negative experience but we don't allow that to be the abiding thought that we bring up the abiding way we relate the story in the future as hope today's podcast was helpful to you if it was please leave me a few comments what you thought about this and leave a review too and if you don't subscribe please feel free to do that and help me spread the word about this podcast if you feel it would add value to somebody else in your world hey the larger thought that this podcast is connected to is posted in my mentorship group it's a free mentorship group if you're interested in joining that and becoming part of that community go to paulscanland.com you'll see more info there and I hope to see you in the new community I've created online called the mentorship group appreciate you guys thanks for being here cheers talk soon