I’ve spent the last week working on implementing chef. The experience is frustrating to say the least. Instead of whining I wanted to take the time to write out some of my pain points and hopefully offer some constructive fixes to what I see as the wall in the learning curve. Now to be clear up front. Most of my problems aren’t with Chef, Ruby, or most of the core product; it’s with implementing it. To be more precise I think the failure REALLY is documentation. ...

Actually I should have called this where have I been. This seemed catchier though. In short the answer is I have been at my new job at SlickDeals They have keep me as busy as can be. Because of this major shift I changed a lot of habits; I stopped writing here as much, I stopped actively contributing to Pelican,1 and I also stopped posting to github. Be not too afraid. I still write plenty of code and fiddle around with everything. I just stopped posting most of it to github. I mostly use my own private stash instance. There is some publicly accessible code for those who are interested. The reason is that stash is SIGNIFICANTLY cheaper for my private repos so I just put most of my stuff there. I have been rethinking that lately since I miss a lot of the github community style. ...

It’s time for my monthly or so post! I wanted to go through and post about my OpenBSD firewall I built but that’s not 100%. Also I’m not ready to go on about anything amazing with puppet because without my lab being done puppet isn’t useful so lets go back to talking about my dev environment! I know Justin has been asking for this for a little while. Preface: Going “back” to Vim As a sysadmin at work I use vi a lot. Not even vim; vi. We have lots of unix boxes that default to vi as the installed editor and we don’t just go installing vim on everything. Personally I use vim a good amount on my machine since I spend a lot of command line time anyways. I know more than just a few of the commands but I really only consider myself a second or maybe third year vim user1 since I never used it full time to write code. I live the motion and use things like ci[ and C-v 5j x but I still fail to use multiple registers, buffers, or tabs… or even the leader commands. ...

All right! You read my post SSH Keys on a USB jump drive on Mac OS X (Mountain Lion Edition) and want to take this to the next level huh? Maybe having your config posting back to a jump drive and having to have it plugged in every time you want to log into something is sooooo lame! You often just leave it there, plugged in when you walk away from your work station. There has to be a better way… ...

Nope, not something to help unmount and flush your transmissions, it’s some tools for Transmission, specifically MY tools. I just though I would share that I redid this repository completely and cleaned up the Move & Stop script to cover some possible bugs and be a bit more python modern. If you had any problems with it not moving single files or just wanted some slightly cleaner code go grab the new version. ...

Here I Address the Eternal Struggle I want to store all my private keys on my jump drive I wear around everywhere. I use Win, Linux, but primarily Macs to do to my work so it needs to be some FAT variant formatted. I want to use the absolutely least hacky way. Windows and Linux were easy to overcome. In short for windows you use putty to make a putty key and in linux you do something shockingly similar to what is below… but I get ahead of myself. ...