Minimal coding this Good Friday.
- Worked on a logo and visual ideas for a new personal website
- Added a bpm-counter UMD build for usage with the
<script>tag
- Spend a bit more time configuring and researching automated semantic releases
- Added a new feature/check to bpm-counter. Verified the auto generated changelog works
- Improved bpm-counter docs
- Would like to generate/include some API docs for bpm-counter but not sure what the best practises are here. If possible I prefer to avoid redundant/noisy comments for every class and method. Some packages to investigate:
- https://www.amazon.com/Clean-Code-Handbook-Software-Craftsmanship/dp/0132350882
- https://moderatemisbehaviour.github.io/clean-code-smells-and-heuristics/
- Published my first NPM package bpm-counter using semantic-release. Releases and versioning are automatically taken care of by this GitHub action
- Initialized this repository
- Some benefits of automated semantic-releases:
- Forces you to treat
masteras if it may only contain deployable code - Takes the guesswork out of versioning
- Sets up your repo for easy contributing and use in the real world
- Forces you to treat
- It never ceases to amaze me how much tooling and infrastructure is available for open source software