Why You Should Write a CLI Tool for Your Organisation
Recommended read: Why You Should Write a CLI Tool for Your Organisation https://www.surminus.com/blog/why-you-should-write-a-cli-tool-for-your-org/
Why You Should Write a CLI Tool for Your Organisation
Recommended read: Why You Should Write a CLI Tool for Your Organisation https://www.surminus.com/blog/why-you-should-write-a-cli-tool-for-your-org/
This is a great resource I've used in the past for learning how best to approach automation testing with a website.
Recommended read: Obey the Testing Goat! https://www.obeythetestinggoat.com/
Using Bash to automate Rubocop fixes
Recommended read: Using Bash to automate Rubocop fixes https://krmannix.com/2019/12/12/using-bash-to-automate-rubocop-fixes/
Blogcop: A GitHub app that helps you manage your Jekyll blog
An interesting idea, but surely you'd not want to break existing links to your articles, and instead have it update the article to say "this may be outdated, we're reviewing this"?
Recommended read: Blogcop: A GitHub app that helps you manage your Jekyll blog https://www.ombulabs.com/blog/github/jekyll/ruby/blogcop-for-jekyll.html
The Language Agnostic, All-Purpose, Incredible, Makefile
An interesting read, but I would personally say to stick to the language-specific process. Ie Rakefile
s for Ruby, a task in your build.gradle
or npm run deps
as it'll handle things nicer in a language / stack you're more familiar in, although I totally see why you'd want a language-agnostic interace
Recommended read: The Language Agnostic, All-Purpose, Incredible, Makefile https://blog.mindlessness.life/2019/11/17/the-language-agnostic-all-purpose-incredible-makefile.html
This is another interesting article about automation, and how it slowly incurs time costs by waiting for the right time to properly tackle the automation, rather than piece-by-piece.
Recommended read: Manual Work is a Bug https://queue.acm.org/detail.cfm?id=3197520
Do-nothing scripting: the key to gradual automation
This is a really interesting way of approaching automation in a gradual way - make the documentation in code, then take that code and slowly iterate over it until you have a fully automated solution. I like it - obviously we always want to have the final product, but it's a good way to get there slowly
Recommended read: Do-nothing scripting: the key to gradual automation https://blog.danslimmon.com/2019/07/15/do-nothing-scripting-the-key-to-gradual-automation/
Automating Promotion of Jekyll Posts from Draft to Post (2 mins read).
The handy script I've created to automate publishing a draft in Jekyll, with handy Zsh + Bash autocomplete.
My editorial workflow for blog posts (8 mins read).
Taking you through the journey I go on when writing blog posts, from ideation to publishing the post.
Deploying to Netlify using GitLab CI (3 mins read).
How adding two lines to my .gitlab-ci.yml
migrated my existing site from GitLab Pages to Netlify.
Saving Repetition with Git Commit Templates (3 mins read).
Speed up your commit message writing by providing a template for when you run git commit
.