Learning is awesome

My favorite part of just living is how much I learn.

Here are some pieces of advice you might find useful, some cool skills I’ve acquired (maybe you’ll be inspired), and a couple other things, too:

Because lists are awesome, too…

• A GPS is only helpful in localizing large vehicles, particularly when you’re trying to use the GPS to direct navigation. When your vehicle is smaller than the error margin of plus or minus two meters (e.g., an RC car), it doesn’t work so well! (This from last summer, at NASA Langley.)
• Pens with lights attached are a fantastic invention. I got a combo flashlight-pen at GHC last year. It writes. It lights up. This pen lives next to the pad of sticky notes by my bed. Now all my middle-of-the-night ideas are legible!
• If you’re working on a big important project, always work on it, every day. Could be a thesis. Could be a novel, or a software project. Even on the days when you really don’t want to work on it and you’re entirely unmotivated, work on it anyway. Do a tiny little bit, then do a tiny little bit more, and maybe you’ll convince yourself that you are in the mood to work on it after all. If not, at least you did a little bit, right?
• Just how cool people think NASA is. Specifically, how cool people think it is when they find out I interned there, twice. I continue to be surprised. Quite seriously. Are my standards for what counts as super awesome too high? Do I just expect everyone else to be similarly awesome, making my accomplishments average on the scale of awesomeness? Maybe I do … everyone has the capacity for brilliance. Maybe not everyone fulfills that capacity, but I think you’re suppose to take this as your cue to go be brilliant.
• I earned my Amateur Radio Technician’s license. I am now qualified to talk on the HAM radio bands! I know more than I used to about electronics, antennae, and radio frequencies. I’m still working on learning Morse Code.
• Philosophy of mind. I know a decent amount on the subject from my cognitive science background, but there’s always more to learn! A friend and I have delved into some fun readings: Aristotle’s conception of matter and form, Aquinas on the immateriality of mind, Lawrence Shapiro on embodiment and reductionism, and many more. I’m re-reading Shapiro’s The Mind Incarnate, which I initially read in my second cognitive science class ever, some three and a half years ago.
• How to successfully relocate to a new city in a new state. Yeah, I did that. It involved a lot of talking to people, a lot of driving, and a lot of paperwork and standing in lines.
• Just how flexible my sleep schedule can be. I used to be a stickler for getting my full eight hours every single night of the week. I realized over the summer that I can function just fine on a weird schedule of eight hours, then three hours, then seven hours, then maybe five, followed by nine or ten hours to catch up… I’ll write more on this sometime. Carol Worthman wrote a particularly relevant chapter on sleep for Evolutionary Medicine and Health that I plan to outline for you.
• The rudiments of tae kwon do. According to the instructors at the Goddard Tae Kwon Do club, I have a decent roundhouse kick. I’d like to learn more — I’m still very much the beginner white belt.

And a whole slew of technology-related items:

• - Octave, essentially an open-source Matlab.
• - R, a statistical computing language and environment.
• - The rudiments of time series analysis.
• - ROS, an open-source platform for robotics work
• - Mobile Robotics Programming Toolkit (MRPT) libraries, also open-source and also for robotics work.
• - PCL, the point cloud library, useful for feature detection in point clouds.
• - Simultaneous localization and mapping (SLAM) algorithms, as well as other common mapping and path planning algorithms.
• - How to use subversion.
• - Random little things about Ubuntu, including the “alt-f9″ shortcut to minimize the current window
• - How to use the Tobii T60 eye tracker.
• - And so much more …

I wonder if I can double this list by this time next year..?

A comprehensive Cognitive Science and Computer Science internship resource list

As my undergrad years draw to a close, I’ve compiled a list of internships and related opportunities for students in Cognitive Science and Computer Science. Most programs are also open to students in other engineering and technology fields and are not limited to undergraduate students!

Take a look! Pass along the page to anyone you know who may find it useful. Although deadlines for some summer 2011 programs have passed, many have March or April deadlines, and many of the semester or year-round programs have later deadlines.

