<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: zonaetmunna</title>
    <description>The latest articles on DEV Community by zonaetmunna (@zonaetmunna).</description>
    <link>https://dev.to/zonaetmunna</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F777232%2F6ca78570-f4fe-4d4d-a4c4-67d2a7135cc8.jpeg</url>
      <title>DEV Community: zonaetmunna</title>
      <link>https://dev.to/zonaetmunna</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/zonaetmunna"/>
    <language>en</language>
    <item>
      <title>Clean code: principle and best practice</title>
      <dc:creator>zonaetmunna</dc:creator>
      <pubDate>Sun, 15 Oct 2023 04:42:24 +0000</pubDate>
      <link>https://dev.to/zonaetmunna/clean-code-principle-and-best-practice-3fog</link>
      <guid>https://dev.to/zonaetmunna/clean-code-principle-and-best-practice-3fog</guid>
      <description>&lt;p&gt;Clean code is a concept that refers to writing code in such a way that it is easy to understand, easy to maintain, and easy to modify. The principles and best practices for writing clean code can be summarized as follows:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. Meaningful Names:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Use descriptive, unambiguous names for variables, functions, 
classes, and modules.&lt;/li&gt;
&lt;li&gt;Avoid disinformation (e.g., using a variable name l that looks like 1 or I).&lt;/li&gt;
&lt;li&gt;Make meaningful distinctions (e.g., getUserInfo vs getUserData).&lt;/li&gt;
&lt;li&gt;Use pronounceable names.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;2. Functions:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Functions should be small and do only one thing.&lt;/li&gt;
&lt;li&gt;They should have a small number of parameters, ideally no more than three.&lt;/li&gt;
&lt;li&gt;Function names should describe what they do.&lt;/li&gt;
&lt;li&gt;Functions should not have side effects that are not obvious from the name.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;3. Comments:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Comments should explain why something is done, not what is done.&lt;/li&gt;
&lt;li&gt;Avoid redundant comments that just repeat the code.&lt;/li&gt;
&lt;li&gt;Update comments when code changes.&lt;/li&gt;
&lt;li&gt;Use comments to mark incomplete code or areas that need improvement.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;4. Formatting:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Code should be consistently indented and formatted.&lt;/li&gt;
&lt;li&gt;Use blank lines to separate sections of code that are logically related.&lt;/li&gt;
&lt;li&gt;Follow the coding standards of your team or organization.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;5. Error Handling:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Use exceptions rather than return codes for error handling.&lt;/li&gt;
&lt;li&gt;Don't ignore exceptions.&lt;/li&gt;
&lt;li&gt;Provide context with exceptions to make them more helpful.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;6. Unit Tests:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Write tests for your code.&lt;/li&gt;
&lt;li&gt;Tests should be clean, too – easy to read, easy to understand, and easy to modify.&lt;/li&gt;
&lt;li&gt;Tests should cover various cases and edge conditions.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;7. DRY (Don't Repeat Yourself):&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Avoid duplication of code.&lt;/li&gt;
&lt;li&gt;Use abstraction, functions, or classes to avoid code duplication.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;8. Simplicity:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Write simple code that gets the job done.&lt;/li&gt;
&lt;li&gt;Avoid over-engineering and premature optimization.&lt;/li&gt;
&lt;li&gt;Remove unnecessary code.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;9. Code Review:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Regularly review your code with colleagues to catch mistakes and get suggestions for improvement.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;10. Refactoring:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Continuously refactor your code to make it cleaner.&lt;/li&gt;
&lt;li&gt;Make one change at a time and test it before moving on.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;11. Code Cohesion:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Keep related code together.&lt;/li&gt;
&lt;li&gt;Ensure that classes and modules have a clear responsibility.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;12. Use Design Patterns Wisely:&lt;/strong&gt;&lt;br&gt;
Use design patterns where they are needed, but don't force them into your code.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;15. Code Documentation:&lt;/strong&gt;&lt;br&gt;
Write documentation that explains how to use your code, especially for libraries and APIs.&lt;/p&gt;

</description>
      <category>coding</category>
      <category>softwaredevelopment</category>
      <category>programming</category>
    </item>
    <item>
      <title>javaScript useful method</title>
      <dc:creator>zonaetmunna</dc:creator>
      <pubDate>Wed, 22 Dec 2021 07:19:21 +0000</pubDate>
      <link>https://dev.to/zonaetmunna/javascript-useful-method-2e7g</link>
      <guid>https://dev.to/zonaetmunna/javascript-useful-method-2e7g</guid>
      <description>&lt;h2&gt;
  
  
  Javascript string and array function
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;toLowerCase&lt;/strong&gt;: toLowerCase() method is convert any string to lower case.&lt;br&gt;
&lt;strong&gt;toUpperCase:&lt;/strong&gt; toUpperCase() method is convert any sting to upper case&lt;br&gt;
Searching method:&lt;br&gt;
indexOf: &lt;br&gt;
includes: &lt;br&gt;
startWith:&lt;br&gt;
endWith: &lt;br&gt;
Array methods&lt;br&gt;
split: &lt;br&gt;
slice:&lt;br&gt;
subStr: &lt;br&gt;
subString: &lt;br&gt;
concat: &lt;br&gt;
 join:&lt;br&gt;&lt;br&gt;
Array searching method&lt;br&gt;
isArray:&lt;br&gt;
indexOf:&lt;br&gt;
includes:&lt;br&gt;
concat:&lt;/p&gt;

</description>
    </item>
    <item>
      <title>CSS position property</title>
      <dc:creator>zonaetmunna</dc:creator>
      <pubDate>Sun, 19 Dec 2021 17:29:28 +0000</pubDate>
      <link>https://dev.to/zonaetmunna/css-position-property-8oa</link>
      <guid>https://dev.to/zonaetmunna/css-position-property-8oa</guid>
      <description>&lt;p&gt;I just simply write CSS position tropic. I  explore some web tutorials and find out some main concepts. I want to just share people for my study and grow my skills and  I want to spread and share with people my knowledge.&lt;br&gt;
&lt;strong&gt;CSS position:&lt;/strong&gt; &lt;br&gt;
CSS position property positioning any element in a web page. how an element stays on a web page depends on the CSS position property. position property has some value static, absolute, relative, fixed, sticky.&lt;br&gt;
&lt;strong&gt;Static:&lt;/strong&gt;&lt;br&gt;
Static is the default value of the position property. Top,bottom,left,right,z-index are not affect.&lt;br&gt;
Have 3 div element.their default value is static.&lt;br&gt;
&lt;strong&gt;Relative:&lt;/strong&gt;&lt;br&gt;
Relative value &lt;/p&gt;

</description>
    </item>
  </channel>
</rss>
