Design Journal

Summary

I am going to try to create design journal entries that adhere to the advice given in The Design of Design: Essays from a Computer Scientist by Fred Brooks :

For designers to get the most learning from each design experience, they need to document how it evolves: not only the whats of the design, but also the whys by which it was reached. Moreover, such a rationale document is a priceless aid to system maintainers; it prevents many ignorant mistakes. Documenting trajectories and rationales is much harder than it first appears.

The Design of Design: Essays from a Computer Scientist
p. 185

Journal Entries

  1. 2018-09-15 : Motivation for series.
  2. 2018-09-18 : Review of the Ansible module, roles/oracle_user/tasks/user_groups.yml .
  3. 2018-09-20 : More design analysis of the Ansible module, roles/oracle_user/tasks/user_groups.yml .
  4. 2018-09-23 : Even more design analysis of the Ansible module, roles/oracle_user/tasks/user_groups.yml .
  5. 2018-09-24 : Decision to create Version 2.
  6. 2018-09-30 : Choice of GIT branch name.
  7. 2018-09-30 : Renaming modules for Version 2.
  8. 2018-10-01 : Meta file design analysis and new role name.
  9. 2018-10-03 : Analysis of “ PADSTOW: GI Directories Should Not Be Created on Standalone Systems (Unless ASM is used) ”.
  10. 2019-02-07 : Rectification of “ PADSTOW: GI Directories Should Not Be Created on Standalone Systems (Unless ASM is used) ”.
  11. 2019-09-24 : Design decisions made in the last major commit ( 2019-04-13 ).
  12. 2019-09-26 : The commit ( 2019-05-14 ) resolved the issue “ PADSTOW: Unable to determine Transparent HugePages Setting #59 ”.
  13. 2019-09-28 : The use of DBCA has been discontinued in favour of using SQL*Plus scripts from my sql-ocm12 repository.
  14. 2019-10-14 : Implemented SQL*Plus scripts from my sql-ocm12 repository.
  15. 2020-01-01 : Resolution of " Ping tests show connectivity across interconnect but large packets are dropped ".