Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.

1. Follow standard conventions.
2. Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
3. Boy scout rule. Leave the campground cleaner than you found it.
4. Always find root cause. Always look for the root cause of a problem.

A commit should be a wrapper for related changes. For example, fixing two different bugs should produce two separate commits. Small commits make it easier for other developers to understand the changes and roll them back if something went wrong. With tools like the staging area and the ability to stage only parts of a file, Git makes it easy to create very granular commits.

Committing often keeps your commits small and, again, helps you commit only related changes. Moreover, it allows you to share your code more frequently with others. That way it‘s easier for everyone to integrate changes regularly and avoid having merge conflicts. Having large commits and sharing them infrequently, in contrast, makes it hard to solve conflicts.

[TOC]

At the end of this lesson you will be able to:

• use github commands to:
• create and clone repository

[TOC]

At the end of this lesson you will be able to:

• use github commands to:
• create and clone repository

[TOC]

​ At the end of this lesson you should be able to:

• Use GET and POST HTTP methods

[TOC]

​ At the end of this lesson you should be able to:

• Use GET and POST HTTP methods

[TOC]

​ At the end of this lesson you should be able to:

• Differentiate frontend and backend development

[TOC]

​ At the end of this lesson you should be able to:

• Differentiate frontend and backend technologies

[TOC]

​ At the end of this lesson you should be able to:

• Differentiate frontend and backend technologies