Archive for the ‘Advice’ Category

Unsolicited Advice X: How to Frame a Winning Proposal

by Julianne

Pretty much every successful proposal starts with a variant of the following structure:

1. Topic X is important and interesting.

2. But.

3. This is how we will address “But.”

The rest of the proposal reiterates those three points with enough detail to make it believable.

In a short proposal, the structure fills a paragraph. In a long proposal, it’s three paragraphs, and shouldn’t go past the first page.

The abstract is a 1 paragraph version of the same structure, with the addition of a closing rah rah rah sentence.

If you can’t bludgeon your introduction into this form, you might want to step back and regroup.

submit to reddit

November 2nd, 2009 2:09 PM Tags:
in Advice | 26 Comments | RSS feed | Trackback >

An Inside Look at the Physics GRE

by John

I am just back from Princeton where we held the annual meeting of the GRE Physics Committee of Examiners, a group of six, ahem, distinguished professors (we have grey hair) who sit around a conference table working through hundreds of potential and actual Physics GRE problem. Each year new exam forms are completed, new questions added to the pool, statistics reviewed, and a good time is generally had by all.

This was my last meeting – I have served on the committee for six years. The membership rotates roughly every two years. I had been an external reviewer and problem writer for a couple years, and was then asked to serve on the committee. I am sworn to secrecy about a lot of the details, for good reason, but let me try to tell you from my perspective as an exam writer how to study for this dreaded event in your physics education.

Firstly, there’s the format. The exam is 100 questions long, and you have 170 minutes to do it. This is, therefore, different from just about every other physics exam you have had in college, where you have, say, four to six problems in an hour-long exam. The GRE Physics problems (or “items” in assessment world jargon) are short, to-the-point questions, and just about all of them are short calculations, if any, and take little time once you see what to do. Writing such questions is a difficult thing to do, let me tell you. We are continually amazed how, after about six levels of review, we can find issues of clarity, reasoning, and even sometimes basic physics correctness in the items submitted to the pool. All the committee members spend a lot of time each year reviewing hundreds of problems, looking for flaws, but more often than you would think the face-to-face meeting in Princeton with the ETS folks reveals something previously overlooked. It’s a really interesting process.
(more…)

submit to reddit

October 22nd, 2009 10:01 AM
in Academia, Advice, Science | 64 Comments | RSS feed | Trackback >

Playing From a Different Tee: How Not to Write a Recommendation Letter

by Julianne

As Mark recently mentioned, we are deep in recommendation letter season. I’ve been in the biz long enough that I’ve probably written at least a hundred letters (estimating more than ten a year for more than a decade), and read far more than that.

After you read enough letters, they can start blend together. But, in a big stack of applications, there are usually a few letters that stand out as risible, causing a good chuckle and round of comment from the committee.

And they are almost always letters written on behalf of women.

In a standard letter of recommendation at the postdoc/faculty level, there is frequently a comparison to other successful scientists. The letter usually reads something like “reminds me of person X, Y, or Z at a similar level of their career” or “shows the same persistence and insight as person Q, and stronger big picture thinking than person P”. These comparisons are almost always favorable, saying that the applicant is in the same league as other people who are recognized as having had a significant scientific impact.

But, for some reason, some fraction of letter writers insist upon doing these comparisons only within a single gender, when the applicant is a woman. In other words, “(woman) X shows a similar level of insight as (woman) Y and (woman) Z”. I’m not saying that these comparisons are not favorable — they’re usually comparing a strong female applicant favorably with other successful female scientists. Their praise is genuine and well meant. However, one can’t but help perceive that they see women as somehow swimming in a different pool than the rest of the guys.

Now the good news is that most committees that I’ve been on have seen right through this. We note it, and have a small laugh at the letter writer’s expense. In addition, it’s not common — usually only affecting a couple of letters in an applicant pool.

So, if you’re writing a letter for someone in an underrepresented group, please save yourself from mockery by examining exactly how you perceive the applicant’s comparison sample.

submit to reddit

October 21st, 2009 6:06 AM Tags:
in Academia, Advice, Women in Science | 18 Comments | RSS feed | Trackback >

Happy 4th of July, Muppet Style

by Julianne

This is transcendently ridiculous.

