Runtime Analysis in the Context of System Engineering

Runtime analysis of function calls and parameter inputs is misleading in practice. Runtime costs need to account for the problem domain to paint a complete picture of runtime costs post deployment.

Paper

https://nwcodex.com/invocationruntimeanalysis

https://medium.com/@nwcodex/invocation-asymptotics-runtime-analysis-based-on-the-characteristics-of-input-data-374337eca8b

Abstractionless Code Auditing

Abstraction in modern computing languages leads to lazy engineering practices by hiding important implementation details from engineers, many of which are critical to review during the code auditing process (building a mental model of the system prior to development to develop well designed enhancement and dependent features). Natural language models that modern computing languages allow engineers to use as abstractions for underlying code constructs do not capture the complexity of the underlying components (CamelCaseClassNames and variable_names don’t map effectively to the structure of underlying components). Abstraction should serve as a mechanisms that empower effective and efficient reuse, and not a means of removing the engineers capacity to audit and understand the underlying system. Below are suggested a few tools to tactfully remove abstractions from source files in Python and C/C++ as a proof of concept.

Paper

https://nwcodex.com/abstractionlesscomputing

https://medium.com/@nwcodex/ingesting-machine-language-9847156fe0fc