![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
I'm feeling better. I still don't know if it was food poisoning or actual illness, but whatever it was, to my relief, is gone.
I missed a code review yesterday because of the crud, so today I went over my comments with the author. He said I obviously read the code more thoroughly than any of the people who were actually there. I think it was a compliment. :-) I've been invited to another code review (different author) tomorrow; the current code marshall likes it when I participate in code reviews, it would appear. (The code marshall decides what will be reviewed and by whom; the position changes monthly. Usually we have one code review per week, sometimes two.)
I wrote actual code against our API this week, starting from first principles instead of starting from other people's applications (or test code). It's nothing especially fancy or clever, but it's just what it needs to be: a simple, basic example on which to build more-involved examples, in an organized fashion, for our customers. This series of apps, which I'm doing with a senior developer (he's going to end up doing most of the coding work, but we're participating equally in specification and design) will form the basis of some tutorials that I will write. The whole experience makes me happy, even if I spent way too long banging my head against the wall Tuesday over what turned out to be a stupid mistake on my part. Still, if I don't get it the customers never will, so better that I bang my head against these things than hand-wave around it and assume I could write apps against the API....
I missed a code review yesterday because of the crud, so today I went over my comments with the author. He said I obviously read the code more thoroughly than any of the people who were actually there. I think it was a compliment. :-) I've been invited to another code review (different author) tomorrow; the current code marshall likes it when I participate in code reviews, it would appear. (The code marshall decides what will be reviewed and by whom; the position changes monthly. Usually we have one code review per week, sometimes two.)
I wrote actual code against our API this week, starting from first principles instead of starting from other people's applications (or test code). It's nothing especially fancy or clever, but it's just what it needs to be: a simple, basic example on which to build more-involved examples, in an organized fashion, for our customers. This series of apps, which I'm doing with a senior developer (he's going to end up doing most of the coding work, but we're participating equally in specification and design) will form the basis of some tutorials that I will write. The whole experience makes me happy, even if I spent way too long banging my head against the wall Tuesday over what turned out to be a stupid mistake on my part. Still, if I don't get it the customers never will, so better that I bang my head against these things than hand-wave around it and assume I could write apps against the API....