Bloggy

So. Prototype has been going fairly well. I’ve been doing good so far on my casualty watches, although the harder 3^rd drill set casualties are on the way for my next two watches.

There’s a roadbump tomorrow though. Thanks to an unfortunate confluence of events, I will be on duty for 16 hours tomorrow. :-(

Basically there is a training event that I must complete before my Final Watch Board, which won’t fit into the normal shift schedule. That’s no problem, we’ll just do it after shift, for a normal 12 hour day.

Then as I am auditing my Qualification Standard, I notice that one of the watches I must stand before Final Watch Board was never scheduled for me. So the choice is either to stand that watch back to back with one of my Engineering Officer of the Watch billets, or get the watch done on my own time. Unfortunately, we could only squeeze that into tomorrow morning.

So now that’s a 16 hour work day. And I have to be there at the beginning of the extra watch to observe the watch turnover. And since I will be on watch the other 8 hours of the day, I need to be in coveralls. And we can’t just stroll into Prototype wearing coveralls, so that means I need to be there even earlier so I can change at Prototype. Yuck.

Although it is nice that I went from struggling to be 2% ahead of the curve to being 13.5% ahead without even having all of my signatures scanned in. :-) I’ll be watch-complete very early compared to other classes, and they’re even trying to push the 8-hour Comprehensive Exam early for us as well to give us extra time off and more time to prepare for the Final Oral Board.

Posted by mpyne under Navy & Personal | No Comments »

I stood my first casualty watch today. (That is, a watch where the staff will run drills on you to see how your react and perform while recovering the plant).

It actually went fairly well. The only casualties that were even serious were well handled by the enlisted students and so the plant was quickly in a safe condition again while I worked through the applicable casualty procedures.

I seem to still need some more practice though. Often times I would give an order and hear, “Uh, sir, recommend you do this first.” And of course, they would be right. Even better is when I would try to communicate with the Engine Room loudspeaker and end up announcing things in the Control Room by accident. I think I’m getting the hang of everything however.

I was hoping the worst would be over by the end of this week but I still have to stand as many Engineering Officer of the Watch shifts in the next week as I have in the last two weeks. :-(

In KDE-related news, those paying attention to the various KDE development mailing lists may have heard that Coverity, a company that has developed a sophisticated source code analyzer tool, has started examining the KDE source code base. What thrills me is that they are using kdesvn-build to perform the actual build of KDE. So the past few days I’ve been trying to adjust kdesvn-build as needed to make the Coverity output more useful. So there have been a few fixes related to the recently-added support for CMake. I haven’t heard anything else since then so I’m just going to assume that everything is going swimmingly. ;-)

Posted by mpyne under Uncategorized | No Comments »