1 of 12

PART I.IV

Version Control

2 of 12

Git Basic Review

  • Initializing a Repository in an Existing Directory
  • Cloning an Existing Repository
  • Recording Changes to the Repository
  • Checking the Status of Your Files
  • Tracking New Files
  • Ignoring Files
  • Committing Your Changes

01

3 of 12

Git Basic Review

  • Working with Remotes
  • Tagging
  • Basic Branching and Merging
  • Branch Management
  • Git Workflow
  • Remote Branches
  • Rebasing

02

4 of 12

Clean Code Rules

03

Coding best practices (Clean Codes) are a set of informal rules that the software development community has learned over time which can help improve the quality of software.

5 of 12

Rules for Specific Language - Language C/C++

  • Formatting: Formatting your source code.
  • Comments: Commenting your work.
  • Syntactic Conventions: Clean use of C constructs.
  • Names: Naming variables, functions, and files.
  • System Portability: Portability among different operating systems.
  • Character Set: Use ASCII by default.
  • System Functions: Portability and “standard” library functions.
  • Internationalization: Techniques for internationalization.

04

6 of 12

For Example:

When you have an if-else statement nested in another if statement, always put braces around the if-else.

Right !

Wrong

05

7 of 12

Code is Art.

06

8 of 12

Examples with Gradle

  • Build Anything
  • Automate Everything
  • Deliver Faster

07

9 of 12

Continuous Integration

08

build

unit tests

integration testing

deploy

Continuous Integration

10 of 12

Continuous Integration for Android

  • PMD
  • Checkstyle
  • FindBugs
  • Lint
  • Deploy & Releasing
  • Environments
  • Coverage

09

11 of 12

Git Workflow with CI

v1.0

v2.0

v3.0

master branch

develop branch

release

feature branch

10

12 of 12

  • Clone the Project Course-PR (or update as upstream ).
  • Create a new directory like: Course-PR/lesson/ [You name].
  • Create a new Java class: Sort.java.
  • Write a bubble sort algorithm in Sort.java.
  • Add changes to git history, commit and push to your fork.
  • Open a pull request and fix the ci errors.
  • Get your work review and merged.

Practice

11