For the many international CV readers, today is the US’s Independence Day celebration, which is in large part an excuse to bar-b-que meat products, blow up fireworks, and drink beer. If you’re tuning in from abroad, you are probable sober enough to read Daniel’s upcoming post on gravitational waves. For the rest of the drunken US crew, you can probably handle the Muppets.

PS. While we’re talking beer, I must recommend the current Full Sail Limited Edition L.T.D. (Recipe No. 3), sold in bottles with the pale blue label. Seriously. Try some.

(h/t: Again with the CakeWrecks)

submit to reddit

July 4th, 2009 12:58 PM Tags: ,
in Advice, Entertainment, Food and Drink, Humor | 10 Comments | RSS feed | Trackback >

The C Variant

by John

Not to be a harbinger of doom, but this one sounds bad. There are some 6-15 million computers out there running Windows which are infected with a computer virus, dubbed Conficker C. The recent report by SRI makes for some chilling reading. On April 1 (that is, next Wednesday!) the virus is set to…well…do something. It’s not clear what, but with so many millions of computers will do it. The report concludes:

We present an analysis of Conficker Variant C, which emerged on the Internet at roughly 6 p.m. (PST) on 4 March 2009. This variant incorporates significant new functionality, including a new domain generation algorithm and a new peer-to-peer file sharing service. Absent from our discussion has been any reference to the well-known attack propagation vectors (RCP buffer overflow, USB, and NetBios Scans) that have allowed C’s predecessors to saturate so much of the Internet. Although not present in C, these attack propagation services are but one peer upload away from any C infected host, and may appear at any time. C is, in fact, a robust and secure distribution utility for distributing malicious content and binaries to millions of computers across the Internet. This utility incorporates a potent arsenal of methods to defend itself from security products, updates, and diagnosis tools. It further demonstrates the rapid development pace at which Conficker’s authors are maintaining their current foothold on a large number of Internet-connected hosts. Further, if organized into a coordinated offensive weapon, this multimillion-node botnet poses a serious and dire threat to the Internet.

Yikes! Whoever wrote this thing is not a very nice person…or persons. The C variant apparently managed to upgrade itself over the network, and disables security anti-virus software. If I were you (and I am apparently not because I use only OS X and Unix) I would update my antivirus software every day and scan my machine. And leave it off next Wednesday if possible.

Pass the word…

submit to reddit

March 25th, 2009 5:28 PM
in Advice, Computing, Miscellany | 28 Comments | RSS feed | Trackback >

Mathematics Reading List for High School Students

by Mark

Via Slashdot, I came across the following question

Troy writes:

“I’m a high school math teacher who is trying to assemble an extra-credit reading list. I want to give my students (ages 16-18) the opportunity/motivation to learn about stimulating mathematical ideas that fall outside of the curriculum I’m bound to teach. I already do this somewhat with special lessons given throughout the year, but I would like my students to explore a particular concept in depth. I am looking for books that are well-written, engaging, and accessible to someone who doesn’t have a lot of college-level mathematical training. I already have a handful of books on my list, but I want my students to be able to choose from a variety of topics. Many thanks for all suggestions!”

There are some good suggestions in the comments, and some not so good ones. Surely our wise and mathematically sophisticated readers will be able to help. Add what you can there, and in the comments here if you like.

submit to reddit

February 8th, 2009 7:58 PM
in Advice, Mathematics | 76 Comments | RSS feed | Trackback >

A Recommendation Letter Word Cloud

by Julianne

Given the current DEFCON 1 level of anxiety about recommendation letters, and my belief that more transparency is usually a good thing, I thought it would be informative to assemble a word cloud of about 10 years of recommendation letters written for undergraduates applying to graduate schools or fellowships (with names and schools omitted).

rec_word_cloud.png

As you can see, the top three themes are “research”, “project”, and “work” indicating that the letters are highly weighted towards what students have actually accomplished, rather than just pure intellectual firepower. The cloud for graduate students applying to postdoctoral positions would be more biased towards words like “thesis” and “papers”, but would again emphasize what one has done, not how intelligent one is.

So, if you are a student thinking about graduate school, you should make sure you get involved in research, and, when you do, make sure you get something done!

submit to reddit

