karzilla: a green fist above the word SMASH! (Default)
karzilla: a green fist above the word SMASH! (Default)
I didn't get very much dev work done in the month of September. Apologies to anyone who missed my virtual presence - my mom, dad, and best friend are all dealing with various ailments and one of my kids unexpectedly decided to join the Cub Scouts. I think I spent more time in my car than at home. In fact I am actually in a hospital waiting room as I write this entry. Tethering FTW!

I will try to get all the recent pull requests reviewed in the next few days. It's about time for me to do a new Current Contributors list as well. However, I don't anticipate doing another code push until the end of the month at the earliest - most likely I will wait until after [personal profile] kaberett's London contributor event, which is scheduled for November 7th.

big news

Jul. 7th, 2015 03:15 am
karzilla: a green fist above the word SMASH! (smash)
So, yes, in case you hadn't heard - my account got upgraded! I am now Dreamwidth's official DevCom.

I'm celebrating with a new icon. KARZILLA SMASH.
karzilla: a green fist above the word SMASH! (Default)
I want to start using this journal again, but I can't continue from where I left off. Too much has changed. The original title of this journal was "Kareila's Bugzilla" and most of the information was directly related to tracking my progress with a ticketing system that we haven't used in over a year.

I considered deleting or hiding all the old entries, but there are some that I think might still provide useful information to other developers or help me refresh my memory about certain ongoing projects. I've only removed the ones that were just me celebrating achievements or venting frustration with code that in most cases I didn't even remember writing.

I still love Dreamwidth and enjoy working on it, although I can't work on it hour after hour, day after day, like I did the first two years I was here. The pace I kept would burn out anyone, and in retrospect, I certainly think that's the best description for what happened to me for a while there. But when I look back at where we started and see how far we've come and how much we've accomplished, I feel like I have a lot to be proud of, both on my own behalf and on behalf of the community.

We struggled when we moved from Mercurial to Git. We struggled again when we lost Bugzilla. I'm sure we'll face more challenges in the future. But I am optimistic, and thankful.

At the end of the day, one thing is the same: I am Karzilla, Destroyer of Bugs. I fight for the users, and my code machete is always close at hand.
karzilla: a green fist above the word SMASH! (Default)
I haven't quite psyched myself up to dust off my DW code yet, although my outstanding vgifts code did get committed, and I'm pleased about that. I still have quite a few other branches dangling, though, and some of them just need testing, which means updating my dev environment. Ugh.

In the meantime, I've been spending my time lately writing lightweight webapps using the Perl Dancer framework. I love how little code it requires to get a simple idea up and running, with no "dev environment" at all. Since the web service is built in, I don't have to fuss around with Apache, and it's very easy to attach the Perl debugger if things begin to act weird.

One of my Dancer projects is on Github: Clean All The Things, a tool for tracking housework task status. When I first started that project, it was just a command line script and a database file, but it has gradually grown in complexity. I'm very pleased with how it's turned out, though.

I love using Template Toolkit. I love how it separates the page display logic from the rest of the code, but is still powerful enough to handle concepts like FOREACH. I love that I can edit a page template and reload my browser to see the changes without having to restart the web server. I love how each call to render a template passes its own little package of variables to use, so I don't have to worry about scoping. I don't think I'll ever want to write web pages any other way again.

I do still bump up against occasional quirks, though. Today I was writing a page that used hardcoded hash keys of the form "foo.2a" and TT interpreted that as "foo.2" followed by an unexpected token "a". I had to write it as foo.${'2a'} before it could understand me.

Anyway, to make a long story short, I have been writing code lately, and I'll try to transition back into coding for Dreamwidth after I finish my current pet project.
karzilla: a green fist above the word SMASH! (Default)

Bug counts: resolved 343, assigned 8, needs-review 3



The display settings page is getting awfully crowded. Maybe we could separate journal settings from site settings, or style settings from content settings? Surely there's some division that would make sense.
karzilla: a green fist above the word SMASH! (Default)
You know what would really help me be even more productive? Being able to classify bugs as needs-perl, needs-sql, needs-javascript, needs-translation, needs-css, needs-s2, needs-xmlrpc, needs-obscure-backend-stuff-no-one-understands-except-dre...

I mean, I know there's already some categories, but pretty much EVERYTHING I do ends up filed as either Misc. Frontend or Misc. Backend, and being able to sort those out into areas of expertise needed would be a big help, I think. Just a thought.
Page generated May. 29th, 2017 05:42 am
Powered by Dreamwidth Studios