| ... |
... |
@@ -37,6 +37,8 @@ |
| 37 |
37 |
| Pain | An unpleasant experience caused by unnecessary efforts that could have been mitigated with better design of the original code. | |
| 38 |
38 |
| Physical | Counterpart to logical. Refers to hardware. For example, physically deleting a file means removing it from the disk. | |
| 39 |
39 |
| Production Code | Code that comprises the functioning part of an application, as opposed to test code. | |
|
40 |
+| Programmer | Someone who writes and tests code. The knowledge level of a beginner. | |
|
41 |
+| Requirement | Statement of what a software must be capable of doing, often outlining features, constraints, and success criteria. | |
| 40 |
40 |
| Resources | Refers to the assets used in the project, including time, money, staff, and effort. | |
| 41 |
41 |
| Rollback | The act of returning a system or data to a previous state, often using a snapshot. | |
| 42 |
42 |
| Runtime | The period when the code is being executed. Often used to distinguish from compile time. | |
| ... |
... |
@@ -45,7 +45,7 @@ |
| 45 |
45 |
| Separation of Concerns | A design principle suggesting that each module or component should have a single responsibility or concern, enhancing clarity and maintainability. | |
| 46 |
46 |
| [[Setter Injection|doc:Software Engineering.Architecture.Dependency Injection.Types of Dependency Injection.WebHome]] | A type of dependency injection where a dependency is provided to an object through a setter method. | |
| 47 |
47 |
| Snapshot | A saved state of a system or data at a specific point in time. Can be used for rollbacks. | |
| 48 |
|
-| Static | Pertains to behaviors or properties determined at compile time. Examples: static code analysis tools inspect source code; statically-typed languages determine an object's type at compile time. | |
|
50 |
+| Static | Behaviors/properties determined before or at compile time. Examples: static code analysis tools inspect source code; statically-typed languages determine an object's type at compile time. | |
| 49 |
49 |
| System | Entirety of software components designed to work together effectively in a production environment. | |
| 50 |
50 |
| Test Code | Code that tests the functionality of production code. Does not contribute to the operational aspects of an application. | |
| 51 |
51 |
| Test-Driven Development (TDD) | A development approach where code is written in small increments, with tests defining functionality written at the beginning of each coding iteration. | |
