All right, let's get started We're gonna talk about GDP are today, which is one of probably the most boringest topics. I've ever given a talk on so I Already understand just to be ahead of it, but I want a little bit. That's me My name is where I work. That's what I do. That's Twitter I recommend if you have any sort of content filtering or HR department to not load that at work And Actually, I want to go back here real quick because I want to point out two important things Notice how they're the word lawyer or attorney is not in that title. What's so ever? I'd also like to point out the lack of letters after my name indicating that I have a professional degree indicating I know the law I Am in no way shape or form an attorney lawyer. I did not go to school for this. I'm a nerd that said We're gonna get into it because this fortunately has nothing to do with the law The law is what it is and there's a lot of people with that spend a lot of time on that But what exactly is GDP are who here has never heard these four letters in a row sounds about right? It's been kind of a big deal lately and More importantly, I want this out. There we go That's what it stands for now None of those words actually mean anything it is probably one of the most vague things that I've seen for something That's essentially this important. So I'm gonna break down. What is it about? data everything about this is about data Personal data and that's why our data is worth a lot of money a lot of money and For years we've just kind of given it away all these companies essentially said trust us and we did and It was a terrible idea. I cannot emphasize how bad of an idea this was From the time it basically started All of these services we just started handing over our data They asked us for something we said sure we just kept clicking numbers until I'm sorry kept clicking buttons until it gave us What we wanted that's kind of how we were trained to use the internet at least I was but I want to look at some numbers about What things are currently? So the first thing Now great 92% of people worry about their online privacy I can't think of a way to frame this question that someone would say no. I have no idea what this means Huh, okay. I have no idea how you could phrase this question that someone would say no So again, this does nothing Now the next thing is going to be Connection lost all right phone things not working. I'll just use this Now this is a better one 31% of company people actually understand how companies use their data. I Do this for a living and I don't really know what they do with all my data I have a better idea than most and maybe I just stopped paying attention because it's scary The next thing is going to be now. This is a big one because this is where it applies to us 74% of people have limited their online activity due to privacy concerns If you're building anything remotely a website of any sort kind application What have you the whole idea is that you want people to use it? Otherwise you wouldn't be building it And they're not coming they're stopping coming because they're worried about something they don't understand So now the question is why? Why is all this matter? What's the big deal all of these companies have one big thing in common All of them since 2014 have had a very large date of reach Sorry, let me try to find the numbers here because this thing is annoying I apologize Whoops, there we go. All right eBay 145 million people target 110 million people JP Morgan 83 million people over 57 million users and then 600,000 drivers Anthem, which is a health insurance, you know health management company 80 million Equifax we remember that one That's a hundred and forty three million and then we have yahoo, which was the big one with three billion and Now all you know users are not the same Depending on where they pull that data from is how valuable it may have been However, how many people in the last year or two have gotten new credit cards in the mail without being told because there may have been a breach And you have to keep changing your numbers online. Yeah, that's why So users have a very good reason to not trust any of us with this stuff because we violated that trust and frankly We've ruined it So then he incomes the EU Now the EU has always had More rights given towards users than the United States, which is surprising for many people in the United States And a lot of this boils down to the users have rights. They have rights that we have not given them in the past Now they have the right to be Informed which is essentially you have to tell them what you're doing with the data that you collect You have to tell them that you are collecting data Even if it's not important You have to make sure that they opt in Which means you cannot check those boxes anymore for them period Now they have the right to the access to the data now This is one of the bigger ones that you saw I probably saw some stuff come out if you have data on me I Have the right to a copy of it at will at request in a human readable format now what that means is Very vague on purpose because what is readable a lot of times would depend on what the data is But you get it you have a right to it And you have the right to be forgotten now this is a fun little story so In 2010 I deleted my Facebook account Mainly because I didn't go to a college that had us I never really got into it like other people and then the first Privacy thing came out. I'm like, you know, I don't really use this and this is just another thing got rid of it A few years later, I was doing a client doing some client work and I Needed to check some face. I was taking all the meta tags and all that other sharing stuff But I had to be logged in Told my client. Hey, I don't I don't have an account. He's like just go ahead and use mine So I go to log in it pings me like hey, you've not logged in from this state before and I'm like alright It's gonna ask me some questions whatever it's like shouldn't the person's friends like who are these people like I have no idea I don't know this person's friends. So I made a fake account That was fine. And then a few years later.  So I made a new one It would not let me use the email address that I had used when I created my first one 12 years prior I Do and this was back in 2010 when they said they would delete it like it didn't say deactivate it actually said delete It's not deleted If you really want to be worried about that Google Facebook shadow profiles, and that's how you can kind of find out stuff If you pull nothing else from this talk know any ideas what not just you need to understand the data that you collect No longer belongs to you You could argue that it never really did But it's really important to know that eight years the best thing you can think of is you're leasing it Because it belongs to the user now. What does that stuff mean? Why do you care? Why I'm sorry. Why is a developer does any of this stuff care to me that sounds like marketing this sounds like analytics This sounds like again stuff that I don't care about So the first part I went to this guy's James Lang does anybody know who this is Okay, he's in prison right now He got 40 months sentenced for better the Volkswagen emissions stuff that they got busted for okay He is not a CEO He is not a manager. He is an engineer He has the same title in his job that I have in my job He is in jail. He was not even and this is the important thing that came out The court even said he was not the mastermind He still got in trouble Which means that we're not Protected simply by saying I wrote what I was supposed to write or I just filled the specs That's not gonna fly Which means they're coming you know like the reason I bring this up is not to point this guy out I'm sure he didn't really think he was doing anything wrong And I'm sure that he didn't decide to cheat the emission systems on his own But he's the one that took it which means we're the ones that have to deal with this I don't think the CEO for VW even got fined So maybe I have your attention hopefully possibly now. What do I do about this and again? Why do I care? So the first thing We have to kind of drill down to what data does this actually talk about what does this stuff mean? Because it's such a nebulous word and you can call anything data, especially us They talked about it's personal data Now I want to first point out that the EU defines personal data differently than we do We just say personally Identifiable information that means one bit of data you can connect it to one person without any help you look at my email address It's my name with a period in the middle. That's personal. You know identifiable The EU just says personal That's anything Not only that they look at context they look at aggregate. They look at a whole bunch of stuff But the first thing's here. Okay racial ethnic political I don't think I have collected any of this data on a website other than maybe political opinions in a comment section So the first time I see this list. I'm like again, I still don't care, you know, none of this stuff matters But then the EU expanded what they meant by that All right genetic data. I don't even think I could connect collection any of that data by a metrics a location Core collects your location when it shows you the upcoming events pseudomized data Okay online identifiers That last one that one How many of these things are not in the user meta table or the user table? so we're collecting personal data by default and That's it's not that you can't collect it and it's not that you can't have it It's just we can't just grab it. It's really what it boils down to So this applies to everyone and now this is a caveat and I will get into this in more detail who does business with the EU And what exactly defines doing business that does not mean doing business with the European Union as a governing body That means anybody Who lives is a resident of is vacationing in is vacationing from the EU So the question the first question I always get with this is can I just stop selling to people in the EU? probably not Because you can't automatically identify that like is anybody here a resident like a citizen of a country in the EU Okay, when I was in Orange County that there we go if you buy something in Michigan from a company in Idaho GDPR applies Because he's a you know, he's a citizen of the EU whatever country in the EU obviously So it applies to everybody Every business every organization there's not a cut-off limit like oh you have more than X dollars or X numbers than it applies to everybody Blanket Now does that mean they're gonna treat everybody the same of course not what we don't know how they're going to be Now this is a big thing who was in charge of all this stuff who is supposed to be doing this work who monitors who does all of this They have no idea But there's two people that are involved and the way they define it is data controllers and Data processors now the controllers again more vague words that don't mean anything You know that a controller decides what to take in Where it's used Where it's stored and who else gets it so think of that as a gatekeeper Think about that frankly most of the time as us when you're collecting that data on the website You are a data controller now data processor is basically anybody else who touches that data Google analytics abandoned cart software anything you know Recurring user anything that you might be doing with that that you're handing a sass something like that They're like which one am I? Very possibly both you can be both So you have to start thinking about privacy by design It's not something you add in later It's not something you sort of bolt on is that you need to start Building things with the idea of keeping user privacy first and that trumps pretty much that word But that trumps pretty much every other goal now In terms of data now it's not visual designs on it, but actual data privacy first So you need to know Everything which sounds like a lot But we're building it Which means you need to know what you're collecting you need to know where it's going you need to be able to articulate to someone what you're doing with it an Easy way to think about this and especially who you're giving it to because that's on you know That becomes your problem sort of as well You know if you're thinking about using a data analytics program or anything like that Like if they can't explain how they do it in like two or three sentences It's probably illegal For the most part Now everything again, it sounds like so much work, and it's like great now. I have another thing I have to care about But it's not really that bad you start with something called a privacy impact statement Heather Burns is a Policy legal policy expert over in over in the England She's been doing a whole bunch on this. She spoke at work. Can't be you about it You start with figuring out exactly And this by the way is this is required. This is almost the law thing You need to figure out what could possibly happen. What could go wrong? And you have this that literally needs to be written down piece of paper Which again, of course is the government wants paper so and then needs to be Accessible to everybody who works on the project and Regulators if they ask for it So it's one of those things where they ask for it That's not the time to make it The time to make it is when you start the project because again when you're doing scope and discovery You're sort of doing this already. You've just never put it in one place because you're again What are the scope? What are the specs? What do I need to collect because it's for the user What do I need to do with it? Who's getting it? Like you're already doing most of this It's just been kind of piecemeal in different parts of your process most likely And again, I could give a whole talk on privacy assessment But this is the big thing. They're still evolving the law is not even done There's another part coming out There was a law that came out in 2002 essentially they called it the cookie law in the EU kind of a misnomer But that's the easiest way to describe it That's getting enhanced as well. They just didn't have time to get them both done before The GDPR came out so there's going to be even more laws and rules about what you're allowed to connect collect and not collect And what you have to inform people about Now they said whatever they do to that cookie law is going to work within the framework of GDPR They've already created so hopefully they won't put out conflicting laws But this is a big thing ignorance is no longer an excuse as we saw with a you know with the guy from from BW He probably said I was building what I was supposed to like I wasn't aware that it was you know again Whether or not he knew what he was doing doesn't matter you know, we can't be ignorant to what we're doing anymore because We're the one building it it's a hard argument to make that you don't know what you've just built I Made that argument before because sometimes I literally didn't know what I just built But almost every single time I know exactly what I did maybe I wasn't aware of it Maybe I didn't think much of it because again when I was building websites, especially when I started doing this 10-12 years ago I didn't think about any of this stuff. I barely knew what I was doing So I'm sure there was stuff going on that was probably not good for a whole slew of reasons and What I want to get into we're gonna do a lot of questions because I know there's gonna be a bunch is This isn't hard and more importantly For us to think you know these laws are coming to the US California is probably going to enact this soon. I Imagine other states probably like New York Delaware or another ones are going to also enact this This is essentially going to be the law of the internet. I would say soon. I don't know how soon but soon This isn't like that that we can just ignore it Because I remember when that came out everyone was super concerned about it Oh, we have to pay all these taxes of these weird companies never done that before in my life And I don't think anyone else ever since that happened. I have not heard another person talk about it This is different like This is people because people get upset. You know whereas that was like accountants and nobody really care Now Again, is there any question other than how can I avoid doing this? Because in Orange County, I had four questions about how can I just avoid this? And the answer was you can't So that question was gonna answer anyway. You can't Okay, and again some of this is difficult to answer because they haven't enforced it yet They haven't actually gone like they've filed against Google and Facebook and Amazon I think over the EU because that's that's love-hanging fruit. Let's be honest So You very well both could be Like it's not a single entity like the whole idea of controller and processor. It's not like you There's one like on the website. There could be multiple data processors depending on what data is being processed I would not just by them saying that they're doing it. I Don't believe would totally absolve you if something happened Especially because you built it you know, they may be collecting it, but you built the engine to collect it So you're there's something at it. No, this is legal Advice, but you might be at least somewhat involved culpable whatever the word may be so but again, it's one of those If you know what's going on Then that shouldn't be a question because it would be like, yeah, whether they're collecting or un-collecting it We know exactly what's being collected. That's the more important is who's doing it secondary. What is happening? Very much primary. You had a question. Sure Yeah, she was asking about as an agency. What is your role in? Drafting privacy policies and and things of that nature for individual clients Once at least, you know, if you're not managing the site Because like there's plenty of stuff that I've built and I've never looked at again And there are sites that I've still had my eye on or help work on for years So those are two very different things As term to the privacy policy in terms of use that would be on the individual site owner only because Their privacy and their terms are going to be based on whatever it is they're doing as a business There's boilerplate language I think core now actually when you spin up a new site it gives you a privacy policy page as a draft So if you spin up a new sorry If you spin up a new WordPress site with four nine six or above it will create a privacy policy draft page as a draft Well, you know, it makes sample page and like hello world. Well now there's hello world sample page and privacy policy and The private it's a you know boilerplate language. There's a link in there to help write one I know and that's gonna they're gonna put more stuff in there like they're getting that out before the May deadline for GDPR So, yeah, the terms of suit the in terms of use privacy policy That's gonna be a lot of stuff based on what the individual company is doing. You can definitely try to give them guidance I would not veer into the I'm giving you legal And because the onus is gonna be on them. I'm not sure your Attorney would be money well spent for them. Unless you're gonna just build that forward to them But yeah, it's it's one of those things, you know as you're building it make note of everything that you're doing and that way Because what very well may happen is you give it to the company the business. They're running it. They're lawyers like oh We need a privacy impact statement So even though you're not the one that has to handle the outcome of that privacy impact statement as the agency You're probably the only one Qualified to write it Because they don't know like most of you know all when I ran an agency for a long time almost none of my clients ever knew What we built they just knew that it worked That's all they wanted That's why they paid us. So yeah, I would I would definitely keep you know again keep all the notes of stuff and just Be ready to have it and hand it over like hey, this is what we have This is what I would give to your attorney or whoever else now again They got to come after the person selling you know selling handmade soaps. I don't know I don't think I don't believe that's going to be the initial round of stuff. They're gonna go after some of the stuff I have a sneaking suspicion is going to be if somebody complains and Someone could complain about their G you know their GDPR rights on a site that sells handmade soap Just the same way that they can do it on Amazon so The potential is there regardless of the size of your site So like obscure being small obscure isn't necessarily going to protect you You know That's not anonymous Your IP address tells me where you are Now I know that and Google is a good example because Google being that they pissed off the EU for about 15 since the EU started they've never gotten along and They have pages upon pages about how they're implementing GDPR and what you're supposed to do in your site to you know Essentially when you went to the work camp Grand Rapids site remember the little cookie thing you got in the bottom That's GDPR That's just the site informing you that they're collecting some data about you. It's again. This isn't a huge idea It's it gets more complicated depending on what you're collecting But it other than that and the analytics like that's a weird thing because they're at that point there You know you're the controller there the processor You're giving them this information by putting analytics on your site You were allowing Google to collect information which means that they collect something. They're not supposed to that's still on you because you gave them the space So you can't just throw the biggest I think the biggest thing that's going to get taken down first of those shady ad networks The ones that just inject stuff into people like those are going to get hit first Because they're the ones that are collecting user data without the site's permission or the user's permission That's the like Google is not going to intentionally break the law You know bright haven advertising very well Mac. I don't know if that's a real company. I apologize Actually you had a question that'll come to you. Yeah, this is gonna sound rough But I would tell her that I mean if it needs to be there and I don't know the policy I don't know her job. That's not important get out Tell her it stays or find another developer Which sounds harsh? But it's one of those things where The people that are pissed off about this more than anybody else are marketing Because they've just been collecting all of this data They're not even sure what they're gonna do with it. I've heard a bunch and I I'm gonna upset marketing people and I'm totally fine with that Like things like net promoter score that literally means nothing. What is engagement? No clue. I engage with things all the time That's how being a human being works. So Again, it's going to be one of those things where You know, they wanted all this data They're not gonna have it which means people that are good at marketing are gonna be even better because I actually know how to do the job And the people that just make reports saying the people engage are probably gonna get fired So if the policy needs now what I would do is I would have you know in this particular case Are you entering? Cool is the person you've got this draft from an attorney Then I would say I believe this needs to be there You need to talk to your attorney because this is important if their attorney says no Then that's not your problem anymore unless you still own the site because if it's for the client and it's gonna be them And I say ownership as in it's their site then And those are usually the worst because they're hard to say no to Yeah, and some of this again like some of the stuff may be Yeah, I would you know again it'd be one of those things where yes long-term client But I don't know what culpability you individually would have but I would definitely make a note of the fact that you Said this should be there and they said no because yeah, you can't just ask people will you give up your rights under GDPR to use this site That's not a valid pop-up. You can't people can't opt out of GDPR You can't just ask them. Hey, do you care and guess or no? No cool. We'll keep going our thing Yeah, you can't just disregard it so Again without knowing the prophet. Yeah, there's probably a lot of nuances to this particular question So I would I would suggest at least like hey, I think this should be there You need to talk to your attorney But document that save that email whatever it is You know, I make sure it's in writing that you felt it need to be there just protect yourself And that actually has him and then I'll come to you there are some and I know there's a lot more being built I've built some stuff What you're gonna want to start with is to do a site audit and Again when I ran agency one of if we took on a client that already had an existing web property That we had to touch in any sort of way part of the part of the contract part of discovery and scope was doing a full site audit If they didn't agree to that we didn't take them on as a client Because how many times you've taken on a site and then you find out that it's like held together with duct tape and bailing wire And it's yeah, so by doing that site audit because it's gonna be it can be to agree degree site specific Do that audit that's when you figure out what you're taking in because at least on your you know If it's not in the database you didn't collect it That's a kind of a it's not a hard and fast, but it's a pretty good rule to think about it If I can't see it in the database. I didn't collect it Then the second thing and this is where client where you can things can get weird when clients start adding stuff after you've built it and Especially again ad networks. Oh tracking. I want to see what the heat map looks like again All of these things are cool and there's not necessarily that you can't use them like none of nothing in GDPR prevents What we do? There's a few things like you can't sell the data to somebody else without informing somebody you know the user That's the only new thing technically that might impact you as a developer is that you can't sell somebody's data I've never sold anybody's data apparently is lucrative, but I've never done it So from that perspective it's like yeah figure out. What are you collecting? What are you collecting outside of the scope of like a core vanilla no plug-in? No theme WordPress install if you don't have registered users you're automatically collecting a lot less data You know the moment you're a logged in user you can see if you look at you know Query monitor or any of the stuff you'll see all the cookies and everything else that gets collected You can look in the user and user meta table and see all the stuff that gets collected if they're not registered users you're not collecting much on them and then as part of that site audit identify any third party that has something on your site Even if it's not inherently collect is because again those ad networks So that's where they started getting in trouble was they would show the ad but they were scraping all this user data as people came Never telling anybody about it That's not legal But you have a very particular quite yeah So there's a combination and that's one of the biggest things that I haven't seen a hard and fast rule about How do we get rid of somebody's data because that's part of it? You have the right to be deleted or Erased or forgotten whatever words they want to use and that came up and I think I was skipping over quickly. I Have no way of knowing with Facebook I they clearly didn't delete my email address because they wouldn't let me use it again And that was ten years ago almost ten years ago So and they as of yet I have not seen anything that will indicate the proof that it's been deleted So some of that is still going to be on trust for now until they can figure out how to prove it When it's things like Google and a little you know by removing Google analytics You can you know a you've removed the source but also and this is where a lot of it comes down to I've never looked at analytics on some sites that I've installed it on ever. I Have a site that I've had running for 11 years and had analytics since day one and I've looked at it twice. I just deleted the analytics and Removed it from the site and I solved the problem now and going forward now I'm aware that you can't do that for all of your sites for most of your sites probably But go back into your Google analytics settings and make sure that you're following along with what they've outlined because again Google has pissed off the EU since the EU began They at least make an attempt to not be flagrant about the fact that they don't care about the EU so I Would start there and then I know that again. I know Google analytics. I believe has a way for Deletion a deletion request and it exists legally it has to where they bury it now I couldn't tell you because they keep moving things, but In that audit that I mentioned that's where you're going to identify what third party even exists Because then it's like, okay, if it's this company Let me see if they have a thing on their website that says how to delete it If it's an API call if it's an email if it's a phone call And if they don't have anything That I would possibly look at maybe replacing it because if you're using a third party that has not even mentioned GDPR That's probably a bad sign Because everybody has mentioned you know, you know those 9,000 emails you got about updated terms of service. Yeah, that's why you got them GDPR and I say yeah, they don't know how they're gonna afford. I mean I wouldn't specifically because going along with a lot of those packages Two people aren't collecting the same data Like how I have my analytics configured is probably different than yours So you may be collecting things at certain places at certain times and I'm not in vice versa So in particular, I would look at service and what they provide some stuff It could be as simple as we just throw this information away after 30 days So there is no data to collect or we aggregate it in a way because again the EU cares about aggregation Whereas the US doesn't because the EU understands that 10 people collecting 10 bits of information makes a complete profile of a person Even if those 10 pieces individually don't Which makes sense. We just don't do that because we don't So yeah, it's really look into the individual pieces that you're allowing on the site and how they are going to approach it because again It depends also what's being collected Yeah Yes I Kind of can make that a little bit concise the idea that as a developer I used to collect as much data as I possibly could because I figured I might need a leader. I didn't know if I was going to use it But I figured the more I had the better it would be so I could do something down the road and I would have a complete picture That's not how to do it anymore I only collect what I absolutely need and can justify having because if I can't justify having that data I Probably don't need it. I got time for one more question He had his hand up first. I promise I was yours later. Yeah. I'm sorry Drop shippers. Okay. Yep Yep That's a great example of how you can be both by the way Maybe and some of this is going to be like when was it collected because if you collected this data in 2014 I don't think there's a reasonable expectation that you would have been following a law that hadn't been written yet I'd like to think however In terms that you know and especially legacy software is going to run to a lot of problems with this because Depending on that ERP system. It could have been written 10 years ago And most like most enterprise software I've written is not new So I would look at those you know because they again, they have to be following this stuff Especially e-commerce I would just and you know if you're doing e-commerce implement this like it belongs to everybody whether than the EU Or not solve your problem now. I'm going forward So for that I would first review what you've got and be like alright. Do I need that order from four years ago? maybe maybe not I Believe that like at the bare minimum I would Back up everything up until the day the GDPR went into effect, which is I think May 25th Save that somewhere like this was our pre GDPR data I don't expect it to be okay And then see what you're tracking going forward and then I again talk to those drop shippers and vendors and be like What are you doing with this data? Because most of them are yeah, we have the address we make the thing we send it out That's all we do and most of them that's pretty easy to follow because we have the stuff You know and then do they have a way for you to say hey delete this person out of your system most of them Maybe it's a manual thing right now until the software catches up So if you don't see anything on a website or you don't see anybody help them you can always be like What do you know email recall? What are you doing about this because they variable could be like? Hey, we have a plan. We're waiting for the nerds to finish writing software You know that could be their answer and that's a valid answer like we're trying to get the software to catch up to You know cuz the cuz JPR was two years in the in the works We didn't start carrying until like a month before America, baby Yeah, so we didn't know it's like we had two years to catch up to this and we were just like whatever Americans so Yeah, it's now something that like we had a lot of time to catch up and we didn't do it So yeah, just kind of look at what you're doing audit your stuff figure out where it is And then you know just be mindful of what you're doing because again It's a lot of it's gonna be good faith stuff where if you're like, oh, I didn't realize this was being collected But I bought you know as opposed to hey, I made a backdoor Trojan for all my users to you know Scrape data like again very different goals and outcomes which EPR applies to both So thank you


