Changes for page Glossary

Last modified by chrisby on 2024/09/19 10:50

From version 18.39
edited by chrisby
on 2023/12/01 18:28
Change comment: There is no comment for this version
To version 18.42
edited by chrisby
on 2023/12/01 18:44
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Glossary
1 +Typically used in the form 'to refactor code'."
Content
... ... @@ -54,12 +54,13 @@
54 54  | Overloading | Some programming languages offer the feature of overloading, which means that two operators with the same name can still be distinguished if they have different signatures. For example, these two functions are overloaded: `tripleNumber(n: float)` and `tripleNumber(n: int)`. |
55 55  | Pain | An unpleasant experience caused by unnecessary efforts that could have been mitigated with better design of the original code. |
56 56  | [[Pair Programming|doc:Software Engineering.Agile.Extreme Programming.Pair Programming.WebHome]] / Pairing (up) | See link. |
57 +| Performance Optimization | Modifying code to enhance its execution speed, which may involve trade-offs at the expense of code quality. It is a subtype of 'Restructuring'. |
57 57  | Physical | The counterpart to "logical". Refers to hardware. For example, physically deleting a file means removing it from the disk. |
58 58  | Points / Story Points | A unit of measure used to estimate the effort required to complete a user story. See also [[here|doc:Software Engineering.Agile.Extreme Programming.Planning Game.Effort Estimation.WebHome]]. |
59 59  | Problem Domain | The language/terminology used to describe the software requirements ("the problems") from the perspective of non-technical stakeholders. |
60 60  | Production Code | Code that comprises the functioning part of an application, as opposed to test code. |
61 61  | Programmer | Someone who writes and tests code. The knowledge level of a beginner. |
62 -| Refactoring | Modifying code to improve its quality without changing its functionality. It is a subtype of 'Restructuring'. |
63 +| Refactoring | Modifying code to improve its quality without changing its functionality. It is a subtype of 'Restructuring'. Often used as: 'to refactor code'. |
63 63  | Requirement | Statement of what a software must be capable of doing, often outlining features, constraints, and success criteria. |
64 64  | Resources | Refers to the assets used in the project, including time, money, staff, and effort. |
65 65  | Restructuring | Modifying code to improve its quality. |