![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Dayness.
1:48
If R. lives up to his initial promise, everything is going to be as good as I thought. He's quite confident, good at reading code, and picking up the bits of the system that we put him in nicely. Which is to say that I dumped him into the most complex individual program in the system, and he took a couple days going through it looking for two bugs (which could have involved interaction with the second-most complex program in the system, which processes transactions from all the other programs). He came out of it having found the symptom, found the root cause of the problem, having found a quick, dirty, and superficially satisfying (but rough on the system) solution to the problem. And then he came to me, told me what he'd found, and told me that he thought that the solution he had found was probably not the right one, and gave me the reasons why. Yes, he missed one, but otherwise he had found where it was inefficient and such. He had half found his way to the right answer, knew exactly where to implement it when I confirmed it, and did so.
In the process, he noted a separate bug in the application end (the second-most-complex program mentioned above), and asked me about it. Ah, the rewards of virtue: I promptly assigned fixing it to him.
I know he's had help from M., M., and P., especially from M. That's what was supposed to happen. So he didn't exactly do it solo. But still. For someone on his seventh day of work, his fifth day in the code of a complex new system (and half the first day didn't really count, and the next two days weren't spent in any of the involved modules), that's a darned good job. So far, I'm very, very pleased.
I am listed to take a week of actual programming time to get something done. I told Y., my week estimate was for time with interruptions, so really 2 days of programming time, but he still listed a week of real time, even though I pointed that out. I don't mind all that much because it means I have more time to go over this one with a fine-tooth comb which I think it really needs to have happen.
2:36
Dammit, I'm not allowed to be sick. Just vaguely queasy so far, but I don't want to lose my weekend to it. Hopefully, my body's just complaining that I went from my usual semi-healthy food to (come on, boss!) cheap greasy (nummy) pizza and soda. Either would have been fine; both was probably overkill. I hope that's all it is. The throat entirely went away just a bit after I ate, the sinuses yielded to the soda and/or random reality (I didn't take a decongestant), so as long as the stomach is just a reaction to the food, I'm basically okay.
At least I'm getting stuff done. Getting stuff done is good.
4:26
The missing CD-set came back. Y. is going to be careful that he knows who gets it now. Good. The secretary is acting like we're nuts to want to lock CDs up, no one here is a thief. Well...fair enough; if we thought they were, we wouldn't employ them. But that doesn't mean that no one here is forgetful; many of us are, and this way there's an extra check on borrowing the CD, forgetting to return it, and not having anyone go looking for it until after you can't remember whether you put it back. :P
And I count myself in that list. I have inadvertently held disks "hostage" for a few weeks in the past because I forgot to return them, then forgot I had them. It's just a better system.
...yay, end of day stuff. Going to do my timesheet soon, after I check in a few more changes, and head out.
I'll likely work some more tonight, but I don't know how much, so...bill that in next week.
If R. lives up to his initial promise, everything is going to be as good as I thought. He's quite confident, good at reading code, and picking up the bits of the system that we put him in nicely. Which is to say that I dumped him into the most complex individual program in the system, and he took a couple days going through it looking for two bugs (which could have involved interaction with the second-most complex program in the system, which processes transactions from all the other programs). He came out of it having found the symptom, found the root cause of the problem, having found a quick, dirty, and superficially satisfying (but rough on the system) solution to the problem. And then he came to me, told me what he'd found, and told me that he thought that the solution he had found was probably not the right one, and gave me the reasons why. Yes, he missed one, but otherwise he had found where it was inefficient and such. He had half found his way to the right answer, knew exactly where to implement it when I confirmed it, and did so.
In the process, he noted a separate bug in the application end (the second-most-complex program mentioned above), and asked me about it. Ah, the rewards of virtue: I promptly assigned fixing it to him.
I know he's had help from M., M., and P., especially from M. That's what was supposed to happen. So he didn't exactly do it solo. But still. For someone on his seventh day of work, his fifth day in the code of a complex new system (and half the first day didn't really count, and the next two days weren't spent in any of the involved modules), that's a darned good job. So far, I'm very, very pleased.
I am listed to take a week of actual programming time to get something done. I told Y., my week estimate was for time with interruptions, so really 2 days of programming time, but he still listed a week of real time, even though I pointed that out. I don't mind all that much because it means I have more time to go over this one with a fine-tooth comb which I think it really needs to have happen.
2:36
Dammit, I'm not allowed to be sick. Just vaguely queasy so far, but I don't want to lose my weekend to it. Hopefully, my body's just complaining that I went from my usual semi-healthy food to (come on, boss!) cheap greasy (nummy) pizza and soda. Either would have been fine; both was probably overkill. I hope that's all it is. The throat entirely went away just a bit after I ate, the sinuses yielded to the soda and/or random reality (I didn't take a decongestant), so as long as the stomach is just a reaction to the food, I'm basically okay.
At least I'm getting stuff done. Getting stuff done is good.
4:26
The missing CD-set came back. Y. is going to be careful that he knows who gets it now. Good. The secretary is acting like we're nuts to want to lock CDs up, no one here is a thief. Well...fair enough; if we thought they were, we wouldn't employ them. But that doesn't mean that no one here is forgetful; many of us are, and this way there's an extra check on borrowing the CD, forgetting to return it, and not having anyone go looking for it until after you can't remember whether you put it back. :P
And I count myself in that list. I have inadvertently held disks "hostage" for a few weeks in the past because I forgot to return them, then forgot I had them. It's just a better system.
...yay, end of day stuff. Going to do my timesheet soon, after I check in a few more changes, and head out.
I'll likely work some more tonight, but I don't know how much, so...bill that in next week.