Please enable JavaScript.

Coggle requires JavaScript to display documents.

Understanding Software (Understanding Software (The components of software…

- - - - Avoid releasing Bad APIs
      - Provide Backwards compatibility if breaking your API
- - - - Programmers responsibility is writing simple code, so that the future programmer reading your code should understand it
      - The simpler the code is, the fewer bugs you will have
      - Always work to simplify everything about your program
  - - - Having Familiarity with what the working system does
      - Accepting that you don't already know the cause of the problem
      - Looking at the data until you know the causes of the problem
      - Fixing the cause and not the symptoms
- - - - Problem List
        
        Create a list of problems that frustrates developers
      - Meeting
        
        Go over the list and get the specific directory, file or code to associate with each symptom
      - Bug Report
        
        File a bug report describing the problem
      - Prioritization
        
        The essence of good programming is taking the right actions in right sequence
        
        Prioritize and resolve the code
      - Assignment
        
        Assign each bug to an individual contributor
      - Planning
        
        Plan when to address the problem
- - - - Observation
      - Decision
      - Action
  - - - Unit Testing
        
        Unit test should be testing the behaviour of the component, not its implementation
      - Integration Testing
        
        If two components are hard to test due to their complexity of their interactions, this indicates that either one or both of them should be refactored
      - End-to-End Testing
        
        If a system is designed in such a way that it can only be tested via end-to-end test, then that is a symptom of broad architectural problems in the code
      - Acceptance Testing
  - - - Understanding
        
        The most common reason developers stop to think is that they did not understand some word or symbol
      - Drawing
        
        It is always more efficient to write or draw something, than thinking about it
      - Starting
        
        Often the simplest piece of code to start with is the core of the application.
        
        If you are not sure about the core code then start with the code you are sure about
      - Skipping a step
        
        Don't jump over steps in development of your system and expect that you'll be productive
      - Physical problems
      - Distractions
      - Self-Doubt
      - False Ideas
      - Caveat