Now the basic definitions of logarithms are all you really need to know to be able to work with any sort of log, however it's convenient to have some shortcut methods, and this leads to what are called the rules of logarithms.  Well, the logarithm is an exponent by the definition of what a logarithm is, the log to base a of x is m, here's our base, here's our argument, here's the actual log, base argument, actual log, so log to base a of x is m, log to base a of y is n. By the rules of exponents, if I multiply x times y, they have the same base, so the exponents are going to add together. If I divide them, the exponents are going to subtract, and if I raise one of them to a power, then I'm going to get the exponent itself multiplied by whatever that power is. And because logs are exponents, this gives us a set of rules for working with logarithms. So the log of x times y is the exponent, m plus n, but m is the same thing as log to base a of x, n is the same thing as log to base a of y, so I can replace them, and I have my rule for logarithm of a product. Likewise, if I take a look at a quotient, the log to base a of x over y is the exponent, m minus n, but m is log to base a of x, n is log to base a of y, so that's going to be the difference of the two logs. And finally, the log of a power, x to the k, the log is the exponent, mk, and again m is log to base a of x, this is going to be k times log to base a of x. And so here's our three rules for working with logs, which we often say the log of a product is the sum of the logs, the log of a quotient is the difference of logs, and the log of a power is the power multiplied by the log. For example, let's say I take log to base 7 of x to power 3 times x plus 5 raised to power 5. So a little analysis goes a long way. So the first thing we should do is we should try to determine what type of expression we have, what type of expression is the argument. So let's take a look at that. That's a product of x to the third and x plus 5 to the fifth. So this is a product, and so that says I should apply the product rule for logs. Log of a product is the sum of the individual logs. So my first simplification, log of a product is the log of the first factor plus the log of the second factor. So there's my first step. Now we want to simplify as much as possible because later on this will become really, really helpful. I have my first expression here, x to power 3, that's a power. So I can apply the power rule for log of the power, the exponent becomes a coefficient. So this log to base 7 of x to the third, that exponent 3 is going to become a coefficient, 3 log to base 7 of x. The other term is also a power. So again, I can apply the power rule. That exponent 5 becomes a coefficient, 5 log to base 7 of x plus 5. And what do I have? Well, let's see, can't do much with that. Here I have the log of a sum. And well, x plus 5 is a sum. So I can apply the sum rule for logs, which is log to base a of a sum, is log to base a of the sum. In other words, if I have a sum, I can't simplify it any further. A sum cannot be simplified using logs. And that means I can't do anything else with this. I've already done with that. And this is the, as far as I can go with the simplification. Well, here's another one, log of that horrible thing. And it doesn't actually matter what the base is. The rules of logarithms hold, regardless of what our base actually is. So again, a little analysis goes a long way. What we have is we have a cube root. We're taking the log of something, something, something, cube root of something. And so cube roots, I can express these as powers. This cube root is the same as raising things to power 1 third. So I have a power, and now I can apply the power rule. The log of a power, the exponent comes out front. So this 1 third is going to become a coefficient. 1 third log of 3x plus something over 2x minus 5. And parentheses, like paper, are cheap. So we should go ahead and use them, throw that into parentheses. This is important because it's 1 third is the exponent of the entire expression. So 1 third should be the log of the entire expression. So again, a little analysis goes a long way. This is the log of a quotient. So I can apply the quotient rule for logs. Log of a quotient is the difference of the two logs. So that's going to be log 3x plus 7 minus log 2x minus 5. And again, we're taking the log of a sum and the log of a difference. And they cannot be simplified any further. The log of a sum is the log of the sum. The log of a difference is the log of the difference. And there's nothing else we can do with them. So at this point, we are done with our simplification. Well, let's evaluate a logarithmic expression. So here I want to evaluate log base 2 of 12 minus 2 log 2 base 2 of 3 plus log base 2 of 6. So, well, let's see. I don't know what any of these are immediately. So maybe I can figure something out. Let's analyze the type of expression we have. This is a sum. The last thing we do is we add things together. So this is a sum of logarithmic expressions. And so I have the sum of logs is the log of a product. However, notice that when I add this sum, there's no coefficients here. This is simply the log. Simply the log. I'm not allowed to have coefficients. I can combine them as a product, but I can't have a coefficient there, which means that this 2 is going to be a profit. So I have to do something with that. Well, I can get rid of the coefficient by using the power rule. k log base a of x, that k, that coefficient, can become an exponent. So this expression here, I could rewrite this 2 log 2 base 2 of 3. This is log base 2 of 3 squared. That coefficient 2 has moved inside as an exponent. And now I have a sum and difference of logs. And I can use the product and quotient rules. So this is log of a difference is a quotient 12 divided by 3 squared. And now I have the log of a sum. And I can use the product rule. Sum of logs is the log of a product. And I can do a little bit of arithmetic. And I can do a little bit more arithmetic. And a little bit more. And a little bit more. And I now have log to base 2 of 8. And I can make a final reduction by remembering that 2 to power 3 is equal to 8, or computing that 2 to power 3 is equal to 8. So remember, log is the exponent. The base is the base. The power is the argument. And the actual value of the log is the exponent. And so log to base 2 of 8 is equal to 3.


