Dependencies Code Diary Entries

This is part of the Semicolon&Sons Code Diary - consisting of lessons learned on the job.

• Avoid specifying dependencies that are subdependencies of your other dependencies
• Avoid wrapper packages over command line CLIs
• Check if OS upgrade breaks software and important hardware
• Dependency hell strategies
• Expect libraries to break when using a different version of the language
• Future proof by checking for existence before binding functionality
• Modify the library imports inline with your code
• Never assume API uses your naming conventions
• Scan readme before installing
• Tell user what to change when they call outdated API
• Try switching version if error opaque
• Update the ultimate dep before the wrapper
• Weird syntax errors may be due to even minor language version differences
• When in doubt assume arguments are all of same type