![[site community profile]](http://www.dreamwidth.org/img/comm_staff.png){kind=small}
![[personal profile]](http://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
kjwcodeHello, folks!
For those who don't know me, my name's kj (yes, that's what I go by in off-line life, too -- blame my mom!) and I do a bit of code review here and there. Well, did a bit. Recently I've been encouraged to do more of it, and I'm certainly up to it.
One of the things I really like about Dreamwidth is the welcoming nature of the project. Both old coders new to the project and new coders in general are welcomed with open arms, and frankly, there's just not enough of that these days. Being a new coder in general is especially hard because it's hard to tell if you're going in the right direction, and waiting a long time for someone to look over your work, test it, give feedback, and put it up for commit can really slow one down when you're learning. Uncertainty is possibly the most difficult part of learning.
One way I'd like to help with that is to pay extra-special attention to the needs of newer coders and other people (who are, like me) new to the project. If you'd like me to review your code, feel free to ask; via e-mail, in IRC (#dreamwidth-dev on Freenode), or by Cc:ing me specifically on the bug, and I'll get to it as soon as I'm able. I can't make any promises on wait time (I've got a day job, a fiancée, a teenager, and a dog!), but I'll do my best to make it happen as soon as I can.
For those who don't know me, my name's kj (yes, that's what I go by in off-line life, too -- blame my mom!) and I do a bit of code review here and there. Well, did a bit. Recently I've been encouraged to do more of it, and I'm certainly up to it.
One of the things I really like about Dreamwidth is the welcoming nature of the project. Both old coders new to the project and new coders in general are welcomed with open arms, and frankly, there's just not enough of that these days. Being a new coder in general is especially hard because it's hard to tell if you're going in the right direction, and waiting a long time for someone to look over your work, test it, give feedback, and put it up for commit can really slow one down when you're learning. Uncertainty is possibly the most difficult part of learning.
One way I'd like to help with that is to pay extra-special attention to the needs of newer coders and other people (who are, like me) new to the project. If you'd like me to review your code, feel free to ask; via e-mail, in IRC (#dreamwidth-dev on Freenode), or by Cc:ing me specifically on the bug, and I'll get to it as soon as I'm able. I can't make any promises on wait time (I've got a day job, a fiancée, a teenager, and a dog!), but I'll do my best to make it happen as soon as I can.
