SagharMax

Clean Code Rules: 31. Always have in mind that you are writing code for humans Any fool can write code that a computer can understand. Good programmers write code that humans can understand. #software_development #programming #dotnet #csharp #dotnetdevelopment #webdevelopment #coding #workstation #workdesk #clean_code #uncle_bob #robert_c_martin #sagharmax (at Urmia) https://www.instagram.com/p/Cp74V0MIqcy/?igshid=NGJjMDIxMWI=

Clean Code Rules: 30. Get used to refactoring It can be a scary word for some developers. It sounds like you’re changing code, which can be dangerous, right? Wrong. Refactoring makes your code better and is essential for writing clean code. When you have some experience developing C# code, you notice that you can do things better. The problem is that changing existing code is more complex than writing new code. Luckily, refactoring is a skill you can learn. Very quickly. #software_development #programming #dotnet #csharp #dotnetdevelopment #webdevelopment #coding #workstation #workdesk #clean_code #uncle_bob #robert_c_martin #sagharmax (at Urmia) https://www.instagram.com/p/Cp5T08so3Vh/?igshid=NGJjMDIxMWI=

Clean Code Rules: 29. Use design patterns Design patterns are reusable code solutions to commonly occurring problems in software applications. They are not solutions to specific issues but templates for common problems in various contexts. You can reuse them in many different situations. In short, they’re a collection of best practices. Design patterns can help you write more readable code and avoid redundant and error-prone code. #software_development #programming #dotnet #csharp #dotnetdevelopment #webdevelopment #coding #workstation #workdesk #clean_code #uncle_bob #robert_c_martin #sagharmax (at Urmia) https://www.instagram.com/p/Cp2xm2JIUiD/?igshid=NGJjMDIxMWI=

Clean Code Rules: 28. Use the using statement The “using” statement is handy when writing code in C#. You can use it to easily avoid memory leaks, which are common if you don’t use them. A memory leak is where the .NET garbage collector doesn’t know your object is no longer being used. So, when you try to run your program, the .NET garbage collector will not free up memory because it doesn’t know that those objects are no longer needed. The using statement will solve this problem. #software_development #programming #dotnet #csharp #dotnetdevelopment #webdevelopment #coding #workstation #workdesk #clean_code #uncle_bob #robert_c_martin #sagharmax (at Urmia) https://www.instagram.com/p/Cp0jYevMlC2/?igshid=NGJjMDIxMWI=

Clean Code Rules: 27. Don’t reinvent the wheel Many developers love writing code. We love to create new little libraries and frameworks. But, sometimes, we forget there’s no need to reinvent the wheel. When you’re writing code for a project, there are certain things that you can go ahead and do yourself. There are also things that you should never do. For example, if you need ORM (Object-Relational Mapping), use Entity Framework Core or Dapper. Don’t write your own. #software_development #programming #dotnet #csharp #dotnetdevelopment #webdevelopment #coding #workstation #workdesk #clean_code #uncle_bob #robert_c_martin #sagharmax (at Urmia) https://www.instagram.com/p/CpxtAviMrK0/?igshid=NGJjMDIxMWI=

Clean Code Rules: 26. CI/CD Continuous integration and continuous delivery (CI/CD) are software development processes in which teams produce software in short cycles, ensuring the software can be reliably released at any time. #software_development #programming #dotnet #csharp #dotnetdevelopment #webdevelopment #coding #workstation #workdesk #clean_code #uncle_bob #robert_c_martin #sagharmax (at Urmia) https://www.instagram.com/p/CpvM6aToqt9/?igshid=NGJjMDIxMWI=

Clean Code Rules: 25. Unit testing Unit testing is when you check that the minor testable parts of an application, called units, work as expected. You can perform unit testing on individual methods, classes, or modules. #software_development #programming #dotnet #csharp #dotnetdevelopment #webdevelopment #coding #workstation #workdesk #clean_code #uncle_bob #robert_c_martin #sagharmax (at Urmia) https://www.instagram.com/p/Cpsi5aosOgF/?igshid=NGJjMDIxMWI=

Clean Code Rules: 24. Perform code reviews One of the most important things when working in teams is constantly improving your code. But how do you ensure that you are writing easy-to-read and understand code? Code reviews are a great way to do that. They allow you to see how other developers see your code. #software_development #programming #dotnet #csharp #dotnetdevelopment #webdevelopment #coding #workstation #workdesk #clean_code #uncle_bob #robert_c_martin #sagharmax (at Urmia) https://www.instagram.com/p/CpqJ2xjrLKL/?igshid=NGJjMDIxMWI=

