| ... |
... |
@@ -18,6 +18,7 @@ |
| 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. | |
| 21 |
21 |
| Dirty (Code) | Code that is messy, unreadable, or poorly designed. | |
| 22 |
22 |
| 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. | |
| 23 |
23 |
| Dynamic | Behaviors/properties determined at runtime. Examples: dynamic dependencies can be replaced at runtime; dynamically-typed languages determine an object's type at runtime. | |
| ... |
... |
@@ -37,6 +37,7 @@ |
| 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. | |
|
41 |
+| Programmer | Someone who writes and tests code. The knowledge level of a beginner. | |
| 40 |
40 |
| Requirement | Statement of what a software must be capable of doing, often outlining features, constraints, and success criteria. | |
| 41 |
41 |
| Resources | Refers to the assets used in the project, including time, money, staff, and effort. | |
| 42 |
42 |
| Rollback | The act of returning a system or data to a previous state, often using a snapshot. | |
| ... |
... |
@@ -46,7 +46,7 @@ |
| 46 |
46 |
| Separation of Concerns | A design principle suggesting that each module or component should have a single responsibility or concern, enhancing clarity and maintainability. | |
| 47 |
47 |
| [[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. | |
| 48 |
48 |
| Snapshot | A saved state of a system or data at a specific point in time. Can be used for rollbacks. | |
| 49 |
|
-| 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. | |
|
51 |
+| 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. | |
| 50 |
50 |
| System | Entirety of software components designed to work together effectively in a production environment. | |
| 51 |
51 |
| Test Code | Code that tests the functionality of production code. Does not contribute to the operational aspects of an application. | |
| 52 |
52 |
| 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. | |
