Using Turbolift and Microplane to enact changes across many Git(Hub) repositories.
:bird: A GitHub action to tweet from a repository. Contribute to twitter-together/action development by creating an account on GitHub.
The first script I write in a new job:
gg (2 mins read).
Why writing a script to easily
git clone repos is my first step as a new starter.
Life without a REPL, and how to still be able to manipulate production which even has quite a few benefits over more one-off REPL-driven operations..
Something I've been thinking about for an alternative to
rails console for Go, and of course Brandur Leach has excellent thoughts about it
Recommended read: Operational convergence, for REPL-less languages like Go — brandur.org https://brandur.org/fragments/operational-convergence
Recommended read: Infrastructure as software https://www.justingarrison.com/blog/2022-06-01-infrastructure-as-software/
Unpopular opinion - automation is perhaps just as important for something you only do a couple times of year as something you do all day long. The reason for this is due to organizational memory, poor documentation, and team turnover
Scott Nasello (@scottnasello)Tue, 12 Apr 2022 15:41 +0000
Recommended read: More Than a Dozen Command Line Tools I've Written—and So Can You! · The Ethically-Trained Programmer https://blog.carlmjohnson.net/post/2018/go-cli-tools/
Recommended read: How we automatically fixed thousands of Ruby 2.7 deprecation warnings https://about.gitlab.com/blog/2021/02/03/how-we-automatically-fixed-hundreds-of-ruby-2-7-deprecation-warnings/
Create Executables, not Shell Aliases or Functions (2 mins read).
Why I create standalone executable scripts instead of shell aliases or functions.
I will be forever indebted to @pulumicorp, for allowing me to continue my "lazy coding" habit.
Two Brainy (@TwoBrainy)Thu, 26 Aug 2021 10:22 +0000
I've been reading this over the last few days wondering how I can get it working with my work Mac + Zoom, or if I use a pared down version
Recommended read: Making a Linux-Based “On-Air” Light for My Home Office w/ Camera & Google Calendar Integration https://joellemaslak.medium.com/making-a-linux-based-on-air-light-for-my-home-office-w-camera-google-calendar-integration-3e5ed35e8c8
This is something I really liked when doing Literate Programming at university. It's really nice to be able to wrap the code with written meaning, in a way that regular comments don't do as well.
Recommended read: Literate DevOps http://www.howardism.org/Technical/Emacs/literate-devops.html
I very much recommend learning how to use a more well-structured scripting language than Bash, as languages such as Ruby have a great standard library, a huge ecosystem of other libraries, and are commonly installed across machines - this is a great look at partially replacing shell scripts with Ruby
Recommended read: Enhanced Shell Scripting with Ruby https://www.devdungeon.com/content/enhanced-shell-scripting-ruby
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/
Recommended read: Using Bash to automate Rubocop fixes https://krmannix.com/2019/12/12/using-bash-to-automate-rubocop-fixes/
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
An interesting read, but I would personally say to stick to the language-specific process. Ie
Rakefiles for Ruby, a task in your
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
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
You're currently viewing page 1 of 1, of 44 posts.