January 20th, 2009 4:52 PM
in Academia, Advice, Words | 26 Comments | RSS feed | Trackback >

Things the Grad Admissions Committee Does Not Wish to See

by Julianne

Here are some of the things from various admissions files that have made me sad (details changed to preserve anonymity)

“I’m sure Stu Dent could do well in graduate school, provided you can get him to talk to you more than I ever could.”

• Transcripts with three times the number of courses (and substantially better grades) in music than in physics.

• Deep, Meaningful quotes from rock bands and dead hip-hop artists in the footer of the applicant’s cover letter.

“No other institution would benefit more from my presence than yours.”

“I only want to work on Topic X! Nothing is cooler than Topic X! My intellectual life is a shrine to Topic X.” Except, our department has no relevant work on Topic X.

“Stu Dent has excellent physical intuition and will undoubtedly succeed in graduate school”. Except, Stu has mostly B’s and C’s in their physics courses and a 15th percentile on the physics GRE.

• Students who have taken no math beyond calculus.

submit to reddit

January 16th, 2009 11:36 AM
in Academia, Advice | 108 Comments | RSS feed | Trackback >

Unsolicited Advice, Part Nine: Choosing a Postdoc

by Sean

Early January, and time for another entry in our unsolicited advice series — this one on choosing a postdoc. For non-academics, a “postdoc” is that lovely several-year period in between getting a Ph.D. and (hopefully) landing a faculty job, during which one establishes some independence and concentrates on doing research to the exclusion of all the other delicious aspects of professordom. And for reasons that have never been fully explained, a lot of postdoc jobs are offered and accepted in December/January/February, even if they don’t start until September. So now is the time to make yet another one of those choices that will dramatically affect the entire rest of your life.

Here, we’re not telling you how to get a postdoc; we’re presuming you already have more than one offer in hand, and need to choose between them. (Yay you!) At some point we should write about applying for postdocs, but that season is largely passed. Note that postdoc situations vary wildly from field to field, and my experience is largely in theoretical physics; there is more advice at Dr. Isis’s place, and I’m sure elsewhere — as usual, leave links in the comments. Free advice on the internet is worth what you pay for it, but if you get a variety of different perspectives a nugget of wisdom might sneak through.

To decide which postdoc position is right for you, it makes sense to think about what your goals are in being a postdoc in the first place. Generally they look something like this:

1) Do some good science.

2) Learn new things and grow as a scientist.

3) Put yourself in a good position to land a faculty job.

The very good news is that these goals are not in conflict! You can do good science while learning new things, and you can do both of those while positioning yourself to apply for faculty jobs. Indeed, you’ll be in much better position (obviously) if you have done some good science. However, it’s possible to do some good science and nevertheless end up in not such a good position.

Before we unpack that, we should say a word about other considerations. You might care about geographic location, or proximity to a loved one, or easy access to jazz or martinis or gambling or whatever your favorite vice may be. (Personally, I can’t decide.) I’m all about the other considerations, and would never tell you to discount them. Life is short, and the years you spend as a postdoc are just as truly years of your life as any other years. However … if you were thinking that it would be worthwhile, at some point in your life, to sacrifice on your other considerations for a bit in order to concentrate on doing the best science you can — now is the time! Of all the hurdles and bottlenecks along an academic career path, the jump from postdoc to faculty is probably the hardest, just in terms of raw probabilities. (There are a lot fewer faculty jobs than there are postdocs looking for them.) At the same time, the transition from the comforting embrace of graduate school, where (at least in principle) you have an advisor looking over you, to the naked Hobbesian individualism of being a postdoc, where your personal initiative counts for everything, can benefit from a certain amount of increased focus. I know, “comforting embrace” isn’t the first phrase that comes to mind when you think of graduate school. But there is more structure there, and a sense of belonging to something bigger. (Often, as a postdoc, the department won’t even list you in any sort of directory.) So, while there’s nothing wrong with taking other considerations seriously, this temporary phase of your academic trajectory is arguably the best time to put those on the back burner while you concentrate on your job, hoping that sacrifice will pay off later. How much you balance those competing considerations is up to you.