Okay. Well, this was more of a teaser title than anything else. No, my intention is very straightforward. You guys have had a very, you know, sequence of technical talks. So what I wanted to do was to have something completely different. So essentially the question I wanted to ask is, and that's why I thought, you know, I'll go be the last one, is to have a kind of a panel or a forum or whatever to see, ask, to answer a few questions. So the first question I have is, and I don't have it up on the thing, I should have put it there, is why do you use Git? What has been your motivation so far? It's for you to answer. Why do you use it? Or... Yeah, you said you tried, what else? In other words, CJ, you have a lot of stuff that you use Git for.  Where do you think you fit? How many would say 50% of the things you do, not programming alone, is using Git? So programming in documents. Documents. Okay, what else? Anything else you think you would have loved to use but you cannot use it? Images? Give and save files. Yeah, config files. Config files? So do you think that's one of the things, I've spoken to a lot of people and config file seems to be one of those things that will be very, very useful to keep track of. I mean, we all try to do it. Or your .files and all that. Is there something that you think... Dropbox. Did you just drop? Your files into a Git directory. There's two. Oh, is that right? SparkleShare. SparkleShare. It behaves like a Google Drive, one drive, dropbox. You drop your files in. Into a .git directory. So it goes out too? It depends on where you set your remote as. Oh, okay. For example, you can have as many as you want provided that they all have individual remotes and your remotes. Whichever hosting a service you're using allows you to share that size of data. So if you have a habit of dropping images, large AI file files, it will not make very much sense because you run out of space very quickly. It doesn't change and because Git doesn't forget, in that sense it doesn't behave the same way as a dropbox. It does keep track of everything which it does. So, you know, one of the things I've loved to see is Git being a standard way into tools like, you know, office tools. Like LibreOffice or something like that. Because I think that's where there's a lot more value that we can get out of Git. So, what do you think we can do with that? That's one area because the reason I put for Git for my mom is for those of them who are not doing any of these things. They are using their spreadsheets. They are using their word processors. How do we get them to be able to do version control? Because I see them sending emails with attachments and this version to the name of the file, dash, mine, or dash, you know, my boss. We know there's a better way to do it. So, what can we do to put that in there? So, I like the idea of the .Git directory. I mean, maybe that's something which I don't know whether that's a good one. What else do you think we can do? Do you think this could be a project that we collectively... Sorry to think of. Instead of sending around a zip file, you could send a packaged archive, which is a git. But the tooling you'd need around it so that people could extract it and use it. It's all there, but it just needs to be... Yeah, it has to be put together. Yeah, so that's my question. That's one of the things I would love to see happen. Because then we have a whole new group of people coming on board and actually using it, not knowing that they're using it. I mean, that's really... it has to be very transparent. But all the benefits they get, but not necessarily the confusion or the pain as it were. So, I'd say one of the barriers to this is the fact that even mainstream Git users, or advanced Git users are mostly using a centralized store. They're not really distributed. It's where you'd share a document, where the boss needs to see it, where you see everyone's editing it. It's possible to merge all those changes. But I think the orchestration is still kind of tricky. So do you think that's something that we can try and build? It's a suggestion. It's what I'm putting out there. I think if you have a repo that's a SQL document, it's totally doable, yeah. But it's a SQL document. But there's a real difficulty in trying to make sure that that would happen. But if you combined kind of DHT kind of distributed hash tables and blockchain kind of idea, plus... I don't think it's interesting. Directly graph storage like Git, you can have these kind of things, but ultimately you end up with a... I think like a magnet leak, basically, but it's... It's like a torrent. It's also... yeah, it's basically... It's like a torrent. It's a torrent, but it's a changing torrent, right? So a torrent is a static resource. We're talking about a dynamic resource that you have... Basically, you need a front-end header key plus the change key. And it could work. But do you think... I mean... You've got to socialise it. Yeah, you have to socialise it. So if we as this meetup group starts experimenting and trying something like this, simple enough, easily packaged up, delivered via plugins or whatever, as the equivalent may be, into any of those tools. It starts with a simple set of tools. I think an office product is probably the best way to start. So just to get them socialised, get them to start using it and see how it goes. Because then I think the value of Git itself, it becomes so much more useful and a lot more people begin to... But they may not fully understand it. But that's okay. But they benefit from it. The understanding may not be there. So that's my first question. So what are the kind of things that you could possibly be doing? The second question I had was... You guys... I'm making assumptions here. You're all upstream contributors in whatever you're doing. Am I correct to assume that? Okay, so upstream. In other words, your organisation has got no issues in making that happen. So do you have projects that you work on, internal to your organisation, that are not upstream at all? Or is everything that you do all upstream? That's my question. That was my second question. Can you elaborate a little bit? Yeah, so the reason I'm asking that is I'm trying to find what kind of mental conflicts do you have when you have to split your mind between what is really upstream and what is sort of internal, even though you may be using the same tools. Because I find that that's like having to keep track of different things in different places, mentally not... Because in an open public environment, if you make stuff, you make a mistake, that's okay. I mean, you can always fix it. But what if you took what is meant to be internal and you put outside accidentally? So you have to have a firewall in your mind to keep track. Is it upstream you mean user facing? Well, it doesn't matter. I mean, any upstream project. Like public? Yeah, public. Yeah, when I say upstream, I mean public. Yeah, not internal. You want to pre-push hook for that? No, it could be something that you may already do automatically for yourself. I find it very difficult to keep track of that. So, I mean, the classic case is credentials. Not pushing credentials to a reproduction. Also private branches. So, did you have any horror stories about that kind of stuff? I'm sure. Yeah, yeah, sure. I'm sure. 20. So, in the company I work for, we have GitHub Enterprise. Okay. So, it's internal and no one can access it from outside. There has been cases where I developed accidentally purchased a public GitHub. It's still very random. And there is an activity that actively scans public GitHub, big bucket, and GitLab. Oh, seriously? All these repos of this. Wow. So, it's a gigantic project involving thousands of servers, but there's just one thing that they do. Oh, that's a lot of... I don't know what the name of the software is. It starts with black and something else. I think it has something. Black, black. Sounds familiar. Anyway, what it does is it doesn't just find Git hashes. It also finds snippets of code. So, sometimes people do take an entire fresh repo and make a brand new commit output. And that gets black as well. So, even if you put it on Bitpocket, including a private repo? Well, obviously, if it's a private repo... So, it's only in that industry that I have it. Yeah. I guess this is one of those horror stories that I've not really mentioned or talked much about. I mean, how real is it? And how prevalent is it as a problem? Because it's actually, to me, it's keeping your presence of mind to exactly what you're doing at the point in time. Unless you say, okay, I only do public upstream projects in the morning.  Oh, anything in the afternoon is always internal or something like that. If you're going to mix and match, then... Generally, if I have a situation where it's a very project that I push both to internal as well as external GitHub, I would usually prefer to put them as separate records, as in separate working directories. Or your own system, that's essentially... Yeah. I mean, that would be like the best practice, right? Yeah, that's the best practice. So, when you do a git push, it's only pushed to wherever. Yeah. So, do you use pre-push hooks? Sorry? Pre-push hooks. For... Even for LinkedIn and... Well, for LinkedIn, but I mean, you use a pre-commit hook for LinkedIn. But pre-push would be... You want to protect certain branches. So, okay, some people, no master pushes. You've got to push to an absolute... Yeah, right. So, if you have that, it's fine if you're the only one using it, but usually you have to manage a team of people. If you usually have a privacy hook on the server side... Yeah, if you've got server control... So, if you're on GitHub, you don't have that. Yeah, they control. But yeah, I mean, you could do all kinds of scanning on a pre-push, depending on... But to...  Correct. But there's an overhead no matter how you slice it. Except after probably years, right? Don't have been. Generally. That's a big picture. The other thing is, if you don't think about it, how do you even know you can do it or not? So, the largest problem is just people who are not aware that they could be doing this.  The biggest problems online always happen because people are just unaware of the dangers. So, it's... So do you think there is an opportunity to educate and teach or... You know, that kind of... I wouldn't call it best practice, but behaviour considerations to make sure that you don't do that. This is your therapy session, right? So, this is... Get up anonymous, right? That's good. So, we do have a couple of options here for me. I mean, the question of... Temporal separation is probably one way to do it. I think that does make sense, right? Pair programming. Pair programming? Yeah. Pair programming, I think it's probably... The challenge with the bank is that... I would like to... Generally, the projects that are meant to be public, they are... They are usually... Usually, most people only have one remote, which is whatever origin they are, and they usually tend to be public or internal. And these days, in terms of package management, we depend a lot on package management to help us with pretty much everything. So, that is one of the common practice. So, for... No... No, especially, it's most relevant for it. You deploy everything through no packages. And there's a public registry you depend on to download. Unless you guys remove somebody upstream. Unless... They are pissed off on a private matter. Like the last pet incident. The point is that... Don't depend on Git for deploying software. You depend on... Which have dedicated package managers to handle it for you. Ubuntu, you have... Debian packaging, and with Red Hat, you have YAM. DNF, right? DNF. DNF. Whatever that stands for. So, what about the other... That's the other thing, right? I mean, with all these ideas of containers and stuff like that. So, where do you think that would be? How do you think that would be?  Git-like feature set or features, but it behaves like you add your different layers on top of it. So, do you think that's something that could help in... You switch to a different container for that purpose and it's probably just, you know, locked down to only to go to a particular place and nothing else. So, you don't make a mistake. Letting the system anticipate that issue rather than best practices. I mean, if it's the same command line, you just... Well, container is just another... I think it's more complicated for developers. You think so? Right. It solves that problem, but it also introduces a whole stack of different features. Yeah, sure. I think all of it ends up indirecting education. So, you either jab it or you shouldn't be allowed on that system. It goes back to the same question where should you rebase or should you merge? Yeah. We're not starting there yet. We're not starting that discussion, but at the end of the day... We're just referring to just one point or two points. At the end of the day, whether you are going to encourage your team to perform rebase or merge, nothing beats actually educating them what the tool action actually do and how they're different and give them the option to choose when they want to do a rebase and when they want to merge. Yeah.  Yeah. But also have very hard rules about certain other things. So, you know, please don't push all of our private keys into your gist. Yeah. But it's a secret gist. No, it's not. Okay. Out of curiosity, how many of you work on open source projects exclusively? Really, as an exclusive? In other words, there's nothing that you create even in your organization that is private repose. Everything is public. Don't think many companies can have that privilege? Well, some can. We have. We have that privilege. Everything's in public. So, I'm just wondering, in this audience here, how many of you? I assume no. None. We encourage open source contribution. If you... How is that encouraged? How is it encouraged? What is the... What is said to make it encouraged? Perks, fame, some publicity. You get a free t-shirt. Well, you can print t-shirts and distribute them for your open source project. It's covered by the company. That's better than we want. So, no, which is quite common. So, my question here is... And this is where... You know what I should do? Do I have it in here? Let me just quickly check. It's actually a slide that I want to show. I forgot to put that in this deck. Hang on. Let me just get that. Okay. It's the wrong one.  Let me show you what we have. Oops, the wrong one. Okay. This is something that we have within Red Hat. And this is a... It's a document about code of business conducts and ethics. And in this document, it's about three or four-page document. It's available online. You can have a look at it if you are interested in reading it. We have to sign off on this every year as an employee. And when you join us for the first time, I put this paragraph out here because this is the basis for everything that we do. So, it's essentially a participation and open source project, whether maintained by the company or another commercial or non-commercial entity or organization does not constitute a conflict of interest even when such participant makes a determination in the interest of the project that is adverse to the company's interest. So, in English... That's awesome. Yeah. No, absolutely no issue. Essentially, in English, that's a project. You are at a decision tree at some point to go via A or B. A is the right thing for the project. B is social for the project and you are a member of the project team. You happen to be a Red Hat as well. And it turns out that A is actually negative impact on Red Hat. But B is kind of neutral to Red Hat. So, what should you vote for? This says vote for A. Make the project succeed. Let Red Hat figure out what to do. Not against you, but let's figure out what to do to manage this because the argument and the understanding is we want the project to succeed because the project is a weaker thing than a company. Technically, a company is a little bit stronger than a project because projects come and go. Projects can die. Projects can have issues. I really don't interpret it that way. That's what it is. That's the reason I'm still here. Otherwise, I won't be here. But surely legal conducts this any way they want? No. If that is the case, there will be a lot of people who will say, Sayonara, you're not interested in this. This is fundamental to what we do because this gives me the freedom to do what I need to do upstream. And this is something, and every year, by the end of the calendar year, we have to online click, click, click ESDS that you've read this document. So, the only thing I read in this document is whether the paragraph is still there. In the last 14 years I've been here, it has always been there. It's been clarified and made shorter, but the idea is still the same. So, to me, this is a very fundamental, so this is the question. In your employment contract or your code of ethics or whatever that you may have signed up to, assuming you read them, what's a clause like that in it? Because this determines how you can contribute upstream. Because you don't have to look back on your shoulder and say, can I do this? Can I do this? Just do it first. Make it happen. And let the business figure out what to do. Not because you did it, but because that's what the business has to figure out. Okay? So, this is something which I would like you to think about. So, let me go back to what I wanted to show in the first one. Oops, sorry. So, the only pitch I have is for Red Hat, like my colleague came here earlier. So, jobs.redhat.com is where you are. If you're interested in anything at all, please look at that. I'll send an email to jobs at redhat.com. The challenge we have, and I can tell you this here, we don't have 100% type of engineering type of jobs in the Singapore office. But that does not mean there aren't any available. Where they are, if you are in Singapore, it will be remote. So, you will be a remoteee to a project team or engineering team or quality assurance or whatever the team that you think you want to be part of. So, I think that's great. In other words, you don't have to be in your office to do get anything done. You come to the office when work stops, right? It's wherever you are, do whatever you need to do. So, think about it if you're interested in it. And I guess the last one is just this. I'm sure you've seen this. Quick question. Singapore is the only office in the region? No. Red Hat is organized in this part of the world. We have six regions. Singapore happens to be the Asia-Pacific headquarters. Also, ASEAN headquarters and the Singapore office. Plus, all the overheads, HR, legal, blah, blah, blah in the Singapore office. In ASEAN, we have it in Malaysia, in Thailand and Indonesia. Actual offices. That's within the last two years. We never had them for all this while. So, it's always there. And engineering happens out of Pune, Bangalore, Beijing. Beijing, we have two offices for engineering and Brisbane in Asia-Pacific. So, there's always opportunities. You name it. So, I would encourage if you're keen on looking at anything, like exploring, please have a look at jelps.redhat.com. If you find something, if you think that's interesting, there's a code for it, whatever the job ID is, send me the link, because then I can make a referral for you if you're interested. So, with that, this is the last slide I have. So, I kind of like this one, because I've seen it in many offices on a front door. So, not the back door, but the front door. If that's a case of fire, get commit, get push, and leave building. Do not go on social media. That was supposed to be in there somewhere, but... So, with that, thank you very much. If you have any questions, comments, or anything that you want to discuss. I like the first part. To see what we can create, I would love to see something like that happen. For mom.  The get commit and the get push need to have dash dash, no verification. So, file up here, file up here, and yeah, that's a good point. But that would be too long for the guy to put, and by the time he goes to the back of the door. So, I think it would be good if we can create some kind of a tool to get one project. So, I don't know what it is that we can do. I don't know how you want to drive this. I think it would be interesting to experiment and try build something, because otherwise moms won't get into the picture. And it would be kind of nice to have them in the picture as well, so that we talk the same language more or less. Well, within inverted commas, right? All right, thank you very much, guys. And thank you for coming to Rehab. Thank you.


Hey everyone it's Gabrielle and Kenny. We're over here today at Oxmer Toyota and we're going to go over some details on the 2021. This is the Toyota Tundra and this is the Limited. And this is in the beautiful cement color. It's a very rare color to get. So the cement color used to only be on the Tacoma TRD off-road. I know because I had one. I loved it. And we still have those now back on Tacoma. We started playing with them on the Tundra recently. 21 Limited with the TRD off-road package. Alloy wheels. There's skid plate under here. And there's a lot of stuff that you're used to with the Tundra. But there's a lot of stuff on the interior that I don't think most people are aware of. That's actually what we're going to focus on today. We'll still give you some of the exterior stuff with it. But on the inside it's a completely different, almost like a luxury truck on the inside with all the features. So let's do a little quick walk around the outside Gabrielle and then we'll get inside and show where a lot of good stuff is too. Alright that sounds great. Let's go.  Also the LED fog lights. So there's that silver grill with the chrome surround. Absolutely beautiful. Now there is a skid plate under there. So our cameraman is trying to get that right now. So this has a 5.7 liter V8 381 horsepower and 401 pound feet of torque. There is a 38 gallon fuel tank which is the largest in its segment. Now for the wheels you have an 18 inch five spoke alloy wheel. There is the classic black running boards. So you have the bedside TRD off-road decal that you can see right there. Also have the chrome limited badging on the side. So there's the spray on bed liner and the bed is actually a five and a half foot short bed. There is the remote tailgate lock. Now this one it's available 10,200 pound towing capacity. As far as the payload capacity you're looking at an available 1730 pound. Now guys why don't we move on into the interior. Alright guys so you have an 8 inch touchscreen. You have the premium audio with dynamic navigation. It has the JBL and so there's nine speakers. You have the Apple CarPlay and Android Auto. You guys have a leather trim steering wheel. So it's going to have audio multi-information display. So you'll have like your Bluetooth, voice command, dynamic radar cruise control and lane departure information. So that's really nice to have. So there's leather trimmed and heated front seating. Then you have the leather trim seats in the back. Now it's really cool you guys. Very very unique. You're not going to find this in many cars. Is a safe and this is by console vault.  In that combination you can put on your own it's set to 4-0 so you just create your own combo just like a regular safe that's kind of neat. Yeah that is awesome. So if you haven't set in a tundra before one of the things that I really like is how much legroom you have. So from the top of my knee to this dashboard I'm going to tell you it's probably about seven inches and I'm 6'2 so that's quite a bit of room and the back is even more. I mean you've got room for two or three people six foot five back there so tons and tons of room in the back. I'm going to pan back there one more time past Gabrielle and you can see the amount of legroom that you have there. So this is a full service vehicle if you've taken a road crew or anything like that you have no problems in this one. No not at all. One more thing I want to touch base on is some of the safety. You do have the Toyota Safety Sense P so that's going to include like pre-collision system with pedestrian detection. You have lane departure alert automatic high beams and the dynamic radar cruise control and there is eight airbags in here so that is awesome. Yeah very safe vehicle. Five star safety rate as you would expect from Toyota. Yes. And the tundra as we saw last year maybe it was two years ago someone had taken one for a million miles so. Yeah that's right. All right guys so that was our walk around on the 2021 Toyota tundra limited if you have any questions if you'd like to stop in take a closer look take it for a test drive let us know all of our contact information is listed right here. Thanks everyone for watching I'll see you all next week. Bye guys.