Work projects
Mar. 5th, 2003 12:26 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
dmazeBack in December, I had two big things I was going to work on in January. The first one took me longer than I thought, but I finished it, and did the prep work for the second. So now I'm at the point where I can actually start working on it -- and my boss tells me that I shouldn't, because he hasn't reviewed my design or given me any input at all, even though he knows this has been something on my to-do list for essentially the past three months.
Meanwhile, our larger project has been on a release schedule (such as it is) where we'll think about releasing "at the end of next term" for the past two years or so. The other half of our group has a chip project, and they have actual chips, and they're giving them to people, and our software I think is one of the better ways to use their chips, and we've apparently promised them that we'll have a software release. So we're doing a preliminary release. By next week. And I'm the person in the group closest to a release engineer. Joy.
Compiler infrastructure == fun. Trying to package it up and give it away == not fun.
Meanwhile, our larger project has been on a release schedule (such as it is) where we'll think about releasing "at the end of next term" for the past two years or so. The other half of our group has a chip project, and they have actual chips, and they're giving them to people, and our software I think is one of the better ways to use their chips, and we've apparently promised them that we'll have a software release. So we're doing a preliminary release. By next week. And I'm the person in the group closest to a release engineer. Joy.
Compiler infrastructure == fun. Trying to package it up and give it away == not fun.