One more about the Grace Hopper conference! This one’s a critical look at presentations, since I attended a bunch of panels and some speakers were better than others.

The right way

One of the keynote speakers, Duy-Loan T. Le, was a brilliant orator. She held the audience captive. She had no powerpoint, no slides, nothing but a microphone. Her speech reminded me that far too often, presentations of one’s work or ideas are focused on the text and images lit up on the screen. The right way to do it: focus on you, explaining and selling your work. A display is great for diagrams and supporting pictures. It’s a bonus for clarifying points. But that’s all it should be: support. Not the focus.

The wrong way: what not to do & how to fix it

The general approach to presentations these days assumes that the focus is on the slides, not the person talking. Personally, I watch the speaker. I’ll glance over at the screen now and then. If I can’t understand the talk because I’m not reading along on the slides, there’s a serious problem.

1. Never, ever read sentences directly off the slides. If you do, it means you have too much text on your slides. You can read directly from your notes. Your notes should not be posted on your slides.
2. Talk slower than you think you should. Everyone in the audience appreciates an intelligible speaker.
3. Make clean slides, both in terms of amount of content on any one slide and the content’s format. This topic could fill a book; I’ve touched on it before. Use a font large enough for people to read from the back row. Use easy-to-read colors. Don’t cram text and graphics into every empty space. If you’re just going to gloss over a topic, you don’t need paragraphs about it on your slides – particularly when you flip through your slides more quickly than people can read your paragraphs. What’s the point of having so many words if no one is going to read them?
4. Don’t have paragraphs on your slides, period. If I want the novel, I’ll email you for it, thanks. A presentation involves you and it involves you, presenting. I once sat through a presentation in which the speaker used a gimmick of little cartoon fishies with whom she “conversed” and who “helped explain” her topic. The fishies even made noise – yup, she found a garbled, irritating bubbling audio track. Multiple times, she told the audience, “I’ll let my fish friends explain,” and proceeded to stand quietly on the side of the stage as the audio track played. We, as the audience, were expected to sit there reading the slides.
5. Proof-read your slides. At GHC, I saw the phrase “If you don’t, know one else will.”
6. Unless you specifically know your audience will be full of programmers, don’t put huge chunks of Java pseudocode in your slides. Even if you’re giving a talk for an audience that is mostly technical women, your presentation needs to understandable by the non-programmers, at least on a general level. Similarly, if you’re going to include technical details, don’t gloss over them using unexplained technical terminology to “give the flavor,” because all the audience learns is that they don’t know the jargon.
7. Insist on a mobile microphone and/or a laser pointer. Sometimes you don’t have a choice, such as at GHC this year. Tied to a specific location on the stage, you’re unable to gesture at your slides or point to them except in a vague, flailing manner, and unable to be heard unless you’re rigidly standing in one spot. A laser pointer and and a mobile mic add flexibility and allow you to more easily incorporate your slides into your talk.

I collected a lot of good advice from the women at the Grace Hopper Celebration of Women in Computing, which I recently attended. I shared what they had to say about undergrads looking ahead to grad school.

This is Part II: applicable to everyone! A lot of it comes from the Imposter Plenary Panel. Those women had good things to say!

1. One of the women on the Imposter Plenary Panel, Fran Berman, emphasized confidence. When you get the opportunity to sit at a table with the most important people in your company or in your field, is sitting there a right, or a privilege? “You’ll do best in that room if you think you have a right to be there,” said Fran. She said it’s a tightrope between who you believe yourself to be and who you want to be in that situation.
2. Yolanda Rankin, another of the women on the Imposter Plenary Panel, said the crux of managing situations is managing relationships with people.
3. Diane Gonzelez, another of the imposter panelists, explained her “Don’t ask, don’t get” policy. You have to tell people what you want, she said. If you want a promotion, your manager may pass you up until s/he knows you’re looking for a promotion. This doesn’t just apply to the job market, either. Diane shared a quote from Althea Gibson: “No matter what accomplishments you make, somebody helped you.”
4. Fran Berman agreed with Diane Gonzalez: “there is no recognition fairy” who’ll come along and give you an award. You must advocate for yourself and your career.
5. From the “How do I become a Researcher?” session: You have more control in academia than you do in industry. In general, anyway, because in industry, divisions get outsourced, proposals and ideas get turned down, and companies get reorganized. Unless you’re the one in charge, you don’t get as much self-determination.
6. Diane Gonzelez said she has observed a tendency among women: There’s a job with ten requirements. A man may look at it, see he has two of the requirements, and apply, claiming that he can do all ten. A woman may have eight, but think, oh gosh, I’m not qualified, I shouldn’t apply! Her advice: Don’t doubt yourself so much.
7. Fran Berman also talked about mistakes. She said, when you make a mistake, “You have to learn from it and don’t repeat it… right away.”

