One of my colleagues shared an article on writing (good) Git commit messages today: How to Write a Git Commit Message. This excellent article explains why good Git commit messages are important, and explains what constitutes a good commit message. I wholeheartedly agree with what @cbeams writes in his article. (Have you read it yet? If not, go read it now. I'll wait.) It's sensible stuff. So I decided to start following the
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| const greet = (message, name) => { | |
| console.log(`${message}, ${name}!`) | |
| } | |
| greet('Hello', 'John'); | |
| greet('Hola', 'Antonio'); | |
| greet('Ciao', 'Luigi') | |
| code is DRY because code uses arrow function and parameters to make code reusable |