How I manage my dotfiles (8 mins read).
A deep dive into how managing my dotfiles has (not) evolved over the last 10 years.
How I manage my dotfiles (8 mins read).
A deep dive into how managing my dotfiles has (not) evolved over the last 10 years.
Learn how to build tools (6 mins read).
A guest post on Letters to a New Developer about learning to automate and build tools to progress in your career.
Performing bulk changes across Git(Hub) Repos with Turbolift and Microplane (4 mins read).
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
I have been a Vim user for 12 years and one important thing that you learn the first days using it is that you can be super efficient…
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
nobody: me to anything that absolutely does not need to be automated: but wait, what if we automated this?Rizèl Scarlett 🇦🇬🇬🇾 (@blackgirlbytes)Tue, 12 Apr 2022 18:05 +0000
So here's why I bought a receipt printer: Every time one of my GitHub repos gets a new issue, I now get a physical ticket printed out on my desk 🪄Andrew Schmelyun (@aschmelyun)Thu, 24 Mar 2022 11:44 GMT
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.Post details
In which I ramble about being a "lazy coder" with Pulumi and scripts. by Two Brainy @racket100 - racket.com/twobrainy/rrdT5Two Brainy (@TwoBrainy)Thu, 26 Aug 2021 10:02 +0000
Two Brainy (@TwoBrainy)Thu, 26 Aug 2021 10:22 +0000
I've been working on something pretty cool at @equinixmetal ... I think y'all are going to like it. Have you met our good friends @PulumiCorp and @kubernetesio yet?David McKay (@rawkode)Thu, 08 Jul 2021 21:45 +0000
I've used https://github.com/palantir/bulldozer before and that's been good
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
Good morning programmers, let's automate!
Ben Porter (@eigenbom)Fri, 04 Sep 2020 21:00 +0000
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.
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
I need to manually alter about 80 blog posts. I reckon it'll take me at least 2 hours. ⋯ OR ⋯ I could spend ~4 hours trying to write a script to automate it. Choices, choices!Terence Eden (@edent)Wed, 01 Jul 2020 15:35 +0000
Why spend 8 minutes doing a one-time task manually when you can spend 2 hours attempting to automate it?
Kelly Vaughn 🐞 (@kvlly)Tue, 28 Apr 2020 16:33 +0000
This is a great resource I've used in the past for learning how best to approach automation testing with a website.
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"?
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
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.
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
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
.
You're currently viewing page 1 of 1, of 46 posts.