Skip to Content

Changes for page Glossary

Last modified by chrisby on 2024/09/19 10:50
From version 2.1
edited by chrisby
on 2022/12/25 18:48
Change comment: There is no comment for this version
To version 2.3
edited by chrisby
on 2022/12/28 13:40
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -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:
... ... @@ -47,9 +47,6 @@
47 47  |Magic|"Code that handles complex tasks while hiding that complexity to present a simple interface."^^[[[sources]>>url:https://en.wikipedia.org/wiki/Magic_(programming)]]^^ For example, the introduction of the Spring IoC container is quite simple, but the logic and wiring that goes on in the background is complex.
48 48  |Pain|Something causes pain when somebody spend unnecessary and great effort on a task that often could have been prevented by better code design.
49 49  |Production Code|The counterpart of the Test Code. It contains all the code required to run the application.
50 -|Reflection|(((
51 -A technique that allows you to work with code from a high-level perspective. For example, given the object "person", Reflection allows commands like this "person.getClass().getDeclaredFields()" to work with the fields of an object. E.g., reflection can ask for the fields names, access modifiers, etc. The code reflects on the code, it is self-reflective.
52 -)))
53 53  |Runtime|(((
54 54  The time period in which the code is executed. For example:
55 55  
... ... @@ -71,4 +71,4 @@
71 71  )))
72 72  |Test Code|The counterpart of the Production Code. It is code that checks whether the production code works as expected. Test Code plays no role in the operation of an application.
73 73  |Test-Driven Development|A workflow in which the developer implements code in small steps, incrementally and iteratively, defining tests at each iteration.
74 -|Wiring|The process of aggregating beans and injecting the required dependencies performed by the IoC container.
71 +|Wiring|The process of generating and injecting dependencies to set up an application performed by the IoC container.