| ... |
... |
@@ -54,7 +54,6 @@ |
| 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'. | |
| 58 |
58 |
| Physical | The counterpart to "logical". Refers to hardware. For example, physically deleting a file means removing it from the disk. | |
| 59 |
59 |
| 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]]. | |
| 60 |
60 |
| Problem Domain | The language/terminology used to describe the software requirements ("the problems") from the perspective of non-technical stakeholders. | |