Words of wisdom were being traded as often as poken high-fours at the Grace Hopper Celebration of Women in Computing, which I recently attended. Academics and professors shared their knowledge of navigating grad school; current grad students explained how not to do what they’re doing; women in industry and government labs elucidated how they got there and why they enjoy their jobs.

These are a few nuggets I found to be particularly applicable. This list focuses on advice for current undergrads or early grad students — I’ll be following up soon with a list of more general advice!

1. One of the women on the Imposter Plenary Panel, Fran Berman, said, “You were not born as an undergrad, and you were not born as an intern.” The skills you used to get to be an undergrad or intern will help you get to the next step, too – whether that’s grad school or your first full-time job.
2. During the “How do I enjoy and succeed in grad school?” session, it was suggested that when investigating grad schools, talk to the students. Ask the students about advisors. How often do you meet? What’s it like working with them, writing with them, and writing for them?
3. From the “How do I become a Researcher?” session: If you apply to grad school without knowing exactly what your focus will be, when you write your application essay, pick one thing you’re interested in and write about that.. Even if that’s not the only thing that interests you. You can change your mind later. The admissions folks are looking passion, interest, and focus.
4. Both the “How do I become a Researcher?” session and the “How do I enjoy and succeed in grad school?” session mentioned the following: When contacting potential grad schools, be conscious of professors’ time. Professors are very busy people. Schedule meetings well in advance when visiting their schools. Show you’ve done your research: read their papers and ask questions about their work. You’re not just finding out if these professors want you in their labs – you’re finding out if you want to be in their labs! Oh, and if you send your resume to a professor, send it plain text, not as an attachment.
5. Erika Shehan Poole, during the “How do I enjoy and succeed in grad school?” session, suggested that students keep a research journal. Any ideas you have, good or bad – write them down. Questions you have. Later on, when you’re planning your thesis (or any other time you need ideas), you can look back. Maybe there’s a theme. Maybe some of those idea – even if they sounded dumb at the time – are actually good. Maybe they’ll spark new ideas.
6. Duy-Loan T. Le, Thursday’s keynote speaker, told all the students in the audience, “If you want to be the top of your class, don’t fall in love.” This speaks, I think, to the notion that time is finite. You cannot put all your time and energy into your coursework if you also want to put some time and energy into your relationships with the people you care about. As I’ve oft been told, it’s a matter of balance.

