I hereby claim:
- I am hews on github.
- I am tpt_phughes (https://keybase.io/tpt_phughes) on keybase.
- I have a public key ASCITOypQntkRo56sMswnkgm7dQ_Db3jAYBYmVxRwQa4wgo
To claim this, I am signing this object:
#!/usr/bin/env perl | |
use strict; | |
use warnings; | |
my $input_image_id = $ARGV[0]; | |
my $input_image_sha = `docker inspect ${input_image_id} --format='{{.Id}}'`; | |
exit if ( $? != 0 ); | |
chomp $input_image_sha; |
I hereby claim:
To claim this, I am signing this object:
I hereby claim:
To claim this, I am signing this object:
At the 2004 Ruby Conference, Jamis Buck had the unenviable task to explain Dependency Injection to a bunch of Ruby developers. First of all, Dependency Injection (DI) and Inversion of Control (IoC) is hard to explain, the benefits are subtle and the dynamic nature of Ruby make those benefits even more marginal. Furthermore examples using DI/IoC are either too simple (and don’t convey the usefulness) or too complex (and difficult to explain in the space of an article or presentation). I once attempted to explain DI/IoC to a room of Java programmers (see onestepback.org/articles/dependencyinjection/), so I can’t pass up trying to explain it to Ruby developers.
Thanks goes to Jamis Buck (the author of the Copland DI/IoC framework) who took the time to review this article and provide feedback.