Let's assume we have a 16-bit computer with 4 words of memory (= 8 bytes, really underpowered!) that we can store variables in. Let's label them 01-04 and write out what's in them in binary:
Memory
00: 0000
01: 0000
02: 0000
03: 0000
Let's assume we have a 16-bit computer with 4 words of memory (= 8 bytes, really underpowered!) that we can store variables in. Let's label them 01-04 and write out what's in them in binary:
Memory
00: 0000
01: 0000
02: 0000
03: 0000
Plan for Change | |
MOTIVATION | |
- Change is inevitable: | |
- Requirements change | |
- Teams change | |
- Technology changes | |
This talk aims to answer the question, "how do I deal with these changes?" |
Requirements always change. We need to write code that is able to change in the future. The process of doing so is usually called design. Design principles are often-cited rules that lead to easily-changed code. Design principles have been derived from the initial goal: to have easily-changed code. They are not arbitrary rules. SOLID principles are an often-used set of design principles.
I hereby claim:
To claim this, I am signing this object: