P/Kevlin-Henney

tests must clearly express required functionality (src: Video_ Structure and Interpretation of Test Cases - Kevlin Henney)

Model: Grouping tests (src: Video_ Structure and Interpretation of Test Cases - Kevlin Henney)

Naming tests snake case is more readable than camel case (when > 30 characters, which tests usually are) “should” is like training wheels name tests as propositions name test as Method_input_result (src: Video_ Structure and Interpretation of Test Cases - Kevlin Henney)

(https://www.youtube.com/watch?v=tWn8RA_DEic) Model_ naming tests snake case is more readable than camel case (when > 30 characters, which tests usually are) “should” is like training wheels name tests as propositions name test as Method_input_result Model_ tests must clearly express required functionality Article: Model_ Grouping tests

(https://www.youtube.com/watch?v=tMW08JkFrBA)

Video: Small Is Beautiful - Kevlin Henney (https://www.youtube.com/watch?v=B3b4tremI5o) -optimization problem bandwidth limit: maximum you can hold in your head -> slow down, caution, hesitant, uncomfortable to touch it throw-away-code: prod, saved, never away we don’t throw things away, we have new versions only in pdf

Model: 3 Axes of software development as opposed to functional and non-functional functional (runtime) operational (runtime) developmental (dev time) Refactoring = keeping functional axis stable eg. func fixed dev improves ops is kept open (src: Video_ Code as Risk • Kevlin Henney)

Code as Risk • Kevlin Henney https://www.youtube.com/watch?v=YyhfK-aBo-Y Article_ Goto Fail, Heartbleed, and Unit Testing Culture - Martin Fowler Article_ Top 10 Secure Coding Practices Model_ 3 Axes of software development as opposed to functional and non-functional functional (runtime) operational (runtime) developmental (dev time) Refactoring = keeping functional axis stable eg. func fixed dev improves ops is kept open Article: Top 10 coding practices