Skip to main content

The obligation to BCC


Today I got a job-related rejection letter, delivered enmass to 151 candidates. I know it was 151 because the sender hit CC rather than BCC, so all of the recipients know. Furthermore, all of the recipients know who else was competing for the job, can look at their department profiles, and likely their CVs. For private individuals, academics tend to have a lot of Web presence, largely due to university/department websites. To a large extent, that's a good thing, but when combined with a leak like this one, that increased Web presence costs a good bit more privacy. Now, there are 151 candidates who get to take a peek at their competition, maybe stalk them on "the Facebook," maybe judge themselves and each other more harshly for it. At the same time, it is not unusual for departments to announce their new hires, so everyone also knows who got the job, enabling further judgement/comparison/stalking.

Situations like this really highlight how many informational traces we can leave while conducting what we could reasonably think of as our own business (and no one else's). One might think that respecting that sense of privacy would be a kind of professional ethic. Certainly, the system of recommendation letters, transcript deliveries, and application dossiers mean that there are a lot of individuals who may be clued in to the fact that a person is looking for a job. Yet, when it's not our business, we don't fish for more, put the clues together, and seek out further information. To so is considered a little creepy, right?


In general, being on the academic job market provides a window into a variety of university cultures and group norms. Unfortunately, one often learns a great deal about an institution's relationship to technology (or lack thereof). There is something about having your login credentials emailed to you in plaintext that just makes you feel...less than safe, especially considering the kinds of information provided to potential employers. Nevertheless, it's not neglect. I'm sure the folks "responsible" are really not aware of it as a problem.
Labels:

Comments

Post a Comment

Popular posts from this blog

RPG Systems: An Analogy with UI Design

The current game in our weekly role-playing group is Deadlands. The previous game was Shadowrun. Both rule systems lie closer to the “chunky” side of the spectrum. Shadowrun has a particular reputation for its complex and somewhat cumbersome rules, and while Deadlands has less overall complexity, the system has a degree of granularity that interrupts play more often than it enhances narration. I enjoy role-playing games because I like participating in a good story. The rules system provides a set of constraints for the characters, the setting, and the conflicts. They help give the narrative structure, a background against which the story will take place. Too few rules, and telling an interesting and well-developed story becomes difficult. Too many rules tend to get in the way of individual scenes or events. With the right balance, it’s possible for the game master, usually me, to be sufficiently fluent in the rules system to resolve any conflict without extended consultation of on
Post a Comment
Read more

The Incredible Lightness of Collaborative Consumption

Last week, we had to exchange our defective futon frame for a new one. The store didn't want to cover transport cost in either direction, so we had to figure out how to get our re-boxed frame from Mountain View to Los Altos. If we had a car, it would not have been very simple since we were aiming to buy a small sedan, nothing that can easily carry the frame and its box. Fortunately, we have a car sharing service that gives us access to a range of vehicles, including a van stored down the street from my building. After work, I grabbed the van, picked up the frame at our place, and then Tara and I drove to the futon to make the swap. I dropped off Tara and the new frame at our place, and then headed back to campus. On returning the van to its parking space, I hopped on a shuttle back to downtown Mountain View. We were able to do all of this because we're not tied to a specific vehicle for all of our transportation needs. The last car we owned was a van, and it came in handy o
Post a Comment
Read more

Carless in California

For various reasons, we do not own a car despite living deep in American car country. The reasons are largely financial; the cost of living in downtown Mountain View crowds car ownership out of our budget. We pay more to live in a pedestrian friendly neighborhood, so we are less able to afford a car. At the same time, I don't need a car to get to work, and Tara doesn't drive, so any car we had would sit in the carport most of the week. Combine that waste of resources with a reluctance to contribute to the Bay Area's traffic congestion, and forgoing car ownership doesn't sound all that bad. Car sharing services allow us to grab a vehicle as long as we plan ahead a bit. The Caltrain provides access to San Francisco. There are convenience stores and cafes in walking distance, so we don't feel the absence of a car too often. Last night was one of the few times where I did. After getting home from work, we wanted a dinner cheaper than nearby delivery options. The n
Post a Comment
Read more