1. In-depth Logging
   1. What
      1. Read Only Access to Terminal Logs (Ex: AWS)
      2. Read Only Access to Code Base
      3. Provision for Running Code Locally
   2. Why
      1. Direct way to read stack trace
      2. Direct way to look where to fix the code
   3. How
      1. Code Collaboration Tools support Read Only Accesses
2. Showing everyone how to read multipage JSON Req / Res
   1. What
      1. It's important to know how to read data
   2. Why
      1. Draining to read big JSON
   3. How
      1. Covert JSON to CSV
      2. JSON Pretty Formatters
3. Clear Error Messages
   1. What
      1. Makes software easier
   2. Why
      1. Helps understand what's gone wrong
   3. How
      1. Debug Mode can provide verbose logs
      2. Debug Mode can be made hard to find for security reasons
4. Reduce Silent Failures
   1. Why
      1. Frustrating Experience
   2. How
      1. Convert NON Success / Unknown Exception Codes to a Popup
5. Display Entity DB Records & Make Entity Model Values Editable
   1. What
      1. DB contain all the info
   2. Why
      1. See all info that's meaningful
   3. How
      1. Give super admins access to edit all entity model values
6. Read-only access to DB
   1. Why
      1. Useful when edit is not required and DB data can save you Dev Time
7. Regular Error Alerts
   1. What
      1. Error Reports
      2. Periodic / Summary Report
   2. Why
      1. What Failed? Where? Who?
   3. How
      1. Ex: AWS Support this
8. Default OTP Responses
   1. What
      1. Hardcoded OTP
   2. Why
      1. Saves Time
9. Controlling Variables & Setting Placed in Config
   1. What
      1. Variables
      2. API Keys
   2. Why
      1. Make it easy for anyone to modify system wide settings
   3. How
      1. Store the base config files in source control
10. Anonymising Production Data
    1. What
       1. Masked Prod Data
    2. Why
       1. Nothing better than realistic production data
    3. How
       1. Script that anonymises production data
       2. Add randomization too
11. Testing Features & their Cron Tabs Separately
    1. What
       1. Cron tabs trigger things when they detect a change in status
    2. Why
       1. It's important to test the interaction of cron and feature
12. Speed Up Individual User Creation
    1. What
       1. Creating users via API (Postman) over UI
    2. Why
       1. API >>> UI (Speed)
13. Making copies of files downloadable
    1. What
       1. Have copies of file before and after they are processed by the software
    2. Why
       1. There might be changes that you don't expect
       2. Ex: Diff Derived, Diffchecker
14. Downloads of aggregated data
    1. What
       1. Bulk Download of entire package as once
    2. Why
       1. Verifies if the internal engine is running correctly.
15. Size of Change
    1. What
       1. Smaller releases to staging before each out for testing
    2. Why
       1. Makes it easier to understand the impact of each change.
    3. How
       1. Release codes more often
16. Mocks and Stubs
    1. Why
       1. Remove blocking dependencies