1. Don’t fall in 2Gs. One of my labmates got to ride the vomit comet because of a science project he worked on, and not falling was one of the recommendations while aboard the plane. The rationale was this: If you fall, you’ll fall too fast. You’ll try to bring your arms up to catch yourself–it usually works, but here, your reflexes will be too slow. Your face will hit the ground and your nose will smash as your arms are still moving up to catch you.
2. Astronauts have to be a certain kind of person. My mentor, Garry D. Qualls, told me about a colleague of his who became an astronaut. Evidently, they take a certain type of person. Gregarious, outgoing. Dedicated. The kind of person who, upon receiving a task, will be content doing that task day in and day out to the very best of his/her ability–astronauts have to practice the tasks they’ll be doing in space for a long time beforehand. The kind of person who can speak reasonably well to large groups and who enjoys meeting all kinds of people, since a huge part of the job is public relations.
3. Always double-check baud rates, port numbers, and IP addresses. Save before recompiling, have a common ground, make sure to use charged batteries, and give your program the right input arguments if it requires them. Installing the referenced libraries usually helps, too.
4. Stick with your federal/government job for at least three years. At the grad seminar, held in June with the goal of providing student interns with information about post-baccalaureate options, one of the speakers commented offhand that if you do become a fed, if you stick with it long enough, you’ll get reinstatement rights. I did a little googling to see what kind of rights those are: Evidently, it means you can reenter the fed workforce without competing for the job with the general public. It doesn’t mean you automatically get a job offer. There are obviously some restrictions, but regardless, good to know! That page also mentions that if you don’t work a government job for three years, you get reinstatement rights for only three years after you leave.
5. Ask about details when investigating grad schools. The grad seminar included a panel of three students (graduate or just finished) who each spoke a bit about how they had gotten to their current place in life. One of the students offered advice on good questions to ask the professors at schools you’re considering: If you’d get to do research, what would the specifics be? Not just the topic, but how much time would be spent sitting in front of a computer? reading papers? attending conferences?

I’ll continue sharing stories about what I’ve learned this summer, so be sure to check back soon!

It’s raining.

Fat, corpulent water globules cascade from the sky. Plop, plop. A drop, and a few of its compatriots, dribble down the inside of your collar. They’re cold. Wet, and unpleasant. The drops slither down your neck.

“Take my cloak,” he [Lord Golden] suggested.

“It would only get as wet as the rest of me. I’ll change into dry things when I get back.” [Fitz]

He didn’t tell me to be careful, but it was in his look. I nodded to it, steeled myself, and walked out into the pouring rain. It was every bit as cold and unpleasant as I expected it to be. I stood, eyes squinted and shoulders hunched to it, peering out through the gray downpour. Then I took a breath and resolutely changed my expectations. As Black Rolf had once shown me, much discomfort was based on human expectations. As a man, I expected to be warm and dry when I chose to be. Animals did not harbor any such beliefs. So it was raining. That part of me that was wolf could accept that. Rain meant being cold and wet. Once I acknowledged that and stopped comparing it to what I wished it to be, the conditions were far more tolerable. I set out.

— Fool’s Errand, Robin Hobb

Keep it in perspective

Keep what in perspective? Well, everything, but particularly the bad things, the frustrating things, and the irritating things. So it’s raining. So you cut your finger slicing potatoes. So it’s ninety-nine degrees Fahrenheit and humid. You are in some set of circumstances and you wish to be in some other set of circumstances. You wish to be dry. You wish your finger didn’t hurt. You wish to be cool and comfortable without drops of sweat sliding down your neck.

Unfortunately, we don’t live in a world where wishes change the world’s physical properties. We have limited control over our environments. We have slightly more control over our reactions to our environments.

“Since we cannot change reality, let us change the eyes that see reality.” —Nikos Kazantzakis

What you expect significantly influences how you will perceive your circumstances. The thing is, a lot of times, we don’t explicitly set out our expectations. You leave the air-conditioned building with the continued implicit expectation that you’ll be cool and comfortable, and when that blast of muggy, sticky air hits you, it hits you twice as hard because you’re expecting something else.

What can you do about this? Try explicitly setting up your expectations. It may help prevent the disappointment of being wrong (and feeling unpleasant). Instead of thinking “Aaugh, I’m getting wet and the rain is cold, why can’t I be warm and dry?” try thinking “Okay, I’m going out in the rain so I’ll be wet and cold. That’s just how rain is.” Keep in mind that this works both ways–sure, you can set yourself up to expect to feel better about your circumstances, but you can also easily set yourself up to expect to feel worse.

As a final note, I’m sharing to a quote I occasionally turn to as a reminder to keep things in perspective, from Nick Hornby’s High Fidelity (on the subject of pop music):

“Did I listen to music because I was miserable? Or was I miserable because I listened to music?”

Are you miserable because of your circumstances, or are your circumstances miserable because of your misery?