work
Time to start studying
I have set upon a new endeavor at work: I am applying to become a DER. A brief explanation is in order, since probably none of my readers are familiar with the avionics industry and how equipment is approved to go on airplanes.
In the USA, the Federal Aviation Administration (FAA) has to approve every piece of equipment that goes on an airplane. The idea is that they can ensure that all aircraft are, by design, safe and airworthy. For software that runs on equipment in the aircraft, that software must be developed with rigorous standards and procedures, and then verified with equal rigor. (The relative rigor of the standards depends also on how critical the equipment is - less critical equipment needs less rigorous procedure and test.) Just for my company (one of the top two or three avionics suppliers in the world), and just in my department (flight displays), we probably request certification for half a dozen software releases every year.
The FAA realizes that they don’t have enough people to review every package in detail, nor do they have the time to stay current on all the new technologies and designs and processes. So, they choose to appoint engineers within the avionics companies as “designated engineering representatives” (DERs), and they give those engineers the authority to review and sign off on software releases on behalf of the FAA.
So, I’m applying to become a software DER. There are only about a dozen of them in our company (out of 10,000+ employees), and half of those dozen reach retirement age in the next 5 years. So, the need is great. I’m kind of at the bottom end of the experience required; counting my college training, I have 10 years of software experience - a minimum of 8 are required. I submitted my application packet yesterday. I will be going to a national DER conference in Norfolk, VA at the end of July, which should provide me with some valuable training. Then I will be studying the federal regulations like mad in preparation for a 30 minute panel examination by the FAA, likely to be scheduled for the end of September.
It will be a good move to become a DER; first of all, it’ll provide some variety in my work since I’ll be doing the DER stuff about 20% of the time, and my usual job the other 80%. It’ll give me visibility to other projects and other types of equipment that I might not learn about otherwise. It’ll make me just a little bit more indispensable, I suppose… and indispensable is a good thing to be.
I imagine I will post about my learning experiences here from time to time, so stay tuned.
here goes nothin'
Yesterday afternoon my manager walked in and asked me if I’d like to become a software lead for an upcoming project. It’s a move up, of sorts, though probably without a pay increase.
For the past 6 years, I’ve been just a software engineer, which means that I just get assignments to do software changes, and I do them. It’s been a fine job, I’ve learned a lot. As software lead, I would basically be responsible for making sure all of the software changes get done for the project, making sure they are done correctly, solving any of the difficult technical problems, setting up the development environment, creating the releaseable software… wait, I guess that’s stuff I’ve been doing at least a bit of in my current position. I guess my last few years have served me well. :-)
The one thing I am not looking forward to is moving from a Windows-based development environment to a VAX-based environment. Not that I’m scared of moving away from GUI to command-line - heck, I prefer command-line; but I hate having to learn a whole new tool set. Oh well, it’s the one development environment I haven’t worked with yet in 6 years, so it will broaden my knowledge. Or something like that.
It’s a little scary moving up to this position, but not too bad. I had originally been told that I was going to be the project engineer, which would entail a lot more document-writing and paperwork. That was much scarier. This will just be a good move up the chain. I think I’m starting to look forward to it…
network downtime...
This morning we are experiencing one of those fun office moments known as “network downtime”. Nobody can get logged in and even if you can (I managed somehow), nothing works; all of the network drives are dead. Fortunately, Internet access still works, so I can post a little blog like this one.
It’s interesting listening to the buzz around here; people are talking where normally there is only silence and people working. I doubt anybody’s gotten anything done all morning, so right now I’m going on 2+ hours of downtime. Take that times 4000 people or so at RC and at the billing rate that engineers cost, and we’re up to almost $1Million in general time while we’re all waiting for the network.
I should really find something more interesting to blog about; I’ve seen some people with long, thoughtful posts; however, I guess I don’t find the time for long, thoughtful writing. I mean, I can when I need to or want to, but I guess I spend so much time of each day just getting work and normal stuff done that I don’t take a lot of time to just sit and think and write. It’s really too bad; I do have actual thoughts about stuff on a semi-regular basis.