even if that one thing is crastinating. Sure, crastinating isn't a word, but I'm a pro at it (like quite a few other people, I'm sure). I'm not entirely enthused on how The Free Dictionary defines procrastinator (To put off doing something, especially out of habitual carelessness or laziness). I'd like to think I have potentially better things to do (read: watch TV or play Burnout Revenge with my five year old son). "You say tomato, I say tomahto". In the end, procrastination forces me to work under pressure, albeit self-induced pressure, but I find that I work that best way, so perhaps my procrastinating is not because I don't want to the actual task but because I enjoy waiting until the last minute to push myself [to the limit]
or why it works for me..
I am a fan of extreme programming, without even really knowing it. I'll admit, I'm ignorant to all the buzzwords: scrum development, agile software development, etc. I don't care what you call it, it's all about getting stuff done and for me, it Just Works.
I am by no means a seasoned perl developer. confound, rafl, perigrin, ribasushi, rjbs, mst, dhoss, jayk, nothingmuch, castaway, robkinyon, Caelum, Khisanth, autarch, t0m, Sartak, jrockway, fRew and a multitude of others can attest to this. I am aware that I'm not good enough but here I am, getting paid by Google to develop a shiny new SQL::Translator. I'll freely admit, outside of the original proposal, I have no bonafide plan as to how I'm developing this. All I am going on is I know what the end needs to do. If you look at the git commit history, you'll see things added and deleted regularly. I am aware this style doesn't fit everyone, but it works for me. I'm sure there are instances where I have wasted time or duplicated effort, but more importantly for me, I'm *learning*.
If you've made it this far in the post, kudos for reading my lack of writing skills. I wouldn't even be posting these posts if it wasn't for Ironman. Aside from not being a very good perl developer, I am also by no means a blogger. I hate writing. I take that back, the only writing I enjoy is programming. But, I suppose it doesn't hurt to JFDI and blog. I am not going to say I've gotten good at it (there's no way I have) but I've at least become consistent with my posts and I'd like to think they've at least been somewhat useful to someone other than myself.
Per one of jayk's articles at catalyzed.org, I am one of those newbies and I feel I have been able to suceed (I never thought I'd ever submit patches for SQL::Abstract, DBIx::Class, Catalyst, etc, let alone be rewriting a whole module) because I decided to JFDI.
I am a fan of extreme programming, without even really knowing it. I'll admit, I'm ignorant to all the buzzwords: scrum development, agile software development, etc. I don't care what you call it, it's all about getting stuff done and for me, it Just Works.
I am by no means a seasoned perl developer. confound, rafl, perigrin, ribasushi, rjbs, mst, dhoss, jayk, nothingmuch, castaway, robkinyon, Caelum, Khisanth, autarch, t0m, Sartak, jrockway, fRew and a multitude of others can attest to this. I am aware that I'm not good enough but here I am, getting paid by Google to develop a shiny new SQL::Translator. I'll freely admit, outside of the original proposal, I have no bonafide plan as to how I'm developing this. All I am going on is I know what the end needs to do. If you look at the git commit history, you'll see things added and deleted regularly. I am aware this style doesn't fit everyone, but it works for me. I'm sure there are instances where I have wasted time or duplicated effort, but more importantly for me, I'm *learning*.
If you've made it this far in the post, kudos for reading my lack of writing skills. I wouldn't even be posting these posts if it wasn't for Ironman. Aside from not being a very good perl developer, I am also by no means a blogger. I hate writing. I take that back, the only writing I enjoy is programming. But, I suppose it doesn't hurt to JFDI and blog. I am not going to say I've gotten good at it (there's no way I have) but I've at least become consistent with my posts and I'd like to think they've at least been somewhat useful to someone other than myself.
Per one of jayk's articles at catalyzed.org, I am one of those newbies and I feel I have been able to suceed (I never thought I'd ever submit patches for SQL::Abstract, DBIx::Class, Catalyst, etc, let alone be rewriting a whole module) because I decided to JFDI.
after I spent all that time figuring out how to run Movable Type with Catalyst::Controller::CGIBin, I have moved my blog from my linode to my Dreamhost account. No headaches, the only 'change' I made was to my .htaccess,
I also have a Google Summer of Code blog at http://gsoc.enotime.net to document my rewrite of SQL::Translator for GSoC 09.
I also have a Google Summer of Code blog at http://gsoc.enotime.net to document my rewrite of SQL::Translator for GSoC 09.
I have migrated my blog from Angerwhale to Movable Type. In doing so, I also hacked around to get MT to run under Catalyst::Controller::CGIBin. It was (surprisingly) mostly straightforward,
except having to add a new CGI object to lib/MT/Bootstrap.pm
much thanks to confound for helping me work all this out.
except having to add a new CGI object to lib/MT/Bootstrap.pm
much thanks to confound for helping me work all this out.
well, GSoC 2009 is upon us. Here are pictures of the schwag that accompanied the pre-paid Visa. Now, I have to figure out how to juggle everything else already going on to work on SQL::Translator.
well, after discussion, I have decided not to patch angerwhale any further and start my own blog based on catalyst. I'll be dogfooding it here (and perhaps my other domains). This should be an interesting project to learn Moose, Catalyst, DBIx::Class and KiokuDB. Hopefully I can get this done alongside my GSoC project and my aspirations for a Moosified/POE/DBIx::Class netdisco (and eventually SNMP::Info).
so, I hacked around on angerwhale and I ported it from Crypt::OpenPGP to Crypt::GpgME. These changes are available on my github fork, specific changes are here. The fork has a few other chang es, including moving from NEXT to Class::C3 next::method and making it send text/html for IE. The IE 'patch' added another dependency, Catalyst::Plugin::Browser, which is really just a nice wrapper around HTTP::BrowserDetect. I also decided to bump the requirement for Catalyst itself to 5.8.
Welcome to my blog, I am not very good at this, but I am trying since we (the perl community) were called out (more information can be found here). They should all aggregate into Planet Iron Man
