 , నిన్టి నిన్ని, వ఩రామౕ ఏుచై, గాసానిని మెలెట్ప్తరారిక్. ముడేముతాల్ను . నారిమిన్తరిఏ. నారిలోలుతరాతరుని. గరికారోమినినిలూలండిటరానినిమండం ది విరిఫానిగంన౿లినియ౔ మపసందలికాఉకానిక౿ ఇమంసతిక౿ లియానినిక౿క౿ కిటూనీట. uh uh is going to help your development workflow. The first mistake that I want to tell you is that a developer should not enable debug mode. This is disabled by default. If this is enabled, then our error will be found out and the catch-cord is very bad. Finally, we will have less time. The first thing that a developer should do is to activate debug mode first. By default, it is disabled. Our first thing to do is to locate the WP config file and set it according to the variable shown on the screen. Do this first. The second thing that I want to tell you is that it is a security issue. A developer should not consider security while coding, but it is very important. WordPress takes security issues seriously. In most of the sectors, where a developer has a common goal, it is to not sanitize, validate, or use WordPress non-seize. It is not to maintain a secure coding style and it is not to use any powerful password for file and database. So, our first thing to do is to sanitize the data. Our user input cannot be trusted by the developer. Our first thing is to sanitize the virus and bacteria from our data. Then, we will validate it. It depends on the client-side validation. But it is very important that the client-side validation will have a server-side validation. Data validation and sanitization cannot be a security issue when there is an SQL injection, XSS attacks, etc. So, there is a problem of saying sanitize early and escape late. First, you have to sanitize your data. Then, you must validate it. Then, when you see the user, you will obviously escape. In WordPress, there is a built-in sanitization function and an escaping function. If you follow our plug-in development handbook, then you can easily search for it. Then, you have to take a security that will not use WordPress non-seize. It will focus on functionality and will ignore non-seize. So, what is non-seize? Non-seize is a cryptographic term. Non-seize is a number used only once. It is a token that is used in my WordPress form and request. It is an extra security layer. It is a token that is used in my non-seize. It is a token that is used in my user request. My user request is a trustworthy source and we can identify that from it. This is something I can do when using non-seize. It will reach to several ways, when using non-seize. We can use non-seize , ShelterOUL ... Weight Percase... ... 6.2% loss of weight if your search uses PV or mouldowing闺 bug in development to this is not a recommended way. So, when we enqueue, what we can enqueue in the file we can enqueue an example is that if we enqueue on a particular page then we can enqueue on this page. And we have some tips for CSS files. We will definitely test our CSS and JS files to minify a single file and if we use CDN then definitely our performance will be improved. A function that chooses the full name is a common mistake. We have mentioned this in many developers that a good function name is self-documenting. A good function name is actually what we can mean in this place or this function can be explained in a good way. A good function name this is not a recommended way. It cannot be a good function. But if we see this then it will be a very good function which is understood by the name of this function. What we actually want to do is to recommend our plugin prefixes. Which is a common function name used by our market every day. If we use a common function name chances are high that our plugin name can be collided with some of these. So if we use the wordpressure recommendation and choose the right way then definitely it will be collided with the plugin. This is what we do. We mostly work in a team and we have an opportunity to work in a team and the most important thing is we forget the code itself. We have to see some day what we actually want to do. So in that way we can document it with some comment in some code blocker or in some other file where our documentation collaboration is easy and we have to maintain it very well. There is a common mistake which is to do unnecessary database query. This will definitely pressure your page speed loading speed is much higher. So our database query as much as we want to optimize some of the optimization techniques which we can use batch processing like caching then our user experience will definitely improve and we will load the pace. Finally we have to keep in mind that we don't follow the wordpress guide line all the WordPress developers and developers we always follow the best practice which will be secure and maintainable. I want to talk about some useful tools which are query monitor, debug bar, toolkit, RTL tester, user switching debug log. There are many other things which are very common in Laravel which will help our debug tool and query monitor tool can be very helpful for us. I am very happy that there is no Q&A session in Lightning Talk. You have answered many complex questions but still if you have any questions then you can meet me in person or just knock me here. Thank you everyone This is Mushurma Siddiqui. Enjoy what comes in it.