Category:Software Design/Practices applying to functions
A category for software design practices that apply on the level of functions, which are also called methods, procedures, routines, operations, etc. in different programming languages and environments. These practices also generally apply to commands. Practices concerning functions' interface also apply to RPC interfaces, such as REST interfaces.
Pages in category "Software Design/Practices applying to functions"
The following 20 pages are in this category, out of 20 total.
- Software Design/Arrange parameters in a consistent order
- Software Design/Begin the name of a function with side effects with a verb
- Software Design/Break up too large and complex functions
- Software Design/Create "deep" functions
- Software Design/Create pure functions
- Software Design/Document function's algorithmic complexity
- Software Design/Don't add a parameter that won't be used
- Software Design/Don't omit function's signature (return type)
- Software Design/Don't use get- prefix in the name of an expensive function
- Software Design/Explicitly pass integration objects into functions
- Software Design/Extract generic components
- Software Design/Make function to access its enclosing class more than any of its arguments
- Software Design/Minimize the accessibility of classes and members
- Software Design/Prohibit overriding implementation of a function
- Software Design/Require the least powerful abstract class you need to implement a function
- Software Design/Specify interface contracts
- Software Design/Split responsibilities between classes and functions
- Software Design/Use a single term to point to a concept
- Software Design/Use class instead of primitive type
- Software Design/Validate data during object construction