(The extent to which personal initiative counts varies wildly from academic field to field; in a big lab, the role of a postdoc may be little different from that of an advanced grad student. For theorists, the role of a postdoc is little different from that of a beginning professor — you are expected to come up with your own ideas and carry them to fruition.)

With all that throat-clearing out of the way, let’s tackle those above goals. First, you want to choose a postdoc position that will help you do good science. This criterion is actually relatively straightforward, but there are some subtleties. Of course it will help if you go to a place that is chock full of good scientists doing the kind of science you would like to be doing yourself. But you still have to ask some of the same kind of questions you asked when choosing a grad school — at the most basic level, would you yourself be able to productively work with these people? Do you like them, are they supportive? What do the other postdocs who are currently there — or even better, were there recently and have moved on — think about the experience?

Here is an excellent little diagnostic. Of the different places you are considering, have a look at some of the papers they have written over the last three years. Now ask yourself: which of those papers would I have been most pleased to be a co-author on? That’s a direct way of separating vague feelings that “this place is good” from “they are doing what I want to do.” But then, to kick it up a notch, look again at those papers, and in particular at the author lists. Are there any postdocs there? Is this the kind of place where the postdocs collaborate frequently and directly with the faculty and each other, or are they more on their own, or have they still collaborating with their old groups from grad school? Different departments have different personalities, but the evidence of how postdocs generally fit in should be easy to gather.

Next, you want to learn and grow as a scientist. This one is a bit trickier. You definitely do want to grow — it’s unlikely that, as a grad student, you did enough different kinds of work that you would be happy to stay confined within those disciplinary boundaries for the rest of your life. Your postdoc years are a great chance to define yourself (see below), so you should think long and hard about how you want to be defined. On the other hand, it is possible to grow too much. If your degree is in string theory, and your first postdoc is in molecular biology, and your second postdoc is in inorganic chemistry, you’re sort of just being incoherent. You’ll have fun along the way — and if that’s your goal, that’s great — but if you are planning on moving to the next level, you want to be broad without losing coherence entirely. You want to challenge yourself with new things, but you want to challenge yourself productively. You certainly don’t want to think of your postdoc as another round of grad school, where you start from scratch. You are now a professional scientist with some established expertise, and you would like to build on that expertise.

But at the same time — and here’s the crucially important part — you don’t want to just repeat yourself. That’s why everyone always tells you to go somewhere else for your postdoc, not to stick around the same place you were a grad student. It sounds like good, solid advice, but when the moment of decision comes, far too many people choose to play it safe, and either stay where they are (if that option is available) or move over to some group with whom they were already collaborating. It’s hard to appreciate until you’ve been around the block a few times, but different departments are truly different in their approach to doing science. One of the absolute best features of the postdoc system (and there are a lot of crappy features) is that you get an invaluable opportunity to be exposed to the idiosyncrasies and habits of mind of a completely different set of senior researchers. That can be a truly eye-opening experience, and you should try as hard as you can to take advantage. Find people with whom you can work and be productive (you want to write papers, not just take classes or sit at the feet of masters), but who will challenge your preconceptions and open your eyes to new ways of thinking about your field.

Finally we have the money goal: you’d like to put yourself in good position to land a faculty job. (That’s what we’re assuming, anyway; if not, standard disclaimers apply.) Of course this is as much art as science, and there’s a tremendous amount of noise in the system — but you control what you can.

With that in mind, recall that our advice for being a good grad student was to “Be the kind of grad student that people would like to hire as a postdoc.” Guess what? As a postdoc, you will strive to be the kind of postdoc that people would like to hire as an assistant professor. And what kind is that? If you’re honest with yourself, you can probably hit upon the right answer by contemplating the kind of applicant you would be most likely to hire, if you were already a faculty member sitting on a hiring committee. The basic rule is that you’re not going to get hired as a faculty member by being talented and smart; you’re going to be hired because the department sees that you are doing awesome things. When people hire postdocs, the applicants are still charmingly unformed as mature scientists, and their letters of recommendation will often weigh more than their lists of publications. But when it comes to hiring a faculty member, it’s rarely done purely on promise — they want to see that you’ve done something.

