I write as my maternity leave is drawing to a close. My child will start with a full-time nanny during the first full week of August, so that I have time to prepare for the start of classes in the last week of August. I am writing this while traveling to and from my first professional meeting since the birth of my child – and also the first time I’ve been apart from my child for more than a few hours. Continue reading
Pre-registration for Fall 2018 concluded a week ago. Our enrollments are strong once again, with all courses nearly filling or overfilling.
|CS 167-A,B||Intro. Computational Problem Solving||42/60||1:1||5|
|CS/Math 220||Discrete Math & Functional Programming||34/24||1:2.5|
|CS 267||Human-Computer Interaction||23/20||1:3||25|
|CS 270||Data Structures||19/24||1:3||3|
|CS 310||Computer Systems Programming||18/20||1:5|
|CS 320||Theory of Computation||19/20||**|
|CS/Math 350||Mathematical Modeling & Numerical Methods||0 enrolled as a CS course|
|CS 495||Capstone Project||16/16||1:7|
Long story short: I was pregnant during the fall semester, my daughter Gwendolyn was born in early December, and I am on maternity leave this semester. We’re both doing very well.
I’ve been meaning to write this post since October, which should say something. For those who have been wondering why I haven’t been writing much, this is why.
This is a fairly personal post. Those mainly interested in the development of the CS program should look for a future post on managing my maternity leave and upcoming research leaves. Continue reading
Pre-registration for Spring 2018 concluded on Tuesday night. Our enrollments remain strong, with all sections except the senior capstone project nearly full or overfull:
|CS 167-A,B||Intro. Computational Problem Solving||59/60||1:3||16|
|CS 210||Computer Systems Fundamentals||24/24||1:4||4|
|CS 270||Data Structures||28/24||3:4||4|
|CS 300||ST: Software Engineering||23/24||**||0|
|CS 301 / Math 373||ST: Cryptography||0 enrolled as a CS course|
|CS 320||Theory of Computation||15/20||1:4||0|
|CS 327||Algorithm Design & Analysis||18/20||1:3||0|
|CS 351||Artificial Intelligence||24/16||1:4||4|
|CS 496/7/8||Capstone Project||3/16||1:2|
This post shares some of the diversity of our students’ summer experiences—a very important part of a computer science student’s education. I’ve gathered short reflections from a few students and linked to the blogs of a few more. This first draft represents two summer research experiences (one at Whitman and one at a large research university) and two internships (one closely associated with Whitman and one not). Continue reading
During her visit to Whitman this spring, Terian Koscik (Grinnell ‘12) invited students to participate in Code for Good, “an annual event based out of the Portland area where Python programmers from all over the globe get together for a long weekend to build projects that help our communities.” Three Whitman students ultimately participated, including my summer research student Andrew Harvey ‘20, our new CS 167 mentor Missy Gerlach ‘19, and the very enthusiastic Nathaniel Larson ‘19. The three of them have agreed to contribute to a joint guest post about their experiences. First they will give an overview of the event, and then each will share their biggest highlights and takeaways. Continue reading
This was my second summer of participating in Whitman’s student-faculty summer research program. Below I share my stories of two projects that were quite different in their content and their material circumstances.
Regular readers might remember that I am the newest member of the Liberal Arts Computer Science (LACS) Consortium. (An earlier post responded to the 2016 annual meeting.) As the newest member, I was invited to host this year’s meeting. Some joked with me that this is hazing, but more accurately it’s paying my dues to an organization that truly depends on the contributions of all its members. It is also the host’s privilege to invite guests of her choosing from both her own institution and others. Finally, I’ve also been invited to host other professional meetings at Whitman in years to come. My experience hosting LACS—a small group who I know fairly well—makes me more confident I can do so. Continue reading
This is the first summer in three years that I haven’t had to move offices. Nonetheless, this summer has its own disruptive events that have made planning difficult. Continue reading
David Allen’s Getting Things Done is no small part of what got me through my dissertation, and I’ve been using it ever since. I was introduced to the system and philosophy by the postdoc I shared my office with. (A.J. Brush, who has continued to get things done—if you are reading this, thanks again!)
However, I won’t say I apply it perfectly. I experience breakdowns pretty regularly, which means reflecting on my tools or routines to figure out what to change to make it work again. Continue reading