I agree with Guido, in that I think
[ x * 2 for x in some_list if x < 12 ]
is much easier to read than the equivalent
map(lambda x:x * 2, filter(lambda x:x<12, some_list))
There's too many things I'm interested in. There's also many hyped technologies and subjects out there that I am disinclined to pay attention to.
When I have the impulse to dig into some subject, I find myself wanting a list to run-down so I know in advance where that idea might land given all the other things I already have in-progress.
Listed in approximate order from high- to low-interest.
Vendoring is the moving of all 3rd party items such as plugins, gems and even rails into the /vendor directory. This is one method for ensuring that all files are deployed to the production server the same as the dev environment.
The activity described above, on its own, is fine. It merely describes the deployment location for various resources in an application.
Unfinished draft; do not use until this notice is removed.
We were seeing some unexpected behavior in the processes that Jenkins launches when the Jenkins user clicks "cancel" on their job. Unexpected behaviors like:
git log --graph
I will maybe someday get around to dusting off my C and making these changes myself unless someone else does it first.
Imagine a long-running development branch periodically merges from master. The
git log --graph --all --topo-order is not as simple as it could be, as of git version 18.104.22.168.
It doesn't seem like a big deal in this example, but when you're trying to follow the history trails in ASCII and you've got several different branches displayed at once, it gets difficult quickly.