| ... |
... |
@@ -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. | |
| ... |
... |
@@ -47,6 +47,7 @@ |
| 47 |
47 |
| Separation of Concerns | A design principle suggesting that each module or component should have a single responsibility or concern, enhancing clarity and maintainability. | |
| 48 |
48 |
| [[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. | |
| 49 |
49 |
| Snapshot | A saved state of a system or data at a specific point in time. Can be used for rollbacks. | |
|
51 |
+| Software Engineer | Technical expert with in-depth knowledge in many areas, including high-level topics such as software architecture and system design. | |
| 50 |
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. | |
| 51 |
51 |
| System | Entirety of software components designed to work together effectively in a production environment. | |
| 52 |
52 |
| Test Code | Code that tests the functionality of production code. Does not contribute to the operational aspects of an application. | |
