Hello, I am the internet, and I am a screenoholic. Yes, I love screen. Never is an ounce of work accomplished on the command line without being encapsulated in the warm embrace of my favorite stateful terminal session manager. So much so that I quickly found myself being annoyed of always having to find my screen and never remembering what I named it, if I named it at all. And even worse were the times where I would lose my terminal to find that I was abandoned by my digital soul mate by never calling them before I stared. Oh how the innocence of youth lost so many critical vim undo buffers and ssh connections. I mean seriously, how many times can a guy type `ssh` in a day before hanging his self. 12. It turns out that number is 12. The resolution to my laziness was something of a revolution when I realized all the work I always forgot to do and never wanted to forget again could be easily accomplished automatically, every time I logged in. All hail the .bashrc. In other words, you can harness the power of .bashrc by intelligently invoking screen when you log in as well as giving a few helper functions along the way. Here is what I mean.
Posts Tagged: code
8
Aug 09
devbarjs: A cross-browser development tool and plugin framework.
The classic frustration with any web development generally arrives the first time you fire up a new web browser to see how your blood, sweat and tears end up looking outside of your favorite environment. This is the time when tears splatter across monitors, brilliant minds of less than a quarter century losing their hair faster than a diseased mammal at spring time, disaster striking in the form of dogs and cats living together, utter chaos. It may be a trailing comma on character 3,565 (of 35,355 lines of JS) or an easy mistake of using a position: fixed CSS attribute, inherited from a 3rd party library. A simple compilation of stupidity and carelessness combined to transform a functional LCD panel into a web of cracks; each creating a wake of red, purple, blue and yellow as it trails as to further indicate you are again down to only a single monitor from your original two. It is this pain that has brought me to give you devbarjs. I’m sorry and you’re welcome all wrapped up into a single, extensible package.
16
Jul 09
Generating Heat Maps Using Perl
A while back, I worked on a project with a company I’m working for and it eventually evolved into something I released to Perl’s open archive network, CPAN and chatted about for my first SPUG talk. Naturally, as the Conwaytistical Perl programmer I am, I figured why not write about it one more time for old times sakes. Generally speaking, Google has already found the documentation for the module which is all I really figure is necessary to explain it. The crazy thing is that people seem to be using this… a lot. Likely for the same reason I made it: there are no programmatic alternatives that I could find. With this unfortune comes the destruction of my inbox with questions and curiosities ranging from examples to the process I took for making this module in the first place. All things considered, I’m happy to see people using the module but it turns out I’m a little lazy and don’t like responding to strangers’ questions all that much. Born from that comes this page. When the forces of this are combined with the perldoc, I’m no longer needed and can feel much more at ease with the temperature of my shoulder as I ignore the trickle of emails that come to me. Lucky for you, I am a personal fan of direct examples that can be followed without the needless bloat of words, and this is what I’m going to (try to) do. The only predicate to this instruction set is that we will assume you are going to map the US. It’s possible to map the entire world, but we will only work with the US for now. Go USA!