Academic freedom for all

The cover story in the latest issue of C&EN is about threats to academic tenure. As someone who spent six years on the tenure track and saw the possibility of tenure snatched away from my colleagues, I have thoughts.

When discussing tenure, non-academics tend to think that tenure means you've got a job forever. Critics of tenure often point to a hypothetical "lazy" tenured professor taking up university resources without putting in "enough" effort, or (all too real) examples of universities finding it difficult to fire abusive tenured professors. These arguments against tenure are specious, though. Tenure does not prevent a university from firing someone for cause – so when they retain an abuser or let them quietly find another place seek prey, know that they are being cowardly, not fulfilling some legal obligation. Besides that, I have a spouse working in the corporate world, and trust me that he has encountered incompetent and abusive people who have kept their jobs for years despite a lack of tenure. Offering tenure does not mean keeping incompetence, and getting rid of tenure does not mean only competent people will persist.

Proponents of tenure point to the importance of academic freedom: the freedom to pursue lines of study (in research and also in teaching) that may be controversial without threat of losing your job. Those areas of study could be anything. As Andrew Dressler says in the C&EN piece, “You don’t know what’s going to be politicized until it does get politicized."

What boards and administrators want (but may not admit to) is the ability to fire people when they feel like it. Worried about decreasing enrollment? Fire faculty from your least favorite programs and tell them it's for the good of the institution. Feel threatened by the existence of transgender people? Fire anyone who puts pronouns in their email signature. Think a Black professor is "difficult" and just doesn't "fit"? Get rid of that professor. These things already happen, but they're easier to do to the untenured.

I am glad tenure exists, but I don't think it is a very good tool for the problems it tries to solve. I agree with tenure supporters that academic freedom is important. I think it's so important, that its protection shouldn't be reserved for those who make it through a six-year obstacle course. A first-year, part-time instructor should be just as protected when teaching controversial topics as a distinguished professor with decades of full-time experience. But right now, they're not.

Tenure is an individual solution to collective problems. I suppose it's very American in that way. The individual professor jumps through hoops attempting to please all and sundry, incentivized to overextend themselves, compete with colleagues, and exploit their trainees. If you think I exaggerate, know that I was advised by my very first dean not to meet expectations for tenure but exceed them, meaning of course that the implicit expectations were somewhere higher than the explicit ones, and how much higher was impossible to know. A couple years later a faculty member on the committee that made tenure recommendations warned junior faculty that since we were part of a hiring boom, the board may not want to grant tenure to everyone. The implied advice was to be even more excellent than the other tenure candidates to have a shot at one of a limited number of seats. (Seats that, when the time came, the board yanked anyway.) And after years of doing more more more, isn't it understandable that some people would want to slow down or stop? How dare they be "lazy."

Once a professor achieves tenure they have its protection, but on the track to tenure they will have been advised not to ruffle too many feathers among the established lest they lose out on necessary recommendations. For those who spend years playing it safe, how many suddenly feel empowered to take the risks academic freedom protects?

If I dream of an alternative, it looks like this: faculty supporting each other instead of competing for scarce seats in the tenure club; faculty of all levels of experience equally empowered to take risks and protected from termination or political interference when they pursue controversial areas of study; and equitable expectations for faculty labor.

A model for this alternative exists, and it's called a union.

Unions aren't perfect. They're still made of people, and people are complicated. Unions are difficult to form at private universities thanks to case law like the Yeshiva decision. Membership among faculty groups (part-time, full-time non-tenure track, tenure-track, tenured, librarians, and other folks with teaching duties and other titles and/or responsibilities) varies widely. But when a union works well it comes with solidarity, job protections backed by federal law, and contracts that set firm boundaries so the work cannot just grow grow grow.

When I came to Utica I took a non-tenure track position. Giving up pursuit of tenure took some getting used to, but as I said that summer and have said many times since: I'd rather have a union than tenure. I'd rather have solidarity, job protections, and a clear contract from day one than spend more years exhausting myself chasing the possibility of security.

If that sounds good to you, maybe you can have that too.

Happy Labor Day

Hire me

I love working at Lyman Briggs, but the job I have is a temporary one. I’m only here for a year. The academic job market has a particular annual cycle, and right now it’s application time for tenure-track positions. This means that though I will be happily teaching chemistry at Briggs from now until May (and possibly into the summer), I have to look for next fall’s job now.

