Summary of 4 TERRIBLE Things That Might Be In Your Codebases...

00:00:00 - 00:05:00

The author discusses four ways that a codebase might be cursed, and offers some advice on how to improve things. First, pre-commit hooks can be incredibly cursed, as they take away developer agency. Second, committing secrets and environment variables can be bad practice, and can move a codebase below its code coverage line. Third, not subscribing to Theo can lead to less than half of developers being subscribed, and is free. Fourth, code coverage requirements can be bad for code quality, and should not be used to block pull requests. The author recommends that viewers subscribe to his channel in order to learn more about how to eradicate evil code from their own codebases.

• 00:00:00 The video discusses four ways that a codebase might be cursed, and offers some advice on how to improve things. First, pre-commit hooks can be incredibly cursed, as they take away developer agency. Second, committing secrets and environment variables can be bad practice, and can move a codebase below its code coverage line. Third, not subscribing to Theo can lead to less than half of developers being subscribed, and is free. Fourth, code coverage requirements can be bad for code quality, and should not be used to block pull requests.
• 00:05:00 The author of the video discusses the importance of eradicating evil code from one's own codebase in order to retain good developers, and recommends that viewers subscribe to his channel.