| ... |
... |
@@ -19,7 +19,7 @@ |
| 19 |
19 |
|Dirty|((( |
| 20 |
20 |
~1. Messy, unreadable, or poorly designed code is referred to as "dirty code". Often associated with code written "quick-and-dirty" due to time pressure. |
| 21 |
21 |
|
| 22 |
|
-2. The term comes from the phrase "getting one's hands dirty" and refers to coding work that is considered monotonous, detailed, low-level and undemanding, but necessary. The term is often used in the context of I/O operations. Creating a database transaction, for example, is always handled very similarly and is not considered a fun task for experienced programmers who have done it many times. High-level design is more exciting because it requires more creativity from the developer and is more intellectually stimulating. Example sentence. |
|
22 |
+2. The term comes from the phrase "getting one's hands dirty" and refers to coding work that is considered monotonous, detailed, low-level and undemanding, but necessary. The term is often used in the context of I/O operations. Creating a database transaction, for example, is always handled very similarly and is not considered a fun task for experienced programmers who have done it many times. High-level design is more exciting because it requires more creativity from the developer and is more intellectually stimulating. |
| 23 |
23 |
))) |
| 24 |
24 |
|Dynamic|((( |
| 25 |
25 |
Often refers to processes which appear at runtime when the code has already been executed and is "running". Examples: |
