03/17/10 07:35 - ID#51209
But soon -- very soon -- it will help decide which kids get into, or not into, colleges. Kinda scary to hold so many futures in my hands. This is pretty much the biggest thing I've ever done professionally.
One downside, it's making me look old and grumpy:
But I can live with that :)
I also got a really nice annual review, I'm pretty down on myself usually but feel awesome for a few days after something like that going well.
Back to work...
11/19/09 04:24 - ID#50345
Sidebar / tabbed panes:
Docs & History:
So many little things to do before launch in a couple months, but I'm really excited at how well this is turning out.
12/05/08 10:51 - ID#46969
Ordering an SSL Cert and Pointing DNS
11/11/08 12:44 - ID#46646
We're going for paired mirrors to start, then splitting out each VM container type into their own tiered clusters as we need to add capacity and can judge bottlenecks.
I know no one cares about this but me, but it's my journal so, what the hell :)
10/29/08 10:38 - ID#46405
10/20/08 09:49 - ID#46219
Pair Programming Starts Tomorrow
We've got our automated testing down pretty well at work, so on to the next step. We start pair programming every single day in the afternoons tomorrow. It will be interesting to see how this goes, if we can make a habit of it. It's the best way to learn.
( - pair programming )
We aren't going to do it full time, as the linked page suggests, but even part time should be very, very useful. I've learned to hate silo-style development. Everyone on a team should share ownership of every single line of code. There should not be anywhere that a developer fears to tread.
It's a little bit scary to work so closely with someone, the times that I've paired in the past - you have to fumble around and show your inadequacies, but it's worth it when you teach each other new things and hash out designs before they're halfway done. Code is easy to change as you're speaking about it and hard to change later.
The alternative - well, it is very nice to work alone and polish your work before you show it to other people, but it's just not as communicative in the end. I totally go off in the weeds when working alone.
We're going to rotate the pairs - most of the time it will be one Ruby expert paired with one former Fox Pro programmer who is learning Ruby, but is a domain expert in the software. It should be a good match. Everyone will work with everyone though, just to make sure we can all talk together.
Code reviews are coming, probably next month, too.
So the arc looks like -
Phase I - automated test suite: TDD and feature stories.
Phase II - pair programming.
Phase III - weekly team code reviews.
I love my job so much. I love love love it.
10/18/08 08:04 - ID#46182
It's not really a promotion in the sense of title change, more of a coordinator role (still spend 80% of my own time writing code), but it's going to be nice when I have my yearly review next April to be able to claim credit for how nice things are going.
The best part of the job? Saying no to stupid things before they are forced upon us.
We're digging into a ground-up rewrite of one of our core products, an evaluation tool for Physical Therapy students. It's going much smoother then I had anticipated, although two of the guys we thought we'd have had on the project months ago are only now able to lay down Visual Studio and Fox Pro and join us.
There are two other ongoing projects too, so 3 things to keep tabs on and moving forward, plus all the training. Training devs is nice - another way to shape the company culture and make sure that we're doing things the same way. They really like Ruby over Fox Pro - big surprise :)
Thank God for the ADD drugs. I'd be hanging myself otherwise.
10/02/08 07:43 - ID#45886
That's all :)
09/05/08 03:37 - ID#45588
UB Faculty/Staff LOL!
The company I work for is just somewhat related to UB, I am not actually teaching or anything crazy.
I am eligible for staff parking on campus though :)
03/16/08 11:31 - ID#43687
Project Color Palette