So when you’re choosing which postdoc to take, choose the one that maximizes your chances of actually doing something. Writing papers, and (more importantly) writing good papers. And (most importantly) by “good” we do not mean “technically competent.” We mean interesting, even to people outside your immediate circle of friends. Papers you would want to read, even if you hadn’t written them. Those are the kinds of papers you want to be writing as a grad student.

The need to write interesting papers should be obvious, but sometimes it gets lost in the excitement. Writing papers as a grad student can be like having sex as a teenager — you’re amazed that it’s happening at all, and not so concerned with excelling. But at some point, as you mature, it becomes important to do it well. It is deadly, as a postdoc, to fall into the trap of writing papers just because you can write them. Like it or not, there are many people like you competing for a scarce resource in the form of faculty jobs. You have to distinguish yourself. If you are working within any field where there is a nontrivial chance of getting hired as a faculty member, there will certainly be other people writing papers in the same field. What is it that will make your papers better?

And it’s not only good papers — it’s papers that define who you are. That’s a question you will literally be asked when you are applying for faculty jobs — what are you really? What do you do? And the appropriate answer has to be well-defined (like it or not) in terms that are comprehensible to a faculty hiring committee. “I work on models of dark energy” is a bit narrow; “I am a theoretical physicist” is a bit broad; “I work on field theory and particle physics applied to cosmology” is about right. (You can always, and in fact should, continue to broaden your scope all throughout your career.) But you can’t just proclaim it; your list of publications has to proclaim it for you. You won’t want to work on the same thing over and over again, but you do want the work you do to tell a coherent story. Each paper is a dot on a map of possible problems one could be thinking about, and you want your set of dots to form a sensible picture. A postdoc period is a good time to fill in what you might think of as gaps in your toolbox, if you will excuse a terribly mixed metaphor. Become the scientist you would want to hire.

Figure all that out, and then choose the postdoc position that will maximize your chance of writing the papers that make it happen. Easier said than done, I know. If it were easy, it wouldn’t be any fun, would it?

submit to reddit

January 8th, 2009 1:12 PM
in Academia, Advice | 20 Comments | RSS feed | Trackback >

A Box Full of Awesome

by Julianne

Many older scientists and engineers grew up tinkering. Car engines were pulled, belts on washing machines were replaced, loose wires on toasters were soldered. Such experiences build a basic competence with the physical world, and develop an innate understanding that the devices around us are not powered by magic. For better or worse, however, gadgets have become both more electronic and more disposable, leaving few useful opportunities for fixing things. Moreover, many of us grew up in non-tinkering households, and even if we’d been raised during the glory days of Large Mechanical Devices Made of Steel, we wouldn’t have wound up tinkering ourselves. And finally, much of that tinkering was pretty clearly marked as a Guy Thing.

But, there is a possible cure. I give to you Snap Circuits.

This has to be one of the funnest, most accessible geeky kid’s toys ever. It completely takes away the overhead of electronics assembly, allowing even very little kids to assemble circuits well before you’d trust them with a soldering iron. All the pieces are color-coded in bright primary colors with the standard circuit notation imprinted on top. The projects are largely fun — things like driving a little motor that turns a fan blade, which, if you mount it upside down, eventually generates enough lift that it shoots off and sails up the ceiling. There’s no chance of exploding capacitors or burnt fingers (which I’m sure for some of you makes it completely un-fun, but we’re talking 5 year olds here). Instead, what kids get is fast understanding of how circuits work, at a level that they can understand and really enjoy.

On top of just being extremely cool, for some reason Snap Circuits seems to have way more cross-gender appeal than the old Heathkits. It somehow cracked the code of not seeming like a gender-coded toy. There are no pictures of kids on the package (male, white, or otherwise), and it’s brightly colored without being frilly. There is also no assumption of past apprenticeship, where one was supposed to have learned soldering and breadboard wiring from some older family member. As such, I know as many girls as boys who are enamored with Snap Circuits (and although I probably don’t hang with the most representative sample of kids ever, the Snap Circuits flickr pool seems to bear my impression out).

So, if you have a kid in your life and don’t mind being stigmatized as the adult who gives nerd presents, consider Snap Circuits.

submit to reddit

December 31st, 2008 1:55 AM Tags:
in Advice, Gadgets, Science and Society, Technology | 19 Comments | RSS feed | Trackback >