Description
A Guideline Toward Cleaner Code
### Goals I expect the audiences to gain knowledge of the tools I mention and the primary usage of them. The tools will cover various aspects of software engineering (e.g., dependencies, testing, security, etc.). Also, I'll purpose how I combine all these tools in my development workflow as a sample for how the audiences can integrate these tools into their workflow.
### Outline for 30 minutes * Dependency Management (4 min) * Testing - Don't let your customer debug for you (4 min) * Style Check and auto-fix (4 min) * Task Management - No more repetitive typing (3 min) * pre-commit - Prevent committing bad code into codebase (3 min) * commitizen-tool - How good commit message can help (4 min) * Security (3 min) * Cookiecutter - Wrap up all the tools (3 min) * Q & A (2 min)
### Outline for 45 minutes * Dependency Management (5 min) * Testing - Don't let your customer debug for you (5 min) * Style Check and auto-fix (5 min) * Task Management - No more repetitive typing (5 min) * pre-commit - Prevent committing bad code into codebase (5 min) * commitizen-tool - How good commit message can help (5 min) * Security (5 min) * Continuous Integration - Assemble all the trivial steps (5 min) * Cookiecutter - Wrap up all the tools (3 min) * Q & A (2 min)