| ... |
... |
@@ -18,7 +18,6 @@ |
| 18 |
18 |
| Dependency | In context of classes, a dependency is an object required by another object to perform its functions. Often, dependencies are provided via dependency injection. | |
| 19 |
19 |
| Dependency Cycle | A situation where two or more classes depend on each other to be instantiated. This situation creates a circular dependency that makes object creation impossible. The dependency graph should be a directed acyclic graph rather than a cycle. | |
| 20 |
20 |
| [[Dependency Injection|doc:Software Engineering.Architecture.Dependency Injection.WebHome]] (DI) | A technique where an object's dependencies are provided from outside, rather than being created within the object itself. | |
| 21 |
|
-| Developer | Skilled programmer with advanced technical knowledge in areas such as software design, coding best practices, technical concepts, etc. | |
| 22 |
22 |
| Dirty (Code) | Code that is messy, unreadable, or poorly designed. | |
| 23 |
23 |
| Distribution | A version of an OS packaged with specific software and configurations, designed for specific use cases. Examples: Ubuntu, Fedora, and Arch Linux, all based on Linux. | |
| 24 |
24 |
| Dynamic | Behaviors/properties determined at runtime. Examples: dynamic dependencies can be replaced at runtime; dynamically-typed languages determine an object's type at runtime. | |
| ... |
... |
@@ -38,7 +38,6 @@ |
| 38 |
38 |
| Pain | An unpleasant experience caused by unnecessary efforts that could have been mitigated with better design of the original code. | |
| 39 |
39 |
| Physical | Counterpart to logical. Refers to hardware. For example, physically deleting a file means removing it from the disk. | |
| 40 |
40 |
| Production Code | Code that comprises the functioning part of an application, as opposed to test code. | |
| 41 |
|
-| Programmer | Someone who writes and tests code. The knowledge level of a beginner. | |
| 42 |
42 |
| Requirement | Statement of what a software must be capable of doing, often outlining features, constraints, and success criteria. | |
| 43 |
43 |
| Resources | Refers to the assets used in the project, including time, money, staff, and effort. | |
| 44 |
44 |
| Rollback | The act of returning a system or data to a previous state, often using a snapshot. | |
