Maintainability and Clean Code

• degree of effectiveness and efficiency with which the product can be modified
• consists of 
  • Analysability
  • Modularity
  • Reusability
  • Modifiability
  • Testability

• reduces costs during maintenance
• enables other 7 characteristics of software product quality (security, functional suitability, performance)

• writing clean code 
• improves internal and external quality of product

• clear, understandable, comprehensible, logical and disciplined implementation of code
• code is designed to be easy to read, change, expand and maintain

Idea:

• improve readability by creating common look and feel

Problems:

• Conventions are ignored (no knowledge)
• Conventions differ between languages and communities

Reasons for other Languages

• harder to write english commentaries/find names
• bad english skills could lead to misunderstandings/typos

Reasons for using English:

• English communities are much larger 
• for help of english community, dont have to translate
• no mixture of english programming language and local language
• you should be able to read and speak fluent English

• use language default
  • detailed guidelines available
  • style switches necessary when working on multiple projects within the same team or project with multiple languages
• decide in your team on a standard
  • keep consistent
  • one style over all languages
  • maybe switching styles between teams

• indications of poor coding and design choices that may lead to bad maintainability
• technically not incorrect
• indicate weaknesses and could be slowing down development or increase risk of bugs
• code vs architectural level