Computer science
- 24th century computer programming seemingly built modularly rather than low-level coding for 99% of design
- Individual modules known as "subroutines", hard-built functions with specific input and output hooks
- Can be individually enabled/disabled
- When disabled, message-passing simply passes through rather than interrupting program flow
- Manipulating functionality of an existing program thus consists of adding, deleting, enabling, or disabling individual subroutines rather than engaging in raw code
- Possibly a factor of code density and/or safety? By using individual, expansively complex modules that have been formally verified, code errors can be reduced to a minimum
- New subroutines could still be designed as needed (and described), inserted, but with potentially less effectiveness or errors