Comments · 329 Views

Refactoring refers to maintenance, i.e. the repair of program code. However, programming errors are not repaired here, but so-called bad or smelly code


Refactoring refers to maintenance, i.e. the repair of program code. However, programming errors are not repaired here, but so-called bad or smelly code - someone to do my homework for me . Refactoring teaches you how to restructure bad code so that it is clean again. The functionality of your program is not in the foreground, but other important points in your source code.

These are:

  • Readability
  • Clarity
  • Comprehensibility
  • Expandability
  • No duplicate code
  • Testability

There are a few methods and techniques to help - do my php homework - you achieve this. These found in the renaming of variables and go up to the complete restructuring of the source code. These techniques come from Martin Fowler.

Clean Code

With Clean Code, so clean code that is exactly the opposite meaning of bad code. The software developer Robert C. Martin coined this term.

Clean source code, but also clean software, is more stable and maintainable. For this to work, it not only has to work, it also has to be intuitively understandable.

That might sound complicated now, but it isn't at all. You just have to keep in mind that you read your source text about 10 times more often than you write it. This means that every line of code written is read approximately 10 times. For this reason, your software should be easy to read, right?

In order to achieve this, you use design patterns, refactor your programs and apply a few easy-to-learn principles when programming - . However, clean code requires a very high level of discipline. Because when you have to go fast, you tend to produce bad code.

Here are two principles :

Meaningful names

Always use meaningful names for functions, classes and variables.

If you do this, even comments become almost unnecessary. Use a long variable name that describes its purpose rather than a meaningless comment.

2 rules for functions

  1. The function should be short.
  2. If it's short, it should be even shorter.

With these two principles I will leave you alone for now. Because there are whole books on this subject too.

It is important that you learn how to write stable and maintainable programs on this topic.

You may have written the greatest game in the world, but if it takes 3 years to fix a bug, you won't be successful.

Read also:

Physics: Energy
Biochemistry, molecular biology
Politics as a subject
An example of design patterns
Famous math theorems