Well, I'm on vacation, and the doomed project is out of my hands. It's a mess in general, but let's hope that's not my fault too much, and if it is let's hope no one notices.
Friday, August 26, 2011
Wednesday, August 24, 2011
Earthquake
So, the earthquake. That was fun.
Conveniently, we had had a fire drill recently, so even the new people knew where to go. In fact, it was so recently that it was probably a mixed blessing. I might have brought more stuff with me when I left the building, and therefore been better prepared for it, if not for the fact that I had just been primed for a brief interruption.
But anyways, at around 1:50 yesterday afternoon, the office shook. At first we thought it was just unusually hard renovation on another floor or something, but obviously not, so the place evacuated. Due to a quirk of fate yesterday, my housekeys and metro card were in my messenger bag rather than my pocket like usual, and I didn't take that with me when I left for the quake. Oops. It was at least 15 minutes and probably more like 30 before they announced that the building was closed for the day, to make sure there was no hidden structural damage. They were letting people back in in relatively small groups by floor to get stuff, and it's just my luck - my floor was second-to-last. So I was stuck outside for over an hour in my trousers, button-down shirt and black leather shoes. (To be clear, I have been in the habit of changing into shorts, a t-shirt and sneakers to bike home as part of my commute. Standing outside in DC on a summer afternoon in formal attire, or even just business casual, is really not fun.)
But after I finally got back into the building, I changed shoes, picked up my stuff and walked off. Changed into shorts and t-shirt at nearby supermarket bathroom. Traffic looked like a nightmare. I've probably never been more glad I don't use a car. As annoying as my situation was, my girlfriend had it worse. I joined her and four of her co-workers at a restaurant near her office. She works on Capitol Hill, and people weren't allowed back into her office until around 6:30 or later. By that time we had already had drinks (well, those of us whose drivers' licenses weren't stuck inside our offices... which was me and just one more person. ouch), water and appetizers, and had given up on waiting and went our separate ways for the day. So she had to borrow my metro pass while I biked home last night and to work this morning.
Doesn't seem like DC handled things well. Like I said, traffic was horrible, worse than rush hour right after the quake, although by the time the usual rush hour came along it was better. In fairness, though, this is not something people expect. I don't know the geological science, but until 1:50 p.m. yesterday I would have said the East Coast doesn't get earthquakes at all. When things shake here in DC in particular, people think "terrorism" before "earthquake". And "safety first" is probably one of those things that government is much better about than either individuals or private corporations. (Sure, there are screw-ups, famous failures that make the news, etc., but speaking generally.) Everyone knows individuals are irrational all the time, and corporations don't like getting sued but they don't like employees not being productive either. Government bureaucracies, though, aren't going to send people back to their desks until they're really, really sure the building hasn't taken structural damage. Indeed, half a dozen government buildings weren't open today, although my building itself wasn't one of them.
As for a personal impact, it made the deadline on the doomed project even harder. I know that's a short-sighted way of thinking about something like this, but as long as we're talking about my view of things, well, there it is. The quake resulted in about three hours less work this week, so I'll just have to work a bit harder to make up for it. Never mind that losing three hours close to a deadline, and particularly close to my part of it, could really throw things off.
Conveniently, we had had a fire drill recently, so even the new people knew where to go. In fact, it was so recently that it was probably a mixed blessing. I might have brought more stuff with me when I left the building, and therefore been better prepared for it, if not for the fact that I had just been primed for a brief interruption.
But anyways, at around 1:50 yesterday afternoon, the office shook. At first we thought it was just unusually hard renovation on another floor or something, but obviously not, so the place evacuated. Due to a quirk of fate yesterday, my housekeys and metro card were in my messenger bag rather than my pocket like usual, and I didn't take that with me when I left for the quake. Oops. It was at least 15 minutes and probably more like 30 before they announced that the building was closed for the day, to make sure there was no hidden structural damage. They were letting people back in in relatively small groups by floor to get stuff, and it's just my luck - my floor was second-to-last. So I was stuck outside for over an hour in my trousers, button-down shirt and black leather shoes. (To be clear, I have been in the habit of changing into shorts, a t-shirt and sneakers to bike home as part of my commute. Standing outside in DC on a summer afternoon in formal attire, or even just business casual, is really not fun.)
But after I finally got back into the building, I changed shoes, picked up my stuff and walked off. Changed into shorts and t-shirt at nearby supermarket bathroom. Traffic looked like a nightmare. I've probably never been more glad I don't use a car. As annoying as my situation was, my girlfriend had it worse. I joined her and four of her co-workers at a restaurant near her office. She works on Capitol Hill, and people weren't allowed back into her office until around 6:30 or later. By that time we had already had drinks (well, those of us whose drivers' licenses weren't stuck inside our offices... which was me and just one more person. ouch), water and appetizers, and had given up on waiting and went our separate ways for the day. So she had to borrow my metro pass while I biked home last night and to work this morning.
Doesn't seem like DC handled things well. Like I said, traffic was horrible, worse than rush hour right after the quake, although by the time the usual rush hour came along it was better. In fairness, though, this is not something people expect. I don't know the geological science, but until 1:50 p.m. yesterday I would have said the East Coast doesn't get earthquakes at all. When things shake here in DC in particular, people think "terrorism" before "earthquake". And "safety first" is probably one of those things that government is much better about than either individuals or private corporations. (Sure, there are screw-ups, famous failures that make the news, etc., but speaking generally.) Everyone knows individuals are irrational all the time, and corporations don't like getting sued but they don't like employees not being productive either. Government bureaucracies, though, aren't going to send people back to their desks until they're really, really sure the building hasn't taken structural damage. Indeed, half a dozen government buildings weren't open today, although my building itself wasn't one of them.
As for a personal impact, it made the deadline on the doomed project even harder. I know that's a short-sighted way of thinking about something like this, but as long as we're talking about my view of things, well, there it is. The quake resulted in about three hours less work this week, so I'll just have to work a bit harder to make up for it. Never mind that losing three hours close to a deadline, and particularly close to my part of it, could really throw things off.
Friday, August 19, 2011
The busy part
Yesterday was productive and yet still bad.
Like I said, I shouldn't have got too optimistic about making that one deadline on the doomed project, because however annoying the previous phase was, it wasn't really my problem. Last week some time I was given an assignment, compiling a list of certain things in the document, as part of the current phase. I said I'd get started on it, but didn't; I got distracted by easy-and-quick-but-less-important minutiae on this project, I got distracted by another project, etc. Tuesday H. asked for a status update on several things, including the list. Mentally, I said "oh shit, I probably should have started that", and in my e-mail reply I said I could "have it done by tomorrow". As it turns out, that estimate was off, I finished a list about two hours after I got to work yesterday, but I'd say I was close enough and no one complained. Of course, a list is just the first step; after that I or someone has to fix numerous problems I found while compiling the list, and find a document corresponding to each item on the list.
But my supervisor and I agree that I should be working on the more immediate deadline, the amendatory instructions and getting the document itself closer to being a publishable rule, than on the list. So we persuaded H. of that. The backup tech writer, who's doing part of this, had already got it set up on Wednesday. Before I could get started on it, though, I had to catch up on other stuff for the doomed project. Changes suggested by e-mail that were too vague or I had to run by someone else or I just hadn't got around to them, etc. A number of e-mails were required there and some instructions were more complicated than others. It was all necessary and productive, but based on e-mail timestamps it kept me busy until 2:26 p.m. yesterday. After that I was able to work on the amendatory instructions for about an hour, when they asked me to do something as a result of a meeting that had happened without me, and that took a while to figure out.
Put it all together and I had only about three hours to work uninterrupted on the part I was actually supposed to be working on. And that's at the end of the day, after my eyes are tired of staring at a computer screen and my brain is so tired of ambiguously-phrased instructions that I've stopped using pronouns. All told I'd say I got about half as much done on the amendatory instructions as I should have if we want to make the "official" deadline for this phase. So today I'd have to work half again as hard as the schedule calls for just to get back on track. And today has also had a few changes introduced late, and e-mail requests to respond to, and of course it's a quiet Friday and I'm writing all this, do you think I'm getting caught up?
Like I said, I shouldn't have got too optimistic about making that one deadline on the doomed project, because however annoying the previous phase was, it wasn't really my problem. Last week some time I was given an assignment, compiling a list of certain things in the document, as part of the current phase. I said I'd get started on it, but didn't; I got distracted by easy-and-quick-but-less-important minutiae on this project, I got distracted by another project, etc. Tuesday H. asked for a status update on several things, including the list. Mentally, I said "oh shit, I probably should have started that", and in my e-mail reply I said I could "have it done by tomorrow". As it turns out, that estimate was off, I finished a list about two hours after I got to work yesterday, but I'd say I was close enough and no one complained. Of course, a list is just the first step; after that I or someone has to fix numerous problems I found while compiling the list, and find a document corresponding to each item on the list.
But my supervisor and I agree that I should be working on the more immediate deadline, the amendatory instructions and getting the document itself closer to being a publishable rule, than on the list. So we persuaded H. of that. The backup tech writer, who's doing part of this, had already got it set up on Wednesday. Before I could get started on it, though, I had to catch up on other stuff for the doomed project. Changes suggested by e-mail that were too vague or I had to run by someone else or I just hadn't got around to them, etc. A number of e-mails were required there and some instructions were more complicated than others. It was all necessary and productive, but based on e-mail timestamps it kept me busy until 2:26 p.m. yesterday. After that I was able to work on the amendatory instructions for about an hour, when they asked me to do something as a result of a meeting that had happened without me, and that took a while to figure out.
Put it all together and I had only about three hours to work uninterrupted on the part I was actually supposed to be working on. And that's at the end of the day, after my eyes are tired of staring at a computer screen and my brain is so tired of ambiguously-phrased instructions that I've stopped using pronouns. All told I'd say I got about half as much done on the amendatory instructions as I should have if we want to make the "official" deadline for this phase. So today I'd have to work half again as hard as the schedule calls for just to get back on track. And today has also had a few changes introduced late, and e-mail requests to respond to, and of course it's a quiet Friday and I'm writing all this, do you think I'm getting caught up?
Wednesday, August 17, 2011
What was I thinking?
What was I thinking, getting so enthusiastic about meeting that stage's deadline? I really should have known better. Partly just out of broad cynicism about this project, my job, and life in general. But I also should have known better because the next stage of the project is no better for me. I mean, what we were doing was still part of the "informal review", which means that it was annoying and tough to keep track of, particularly with version control issues, but in the end, for me, nine times out of 10 there were simple instructions and it was just a matter of doing them.
I should have remembered that the part of the project after that is my actual job, editing the document, and I would now need to get started on it. On a document that is very messy because of how we've been doing things, plus all the other problems with the doomed project. The next week and a half will not be fun, and after that period I'm going on vacation, and coming back from vacation will really, really not be fun.
I should have remembered that the part of the project after that is my actual job, editing the document, and I would now need to get started on it. On a document that is very messy because of how we've been doing things, plus all the other problems with the doomed project. The next week and a half will not be fun, and after that period I'm going on vacation, and coming back from vacation will really, really not be fun.
Monday, August 15, 2011
The meetings will continue until morale improves
There was a meeting this morning at 11 a.m., with 10 minutes of the usual office-management and achievement-recognition announcements, followed by literally an hour of discussion of workplace satisfaction surveys we took a few months ago. I've come to the conclusion that my department's head is a nice guy, and well-meaning - not a ladder-climbing schemer, not a petty feudal fiefdom type - but just plain kind of dumb. Part of the issue was feedback on harassment and discrimination issues. 9 out of 49 people, 18 percent, reported something. Now, I seem to remember that the survey questions were badly designed, but that's not the point of this post. The well meaning but dumb (WMBD) boss mentioned in passing that roughly 20 percent of people reporting discrimination problems was considered the target or something like that, according to the polling organization, but he said that even the current level of reported problems was unacceptable. He also seemed to be genuinely confused about the fact that he had personally heard of fewer problems than the survey indicated.
As for pursuing perfection, I think he misunderstood the meaning of the 20 percent figure. I very much doubt that the surveying organization is saying that that amount of discrimination is good, just that that's the amount beyond which improvement is impractical, unfeasible, more trouble than it's worth, the consequence of people being imperfect. So, sure, it's inspiring pablum to say "I'm never going to tolerate intolerance" or "We can always do better", but I'd actually be reassured if someone who says that kind of thing doesn't mean it. And as for whether he would have heard about problems before the survey, I may as well admit that I'm a straight white male so I have little or no personal experience with being on the receiving end of discrimination, but I find it easy to imagine reasons why a person might not want to deal with discrimination through official channels. The big, obvious, easy one is if the discrimination is less trouble than dealing with it would be. One sexist joke from one guy in one meeting, or even one regularly sexist guy you work with occasionally, would probably not be as much stress and frustration and trouble as reporting the guy and going through an adjudication process and worrying about how it looks in the long run. And the zero tolerance policy espoused in reaction to the first point actually seems counterproductive here. I'd have to really hate my harasser indeed, and/or really, really trust the WMBD guy, if every slightest allegation was going to result in a full investigation and all that. But WMBD apparently never thought of that, or if he did, apparently came up with no way to deal with the problem.
Other than that, though, most measures of workplace satisfaction were good. Less for contractors like me, of course, and WMBD went out of his way to say that we're all a team, a family, etc., and fair enough, I'm sure he means it, but there's only so much you can do when you're way down the totem pole.
That being said, there was one ironic thing about it. Guess what it was. Here's a hint: notice the timeline. Started at 11, 10 minutes of housekeeping, an hour of workplace satisfaction discussion. That's right, the workplace satisfaction discussion cut into lunchtime for most people. I know that impacted my workplace satisfaction, and not in a good way.
Sure, of course, maybe WMBD knows what's attainable and meant what he said as platitudes, like I'd prefer. Maybe he realizes the issues with reporting harassment and is still working on how to address them, or believes that what he said today helps, and maybe he's even right about that. It's just that (as I've said before), the best thing my supervisors high in the department can do for me is stop acting in ways that come across as stupid, and this morning's meeting was yet another example of that.
As for pursuing perfection, I think he misunderstood the meaning of the 20 percent figure. I very much doubt that the surveying organization is saying that that amount of discrimination is good, just that that's the amount beyond which improvement is impractical, unfeasible, more trouble than it's worth, the consequence of people being imperfect. So, sure, it's inspiring pablum to say "I'm never going to tolerate intolerance" or "We can always do better", but I'd actually be reassured if someone who says that kind of thing doesn't mean it. And as for whether he would have heard about problems before the survey, I may as well admit that I'm a straight white male so I have little or no personal experience with being on the receiving end of discrimination, but I find it easy to imagine reasons why a person might not want to deal with discrimination through official channels. The big, obvious, easy one is if the discrimination is less trouble than dealing with it would be. One sexist joke from one guy in one meeting, or even one regularly sexist guy you work with occasionally, would probably not be as much stress and frustration and trouble as reporting the guy and going through an adjudication process and worrying about how it looks in the long run. And the zero tolerance policy espoused in reaction to the first point actually seems counterproductive here. I'd have to really hate my harasser indeed, and/or really, really trust the WMBD guy, if every slightest allegation was going to result in a full investigation and all that. But WMBD apparently never thought of that, or if he did, apparently came up with no way to deal with the problem.
Other than that, though, most measures of workplace satisfaction were good. Less for contractors like me, of course, and WMBD went out of his way to say that we're all a team, a family, etc., and fair enough, I'm sure he means it, but there's only so much you can do when you're way down the totem pole.
That being said, there was one ironic thing about it. Guess what it was. Here's a hint: notice the timeline. Started at 11, 10 minutes of housekeeping, an hour of workplace satisfaction discussion. That's right, the workplace satisfaction discussion cut into lunchtime for most people. I know that impacted my workplace satisfaction, and not in a good way.
Sure, of course, maybe WMBD knows what's attainable and meant what he said as platitudes, like I'd prefer. Maybe he realizes the issues with reporting harassment and is still working on how to address them, or believes that what he said today helps, and maybe he's even right about that. It's just that (as I've said before), the best thing my supervisors high in the department can do for me is stop acting in ways that come across as stupid, and this morning's meeting was yet another example of that.
Friday, August 12, 2011
It's a first
Well, we made the deadline on that stage of the doomed project, barring four isolated issues. On one, I went to a presentation yesterday about how ridiculously complicated the issue is, and the team member responsible for the issue has said he can "take [his] lumps" for not having it resolved yet, so that seems fair enough to me. Two more are legal issues and I'm pretty sure that the legal department is allowed however much time they need for things like this. Finally there's one more issue that was assigned to me, but when I tried to solve it I found I needed help from someone who wasn't around at the time.
Technically it's my fault and responsibility, but you know, I'll take the blame for that ONE problem if it means I can spread a little of it onto him, probably the most unhelpful team member. That's partly just general frustration with the project, since the last part of the assignment before the deadline was mostly mine. And it's probably unfair to rate his helpfulness or lack thereof against a few people who have had less total involvement with the project, but to the extent that they were involved they seemed even more useless than the unhelpful guy.
But now that I've got fairness out of the way, getting useful contributions out of the unhelpful guy has been like pulling my own teeth. He's frequently absent from the office on short notice. Taking vacations during summer is understandable, of course, but this week he took two days off, and he didn't let the team know about it until just half an hour in advance, and even that was only because of a reminder that went out to the team that people still had things to resolve. And that's another thing: he breezily offers to take care of lots and lots of stuff, and doesn't. I wound up talking to him on his cell phone while he was in the airport on the deadline day. There are a lot more things he had taken care of in some sense, or thought he had, but it wasn't taken care of in any way that matters. Which brings up yet another problem: this guy is the biggest cause of version control problems, and was unashamed of it as far as I can tell. I mean, sure, in the grand scheme of things, screwing up version control is a minor problem, but one guy apologized for it and it wasn't the unhelpful guy even though he did it much more.
Well, we're over with that phase of things. Now for the next part, which should be easier. For me. For a little while. Probably.
Technically it's my fault and responsibility, but you know, I'll take the blame for that ONE problem if it means I can spread a little of it onto him, probably the most unhelpful team member. That's partly just general frustration with the project, since the last part of the assignment before the deadline was mostly mine. And it's probably unfair to rate his helpfulness or lack thereof against a few people who have had less total involvement with the project, but to the extent that they were involved they seemed even more useless than the unhelpful guy.
But now that I've got fairness out of the way, getting useful contributions out of the unhelpful guy has been like pulling my own teeth. He's frequently absent from the office on short notice. Taking vacations during summer is understandable, of course, but this week he took two days off, and he didn't let the team know about it until just half an hour in advance, and even that was only because of a reminder that went out to the team that people still had things to resolve. And that's another thing: he breezily offers to take care of lots and lots of stuff, and doesn't. I wound up talking to him on his cell phone while he was in the airport on the deadline day. There are a lot more things he had taken care of in some sense, or thought he had, but it wasn't taken care of in any way that matters. Which brings up yet another problem: this guy is the biggest cause of version control problems, and was unashamed of it as far as I can tell. I mean, sure, in the grand scheme of things, screwing up version control is a minor problem, but one guy apologized for it and it wasn't the unhelpful guy even though he did it much more.
Well, we're over with that phase of things. Now for the next part, which should be easier. For me. For a little while. Probably.
Tuesday, August 9, 2011
God of punctuation
My job sometimes has a weird blend of the incredibly momentous and the most trivial minutiae.
For example, the doomed project makes frequent reference to something which I'll call "XYZ" here. Last week I was told that this is the first reference ever in regulation, or at least this agency's kind of regulations, to XYZ. I guess that's just because it's a relatively new thing, I don't know. But it's important where it appears, and it appears on big and valuable and dangerous things. If we don't handle it just right, that could cost people lots and lots of money and cause environmental damage and maybe loss of life. That's not certain, or we would be taking XYZ even more seriously than we are, but it definitely seems possible. And, as I've said, parts of the approval process for the doomed project are going to be expedited to help with the "deadline", so XYZ will be covered sooner than it would otherwise.
So how am I handling it? Well, first of all, I'm annoyed that we're doing anything with it at all. As I've said, the doomed project should be a narrow, limited thing to have any chance at all of meeting the deadline. To my non-expert eyes, XYZ, while it might be important, looks like the kind of thing that's outside the "correct" scope of the project. So it bugs me that it's in the rulemaking at all instead of having one all to itself.
But that's just my general attitude to this and many other things about this project. What have I personally, recently been doing about it? Answer: trying to figure out when and if variations on the acronym are acceptable. That is, can we use phrases like "XY computers" or "XY sensors" or "XY facility"? The answer from the team was no; we should say "XYZ" where appropriate, and if that really doesn't make sense, we should spell out the first two words. Variations are not acceptable, I was told. But I have googled some uses of it and apparently the industry actually does use them. At the moment I'd taking refuge in the exact words of what the team agreed upon and I was told to do, but if this project wasn't on such a short deadline I'd probably try to figure out when and if and how we should be using variations.
So: this is a ground-breaking problem with wide implications for industry and the public, fast-tracked to gain the full force of law as soon as possible, but I personally doubt we should even be doing anything about here at all. My role in it is making sure that an acronym is used consistently, and I have doubts about that too.
For example, the doomed project makes frequent reference to something which I'll call "XYZ" here. Last week I was told that this is the first reference ever in regulation, or at least this agency's kind of regulations, to XYZ. I guess that's just because it's a relatively new thing, I don't know. But it's important where it appears, and it appears on big and valuable and dangerous things. If we don't handle it just right, that could cost people lots and lots of money and cause environmental damage and maybe loss of life. That's not certain, or we would be taking XYZ even more seriously than we are, but it definitely seems possible. And, as I've said, parts of the approval process for the doomed project are going to be expedited to help with the "deadline", so XYZ will be covered sooner than it would otherwise.
So how am I handling it? Well, first of all, I'm annoyed that we're doing anything with it at all. As I've said, the doomed project should be a narrow, limited thing to have any chance at all of meeting the deadline. To my non-expert eyes, XYZ, while it might be important, looks like the kind of thing that's outside the "correct" scope of the project. So it bugs me that it's in the rulemaking at all instead of having one all to itself.
But that's just my general attitude to this and many other things about this project. What have I personally, recently been doing about it? Answer: trying to figure out when and if variations on the acronym are acceptable. That is, can we use phrases like "XY computers" or "XY sensors" or "XY facility"? The answer from the team was no; we should say "XYZ" where appropriate, and if that really doesn't make sense, we should spell out the first two words. Variations are not acceptable, I was told. But I have googled some uses of it and apparently the industry actually does use them. At the moment I'd taking refuge in the exact words of what the team agreed upon and I was told to do, but if this project wasn't on such a short deadline I'd probably try to figure out when and if and how we should be using variations.
So: this is a ground-breaking problem with wide implications for industry and the public, fast-tracked to gain the full force of law as soon as possible, but I personally doubt we should even be doing anything about here at all. My role in it is making sure that an acronym is used consistently, and I have doubts about that too.
Thursday, August 4, 2011
What's a deadline?
Apparently, deadlines now matter around here. Who knew?
The current phase of work on the doomed project has been harried and busy for the past few days, because suddenly, we have a deadline that we really, really can't miss. I'm not sure why. Either our bosses just got tired of putting it off, or someone further up changed their minds about their priorities, or there's just an unwritten rule that being five months behind schedule is fine but behind six months behind is beyond the pale and really, really heinous. (And, remember, that schedule was highly optimistic from the start. And calling it "highly optimistic" is the diplomatic phrasing; more accurate descriptions include "crazy" and "a joke". The original schedule was based on compressing three years of work, much of which is out of our control, into one. The point is, we are and have always been working relatively fast given reasonable expectations.)
We actually are getting through this part faster than most, both because of general pressure on us and because we're getting more support. (Which is a polite way to say that people are actually showing up for meetings.) I still doubt we'll be completely finished by the alleged deadline of tomorrow, though. Partly because the only remaining points are sticky things that people have to recheck or run by third parties, but also partly because people aren't around. At least two key team members have been unavailable for most if not all this week because of vacations, and I myself am taking a four-day weekend. So one thing on my agenda today is getting another tech writer to help me with this.
The current phase of work on the doomed project has been harried and busy for the past few days, because suddenly, we have a deadline that we really, really can't miss. I'm not sure why. Either our bosses just got tired of putting it off, or someone further up changed their minds about their priorities, or there's just an unwritten rule that being five months behind schedule is fine but behind six months behind is beyond the pale and really, really heinous. (And, remember, that schedule was highly optimistic from the start. And calling it "highly optimistic" is the diplomatic phrasing; more accurate descriptions include "crazy" and "a joke". The original schedule was based on compressing three years of work, much of which is out of our control, into one. The point is, we are and have always been working relatively fast given reasonable expectations.)
We actually are getting through this part faster than most, both because of general pressure on us and because we're getting more support. (Which is a polite way to say that people are actually showing up for meetings.) I still doubt we'll be completely finished by the alleged deadline of tomorrow, though. Partly because the only remaining points are sticky things that people have to recheck or run by third parties, but also partly because people aren't around. At least two key team members have been unavailable for most if not all this week because of vacations, and I myself am taking a four-day weekend. So one thing on my agenda today is getting another tech writer to help me with this.
Subscribe to:
Posts (Atom)