Clean Code Rules: 23. Use constants instead of magic numbers/magic strings Magic numbers are a bad practice that you should avoid in your code. They don’t provide any context to the value they represent and are hard to maintain since the deal itself is hard to find. #software_development #programming #dotnet #csharp #dotnetdevelopment #webdevelopment #coding #workstation #workdesk #clean_code #uncle_bob #robert_c_martin #sagharmax (at Urmia) https://www.instagram.com/p/CpnDHkoIOSl/?igshid=NGJjMDIxMWI=

Clean Code Rules: 22. Minimize the use of global variables Every C# software engineer knows that using global variables is not good practice. But we do it anyway because it’s so convenient. The fact that global variables are accessible from anywhere comes with a downside. Any changes to a global variable also affect everything else in the application. #software_development #programming #dotnet #csharp #dotnetdevelopment #webdevelopment #coding #workstation #workdesk #clean_code #uncle_bob #robert_c_martin #sagharmax (at Urmia) https://www.instagram.com/p/CpkoDQ-ssU5/?igshid=NGJjMDIxMWI=

Clean Code Rules: 21. Use SOLID principles SOLID is an acronym for five coding principles for writing better code. These principles help develop any application but have been especially useful for object-oriented programming. ○ Single responsibility principle: A class or a method should have only one reason to change. ○ Open/closed principle: A class should be open for extension but closed for modification. ○ Liskov substitution principle: Base type should be substitutable for child types without breaking the functionality. ○ Interface segregation principle: No client should be forced to depend on properties and methods it does not need. ○ Dependency inversion: High-level modules should not depend on low-level modules. They should depend on abstractions. Abstractions should be independent of details. Details should depend on abstractions. #software_development #programming #dotnet #csharp #dotnetdevelopment #webdevelopment #coding #workstation #workdesk #clean_code #uncle_bob #robert_c_martin #sagharmax (at Urmia) https://www.instagram.com/p/CpiPV2koZMn/?igshid=NGJjMDIxMWI=

Clean Code Rules: 20. Use the KISS principle You should keep your code as simple as possible. Getting carried away with complicated code is easy, but the KISS principle suggests otherwise. The KISS principle says that “Keep It Simple, Stupid.” Therefore, follow this rule to increase the code quality. #software_development #programming #dotnet #csharp #dotnetdevelopment #webdevelopment #coding #workstation #workdesk #clean_code #uncle_bob #robert_c_martin #sagharmax https://www.instagram.com/p/Cpf3iGtMuxM/?igshid=NGJjMDIxMWI=

Clean Code Rules: 19. Use the DRY principle The don’t repeat yourself principle (DRY) is a software design principle that reduces the repetition of duplicate code in the application. #software_development #programming #dotnet #csharp #dotnetdevelopment #webdevelopment #coding #workstation #workdesk #clean_code #uncle_bob #robert_c_martin #sagharmax (at Urmia) https://www.instagram.com/p/CpdYEeSME3w/?igshid=NGJjMDIxMWI=

Clean Code Rules: 18. Use the YAGNI principle The YAGNI principle should be more noticed in the development process. It stands for “You Aren’t Going to Need It” and reminds developers only to build what is necessary. This principle can keep projects on track by preventing unnecessary features from being added and bogging down the development process. #software_development #programming #dotnet #csharp #dotnetdevelopment #webdevelopment #coding #workstation #workdesk #clean_code #uncle_bob #robert_c_martin #sagharmax (at Urmia) https://www.instagram.com/p/CpamJ02IlNP/?igshid=NGJjMDIxMWI=

Clean Code Rules: 17. Write private code You should always use private fields and methods as much as possible in your classes. This way, other types can access only the minimum public methods. As a result, you can change the code anytime without worrying about anyone else accessing it. #software_development #programming #dotnet #csharp #dotnetdevelopment #webdevelopment #coding #workstation #workdesk #clean_code #uncle_bob #robert_c_martin #sagharmax (at Urmia) https://www.instagram.com/p/CpX7dyGosx6/?igshid=NGJjMDIxMWI=

Clean Code Rules: . 16. Avoid returning null as the method result Returning null is a common programming practice used when a method cannot complete its action. However, this is a considerable risk. It would be best if you remembered to handle the null result that the method returns. #software_development #programming #dotnet #csharp #dotnetdevelopment #webdevelopment #coding #workstation #workdesk #clean_code #uncle_bob #robert_c_martin #sagharmax (at Urmia) https://www.instagram.com/p/CpVSciuuwD_/?igshid=NGJjMDIxMWI=

Clean Code Rules: 15. Don’t write “clever code.” I am cautious only about writing clever code that is easy to maintain. I will often rewrite code that is clever and make it more straightforward. #software_development #programming #dotnet #csharp #dotnetdevelopment #webdevelopment #coding #workstation #workdesk #clean_code #uncle_bob #robert_c_martin #sagharmax (at Urmia) https://www.instagram.com/p/CpTEJcMLbQE/?igshid=NGJjMDIxMWI=