I don’t like applying for stuff. I don’t like selling myself. I worry that nobody will want me, that nobody likes what I do, that I’m not good enough, experienced enough, polished enough to get the job I want. I worry that I’ll be passed over because of my gender, my opinions, my beliefs, my appearance or my personality. I worry that the search for the next job will be a hindrance to the job I am currently doing.

But.

When I can drive the poison of Impostor Syndrome from my addled brain, I remember that I’m actually a competent, qualified instructor with a passion for teaching. I’m an expert in my field, with the publications and fancy diploma to prove it. I am capable and talented and enthusiastic. I have a deep desire to ask and answer scientific questions. I have the potential not just to succeed, but to thrive.

So if you’re at a liberal arts college or regional university and you have an open position in chemistry to fill for next fall, I hope you’ll consider me when my application crosses your desk.

Swift

I got an iPod Touch in 20091 and wished from the start that I could write my own apps for it.2 I knew approximately nothing about coding, though, so it was a rather far-away sort of wish.

In grad school I learned to code in Matlab. It was a sink-or-swim kind of thing. With the help of another grad student, two books, the wonders of Matlab Central (and later StackExchange), and lots of practice, I learned how to write and debug programs.

My brother is a programmer, and by his standards I'm a hobbyist at best, but I can make the computer do what I need, and I've gotten better as I've gone. Still, he teases me about how I should learn a "real" language, and I kind of agree. So about a year ago, after listening to a Mac Power Users episode about learning to code, I bought a book about learning Objective-C.3 I got a little better than halfway through it before other things got in the way; it's one of the things I was planning to come back to this summer between grad school and job.4

Those summer plans may have just changed, though. A week or two ago at the WWDC Keynote, Apple announced a new programming language called Swift and I think I'm in love. I watched the demo and thought "I can definitely do this." I may finally be able to write the apps I wished for. There's an eBook about the language, which I've already started reading. Though it starts from "Hello world," I don't think it would be much help if you had no familiarity with programming whatsoever,5 but it does look promising for someone (like me) who has at least dipped their toes into the programming pool before.

So that's my next side project: learn another language, try to make an app (I have several ideas), and see how it goes. I'm excited to get started.


1: Nearly 5 years later, it's a bit sluggish but still kicking.

2: I was also bowled over by the idea that the device playing podcasts in my pocket had a bigger hard drive than my laptop's original drive: 64 vs 60 GB. When I stop to think about it, it still amazes me how powerful the gadgets in my pockets and bags are. And then I start feeling old…

3: It's a really good book, too: The Big Nerd Ranch Guide. My inability to finish it has much more to do with being an overwhelmed graduate student in need of "off" time for my brain than the quality of the book. I highly recommend it, and I think it's an excellent example of instructional writing.

4: Oh yeah, I accepted a job about the same time I was completely overloaded with dissertation and defense stuff. The defense is done, the dissertation is submitted, and though I wrote about the stresses and thrills of job-hunting, I guess never did mention here that I did accept an offer. More on that another time. Short version: I have a job starting in August and I'm excited about it!

5: This is actually the same gripe I have about the Matlab Getting Started Guide and books for "beginners." All of these say that you can start from scratch, but they usually assume knowledge and vocabulary that a first-time programmer may not have. (I'm looking at you, floating-point array.)

Consider these programming languages like human languages: the Getting Started Guide might tell me how a verb is conjugated, but if I don't know what "conjugation" is, I don't know what to do with that information. If you've learned another language before, you've probably learned the meta-terminology already, and have some kind of structure for understanding this new set of words, sounds, and grammar rules.

About that STEM shortage

About that STEM shortage

A week or so ago, somebody on Twitter shared this post at the US Census Bureau blog on employment in STEM fields. It includes a chart showing the trends in the fields as a fraction of total STEM employment. It doesn't tell you about would-be STEM workers who are unemployed, nor does it tell you about unfilled positions in these areas. Still, I think you can get a rough idea of the relative demand for workers in each field. If there are many people currently employed in a field, it implies a large demand for that field. Said another way, if there weren't demand for that work, why would those people still have jobs?

I was not surprised to see that T and E are bigger slices of the STEM pie. What did surprise me was how much bigger they are. So here, for your viewing pleasure, is a little graphic. The colored bars are proportional to each field's contribution to total STEM employment in 2011.

Read More