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.
Leave a comment