 All right, so I'm Micah. I do have at the bottom here if you haven't already noticed a link to the slides if you want to Take note of that real quick It's just link dot WP scholar comm slash WCAVL, which is the word camp Asheville hashtag dash 2019 dash standards So you can get it all the information here. So Who's familiar with WordPress coding standards in general? Okay, so basically I'm just going to cover real quick what they are And essentially to kind of understand what coding standards are we're going to take a look first at coding conventions And really all a convention is is some general guidelines that we as developers have realized are probably good things to do They result in higher quality software And so everywhere you go everyone every individual is going to have some Conventions that they use in their code or the way that they work with their code That's kind of a best practice, right? So these are the conventions, but not everybody necessarily agrees on these things, right? Everybody has their own opinions and ways of doing things but coding standards are essentially Conventions that have been formally adopted by a group or an organization, right? So when we say the WordPress coding standards, all we're really referring to is the fact that WordPress The organization as a whole The community everyone involved in contributing to WordPress itself has decided on some standards and The ones that we've documented are the coding standards and things that we're going to follow. So So that's all we're saying when we're talking about WordPress coding standards And of course as a plug-in author or a theme author You might not necessarily want to follow the WordPress coding standards to a tee because they're technically for WordPress core development So there could be some things where you may want to deviate a little bit here and there But as a general rule if you're working in the WordPress space the WordPress coding standards are a very good place to start They may not meet your needs perfectly, but the important thing to know is Each team in each organization gets to decide that so if you work in an agency and you have your own version of Standards that's perfectly fine It's not one-size-fits-all right So you want to make sure that you adapt the coding standards that you use to how you in your organization or team work and of course standards can change over time as A father of four children. I really like this. Please excuse the mess. We are standards have lowered with each child, right? So as your organization changes as your team changes Maybe you get more Different types of developers from different resource places that can impact, you know, maybe how you formulate your standards and things So just important to know that it's not one-size-fits-all and you can change anything about them You can exclude rules things like that So why should we use them? The ultimate reason is because it's going to make our code easier to maintain easier to debug and Hopefully easier to add features as well And that's the general guideline as to why we would do this more specifically There's a lot of benefits, right? So one of those is that your code is going to be more consistent obviously if you have some sort of tool that's looking at your code and Hey And there there are my four kids right there so and my wife So so the code is going to be more consistent So when you have something that's scanning your code for you and and saying, you know, there should be spacing here You should use tabs. You should do this Your code is going to naturally be more consistent in the way that it reads Which is going to make it easier to read, right? So think of it as when you're reading a book if someone mushed all the paragraphs together and didn't indent them It's going to be a lot harder to read But we have basic guidelines for how people put books together We put spaces in between paragraphs and if you don't do that you end in the lines So you can tell where the next thought is occurring, right? So it's same idea you if you can Provide general structure to your code. It'll be a lot easier to read One of the nice things about things like code editors is you can actually tell it to auto format your code based off of your standards Which means that you can take something someone else wrote that is an absolute mess And if you are charged with maintaining it, you can just reformat the whole thing in one go And then work on it from there So another thing is it's going to make collaboration easier. So obviously if you You know are trying to get your code to a point where it's a little easier to understand It's going to make it easier for everyone to kind of pitch in especially if they know not just Especially if they can know what the expectations are moving forward as to how the code should be written and how it should look and It's going to make your code more secure and the reason well I say