Skip to main content

Kimberly Blessing

My Nerd Story

8 min read

Rosie the Riveter reminds you that we can do it!These are cute totems. I have the Tesla doll.

A few days ago, I was directed to Crystal Beasley's Nerd Story post by Kirin Kalia, my Bryn Mawr College classmate. She asked me to share my own "nerd" story.

I hesitated. I hesitated because I saw that Crystal was prompted to write her story in response to one of the current sexism-in-tech spotlights. (I'm not trying to downplay whatever is going on currently -- I'm just not following it and can't speak much about it.) I hesitated because I know that my story is laden with the exact kind of privilege that is often attributed to white men in technology. I know that some women don't so much see me as a potential role model as part of the problem.

Still, I considered it. Then I went back to Crystal's post and read the comments that had been left and thought, "I don't need to deal with this shit." Crystal's post had brought out the trolls, haters, and real misogynists. While I've read my fair share of hate mail, I am past the point where I want to deal with online harassment because it wastes *my* time to have to handle it.

After thinking about it some more, I figure that if my story guides or inspires just one other person, or validates something going on in their brain (or heart), then any grief will be worth it. So, here goes.


I grew up in a middle class family that was extremely focused on education. My grandfather was an engineer in the midst of the CAD revolution; my dad and aunt were pharmacists dealing with the computerization of their field. Math, science, and tech geekiness ran in my family.

I started elementary school in 1980 and, from day one, got used to seeing a variety of TRS-80s in the building. Soon, I got used to using them on a regular basis, first through the gifted program, and later through a before and after school program, which I've written about before. BASIC was my first programming language. I wrote programs to make sounds, change the screen color, print text to screen, draw shapes -- all of which culminated in me programming a TRS-80 CoCo 2 to play the harmony to "Yesterday" by The Beatles, while I played the melody on the flute.

TRS-80 CoCo 1My TRS-80 CoCo 1, salvaged in 2008. I don't like getting rid of old tech.

Meanwhile, at home, we had Pong, then an Atari 2600. Playing games was fun, but I wanted to write programs. I got a Commodore 64; in the summer of 1983, after seeing War Games, I spent weeks trying to program my own "Joshua" artificial intelligence. Thankfully, no one ever discouraged me from working on that fruitless program. I don't think they even knew that building an AI wasn't possible. I sure as hell didn't.

The Commodore 64 eventually became a 128 and was a mainstay for everything from gaming to doing homework to getting online. In 1985 or 1986, my aunt purchased an Epson Equity PC (8088) and thus I was introduced to DOS (version 2.11, and all of the upgrades from there!). She was using it for basic word processing; I quickly figured out how to do mail merges for her, create spreadsheets, and other more "office-y" type things with it.

As I made my way into junior high and high school, my interaction with computers was limited to home and the library. Whereas every classroom in my elementary school had a TRS-80 or an Apple IIe, the only computers in the upper schools were in special computer rooms, which were mostly used by the "business prep" students. Honors/gifted students, apparently, didn't need to use computers. At home, with more and more homework to do, my computer use became much more practical -- checking math and typing papers. There wasn't time for programming.

In reality, I didn't make time for programming anymore. It wasn't in the classroom anymore, so I suppose I didn't see it as important anymore. Although I started seventh grade already knowing some trigonometry, I went back to algebra. Yawn. Science was still fun, at least, but my language and music teachers were much more encouraging of my work and progress. I turned my focus to where I got feedback and positive reinforcement. By the time I graduated high school, I had dropped out of calculus but took AP French. I had skipped the one and only programming class at my high school -- but when I saw the homework assignments, I yawned again. They would've been pretty repetitive for me.

Thanks to my grandfather, I started college with a brand-new Packard Bell 486/33, which came with 4 MB RAM, a 120 MB hard drive, a sound card, a 2400 baud modem, and Windows 3.1 -- better than my boyfriend's! In my single dorm room, I had plenty of time to noodle with my new tech. Word 6 and NCSA Mosaic had just been released. I had accounts on AOL, Prodigy, and Compuserve but also quickly learned how to dial in to my college's UNIX server. That computer lasted me one year; I built a new computer the following year and upgraded it consistently, until I got to grad school and bought a fancy Dell machine with a Pentium processor.

At the same time, I was rocking my liberal arts education experience, with my intended romance languages major, until the reality of completing the quantitative (i.e. math) requirement reared its ugly head. I wanted to love calculus, but I struggled. Where to turn? Intro to computer science, of course. I figured it should be easier than suffering through more calculus. I didn't count on it changing my educational direction.

I wasn't a great student, that first CS class. Instead of really trying to learn something new, I relied on my existing knowledge and prior experience to get me through. But I guess it was clear that I "got" it enough to warrant the encouragement of the professor, my friend Deepak Kumar, to continue studying CS. So I did. It was as simple as someone saying, "Hey, you're good at this. Ever thought of majoring in it?"

Me in college with an X-TerminalIn the X-Term lab. I think Sarah and I were writing a program to play Konani.

Being a major in computer science at a women's liberal arts college with only one CS professor wasn't easy. I had to lobby the school to be a CS major, and I had to take classes at other colleges and universities in order to complete my CS requirements. I remember taking computer organization (my favorite subject) at Carnegie Mellon University, and being one of about four women in the hall of perhaps 200 people. It's only strikingly odd to me now; at the time, I knew I was a rarity, but it didn't really faze me. (Later, in grad school, the ratio was a bit better because the classes were smaller.)

I made friends with Sarah Hacker (yes, her real name) who had already decided on a CS major; she worked for campus IT services and helped me get a job. Because I knew UNIX, I made an extra 25 cents an hour! Sarah introduced me to HTML (and helped me fix my first markup bug) and I started cranking out websites on Deepak's server. Other members of the team taught me everything I know about software and hardware support. It was a perfect storm of interest, opportunity, and encouragement. The rest, as they say, is history.

Today, after 20 years of experience in large internet/tech companies (AOL, PayPal, and Comcast) and other organizations, I head up the web development team and growing technology consulting practice at Think Brownstone. I've architected and built some of the coolest publishing systems and web sites in the history of the internet -- and I still get excited when I'm presented with a challenge that requires strategic thinking, technical know-how, and organizational savvy. I've been able to take my experience and turn it into book contributions, conference presentations, and a for-credit CS class at my alma mater. I'm still a technology junkie, but as a manager and leader, I get the biggest kick out of coaching younger talent and helping them grow their skills.


Disney's Kim Possible

The moral of my story is: discouraging a young mind can stop its progress, but encouragement can help get things moving again. If you're an adult, figure out who you can encourage today. If you're a young adult, avoid the discouragers (as much as you can) and find the encouragers.

Write your own Nerd Story -- don't let it be written for you.

Kimberly Blessing

Want to become an expert? Study (web) history

5 min read

Lately I've been spending a lot of time thinking and talking about the past.

I'm at the airport awaiting a flight that will take me to the Line-Mode Browser Hack Days at CERN. CERN, perhaps presently most famous for being the home of the Large Hadron Collider, is also the birthplace of the World Wide Web. More on that in a moment.

Screen shotMy first personal web site, circa 1997

Twenty years ago -- What the hell? Where did the time go? -- I started college. I arrived at Bryn Mawr College a French major, soon to switch to Romance Languages. My Italian professor assigned us reading on a Web page. I was one of the few people in my dorm to have a computer (and modem! and laser printer!). I had email before I got to college, on both AOL and Prodigy. Bryn Mawr had a gopher space, but no web site -- in fact, there were only about 500 web servers up and running at the end of 1993. And yet, that seemingly meaningless introduction changed my life. I took computer science classes. I changed my major to computer science. I started building web sites -- heck, I designed and built the first web page to be hosted at www.brynmawr.edu. For me, that was the start of it all.

And so here we are today. You, reading. Me awaiting my flight to Geneva. To CERN. Holy freaking crap! Understand that, for me, this is akin to visiting Mecca, except I am worshiping ideas, and code, and technology, and the propagation of all those things that has help fuel the evolution of our world into its presently hyper-connected state.

But I must admit that I was surprised, when telling some other web developers about my trip, that they didn't know about CERN's relevance to the web. The popular history of the Internet as an American creation dominates, and it has consumed the WWW creation story for some. So I educate and inform, to set things right, to help those whose careers are based on HTTP and HTML understand their domain's history.

Now, here's where I get preachy, because I run into scenarios like this -- where a web developer will make statements about web-related history that are completely wrong -- frequently. "Oh, IE doesn't support inline-block." Wrong, it has supported inline-block for a long time, but it couldn't just be assigned to any old element. (I've heard this one a lot lately -- perhaps because I'm interviewing and one of the coding problems I give can potentially be solved with inline-block.) "Old browsers don't support the HTML5 doctype," is another popular one. Misunderstanding the origin of CSS3 properties, incorrectly attributing computer accessibility to web accessibility, explaining IE compatibility mode based on one or two simple tests rather than reading the documentation -- even attesting to a lack of JSON support prior to 5 years ago (?!) -- are things I've encountered lately.

I admit that I am quite privileged to have, essentially, grown up with the web. I've been active with it, as a user and a developer, almost as long as it's been around. I do fondly remember using both Lynx and Mosaic to not just surf the web, but also test my own sites. I remember "playing around" with CSS to layer text, and trying to get it to work in both Netscape 4 and IE 3.

But I digress -- this isn't about me. This is about getting other web professionals to better understand our field. To be correct in what they say about the past, when trying to educate others. To not make false statements, based on lack of knowledge or direct experience, which lead to wrong assumptions and misinformed decisions about code and architectures.

I realize I sound like a crotchety old geek, complaining about the young whippersnappers who don't respect their elders. This isn't the case at all. I've had the pleasure of working with many younger people, or just less-experienced people, who have taken the time to learn about the web's history. (Admittedly, some of those people were required to, when they took my course on web app development.) And just knowing facts about history doesn't do much good, without analysis or thought of impact, for today or beyond.

Genuine curiosity and a desire to learn all that one can is ultimately what makes an expert. And, truth be told, any real "expert" will be the first to admit that they're hardly such -- they're still on the quest to become experts, themselves.

So, here I am, about to board my plane, hoping to enrich both my understanding of web history, and yours. Assuming I haven't entirely turned you off, I hope you'll follow my travels on Twitter.

Required Reading

Kimberly Blessing

Why I'm starting a new blog

2 min read

Welcome, and thanks for checking out my new blog!

My old blog, Obi-Wan Kimberly Is Your Only Hope, is still online and won't be going away. The content is all still relevant although the code needs major updating. It's still on my to-do list and it will happen, eventually.

I've been saying for a while that I need to get in the habit of writing more often. I love reading blogs by tech folks that write every day, even when they don't write about technical topics -- Tim Bray writes one of my favorites. If I can make time to read every day, I can make time to write everyday. I know how to form new habits, duh.

I'm starting fresh to free myself of constraints. I'm using a default WordPress theme in order to stop myself from making excuses about design tweaks or code changes. Even though I'm calling the site "People, Process, Technology", I'm going to allow myself to write about whatever's on my mind. (I'll explain why it's called "People, Process, Technology" soon, though!) In short, this site is a blank notebook for me. You're welcome to read through it, at your leisure.

Thanks again for stopping by and I hope to see you again soon.

Kimberly Blessing

Celebrating Ada Lovelace Day 2010

8 min read

My Ada Lovelace Day post is a two-parter: the first part, recognizing two women who inspired me in math and computing; the second, recognizing Milly Koss, an inspirational and accomplished female computer scientist.

Ada Lovelace Day is an international day of blogging to celebrate the achievements of women in technology and science. Learn more

Mrs. Smarkola, Miss Herrick, and the Dawn Patrol

Article about The Dawn Patrol From the Grace Park Mini News, an article about Dawn Patrol by yours truly, circa 1985.

I am so fortunate to have been raised in the 80s, during the emergence of the personal computer. My school, Grace Park Elementary, and my teachers were excited about the TRS-80s and Apple IIes in the classroom, and many kids had Commodore 64s at home. Our teachers saw us get excited about learning; we were having fun playing with new toys our parents never had.

Our librarian, Mrs. Smarkola, was one of my most favorite people at school. When I think of her, I always imagine her with a large book in hand, head down, adjusting her glasses, focused on her reading. But I also remember her running the classroom full of typewriters and computers which was across the hall from the library. She'd walk from computer to computer, typing commands, turning them on or off, inserting tapes or disks, making sure each computer had an instruction sheet or book for the next activity. Around the time of fourth grade, a few of those computers moved into the library itself, and the whole school used them to check out and return books -- under Mrs. Smarkola's watchful eye, of course.

My fourth grade teacher, Miss Herrick, was one of those teachers that all of the kids in school were afraid of. Kids talked about her being "hard" and "mean" -- but when I got in to her classroom, I was in heaven. You see, Miss Herrick loved math. I loved math. We were a perfect match! She frequently gave us math quizzes with long division problems, which I always aimed to complete first -- because the first to finish got to "play" on the computer we had in the classroom. I'd guess that I spent more time on that computer than anyone else, and I think I was also the classroom "computer aide," to help other students with it. (BTW, to this day, I love doing long division in my head when I'm bored.)

So many of us kids at Grace Park were interested in computers and learning, that our awesome principal, Dr. Joseph Fleischut, authorized a program called "Dawn Patrol" which was run by Mrs. Smarkola and Miss Herrick. For kids who signed up and got to school about 30 minutes before the opening bell, it was a time to use the computers, typewriters, and library. As you may have guessed, I signed up nearly every day. It may have been during Dawn Patrol that I programmed a TRS-80 CoCo 2 to play the harmony to "Yesterday" by The Beatles, so that it could accompany me as I played the melody on the flute. (When I got to perform at the district concert with the computer, it choked under the hot lights of the stage, sadly.) It also may have been there that I first attempted to program a Joshua-like AI from WarGames. I definitely spent time playing the Oregon Trail and Carmen Sandiego games there, as well as being questioned by Eliza. But what I remember with the greatest certainty (and the utmost thanks!) were the ways in which Mrs. Smarkola and Miss Herrick (and Dr. Fly, too) encouraged me, nurtured my passion for math, computers, reading, and learning, and always praised me for my accomplishments -- key factors which recent studies say are crucial to getting more women in to STEM.

Adele Mildred (Milly) Koss

Milly Koss and Me I was introduced to Milly Koss in September 2006 when a historical marker was placed at the site of the Eckert-Mauchly Computer Corporation.

Milly Koss "had a distinguished career of more than 47 years in all phases of computer technology, implementation and management, including applications design and development, software/hardware selection, database technologies and computer security." Her name is known to some -- but not enough, in my opinion.

Milly was raised in Philadelphia and attended the selective Philadelphia High School for Girls. She earned a scholarship to attend the University of Pennsylvania in 1946, at a time when schools were primarily giving spots to veterans. She graduated in 1950 with a degree in mathematics. In the early days of computing, women were seen as ideal computer programmers due to their "patience, persistence, and a capacity for detail." Of course, in order for a woman to get one of these jobs, she had to have a degree in math and not be married. Milly Koss qualified on the first point, but not on the second: she was engaged. The first company she interviewed with rejected her for this reason.

Fortunately, she was in the right place -- Philadelphia was home to the Eckert-Mauchly Computer Corporation and, from the way Milly describes it, I imagine it to be a workplace much like any modern internet company -- except that 40% of their programmers were women. Milly interviewed with Dr. John Mauchly, who she described as being very nice, flexible, and open. He gave her a wonderful, exciting, creative job -- working with the UNIVAC.

Milly worked with Grace Hopper and was responsible for developing Editing Generator, a problem-oriented language for computer-generated reports, in 1952. Milly was interested in what "computers could do for programmers... how it could help programmers program." She also worked on sort routines for years, which she calls "the quintessential program for machines." She reminds us that today we should be grateful for that early work in automated programming, interpreters, assemblers, and compilers.

By the way, much of this she did while working part-time and remotely! According to Milly, when informed about her pregnancy, Grace Hopper told her to "take it home" -- meaning, the work. Milly would go in to the office one or two days a week, otherwise working from her dining room table. In an interview with Kathy Kleiman (who is the driving force behind the ENIAC Programmers Project), Milly said:

"What’s funny about that period, I’m not sure who my boss was. This was such an unstructured environment… Once I had a child they let me continue to work the way I wanted to. I inferred from that I was of value to them. Nobody lets you work that way unless they are getting value. I got increases. I got paid fairly well. Eckert & Mauchly was pretty good that way… There were no models, they didn’t care how you worked. There were no preconceived notions as to the way you could contribute. You did not have to be in the office…. We did not have huge management teams. We did incredibly new and exciting things and nobody had a problem.”

Milly later went to work for Burroughs Corporation, Philco, and Control Data Corporation, and Raytheon. At Burroughs and Philco she continued her flexible work schedule and would send her work in by mail! At CDC, she worked with early graphics algorithms and interfaces including light pens. Then Milly moved to Harvard University, where says she finally started feeling the hierarchy and loss of flexibility. She spent 27 years at Harvard, in multiple roles. She applied data management expertise to applications for the school and led an R&D effort to develop one of the first data warehouses, the Information Utility. She served as Associate Director of the Office for Information Technology and as the Information Security Officer for the university.

Milly retired in 1994. In 1997, she received a Pioneer Award at the Grace Hopper Celebration of Women in Computing. In 2000, she received the Ada August Lovelace Award from the Association for Women in Computing. With her many years of contributions to the field, I'm sure she also inspired many people -- women and men alike.

Additional Resources

Kimberly Blessing

Preparing for Your Web Developer Job Search

6 min read

It's a new year, and perhaps you're a Web Developer looking for a new job. As a long-time Web Developer, here are three things I prepare when looking for work, whether it be freelance or full-time. And as a hiring manager, these are the same three things I'm looking for from the candidates who apply for work!

A Resume

I don't care whether I get one page or three pages from Web Developer candidates -- as a hiring manager, I do review the whole thing. Just don't fill it with fluff. I'm looking for dates of employment, size of company/product/team, type of work performed, and skills utilized. The general stuff which you do on a regular basis (emailing with Outlook, writing documentation in Word, slicing of assets in Photoshop or Fireworks, etc.) can just occupy a general skills section rather than be repeated for each job. Starting the resume with a technical skills overview gives me a quick snapshot of what you say you're capable of, and is a likely place for a hiring manager or recruiter to start with questions -- so don't list technical skills which you can't back up with experience! (Saying you have experience with HTML 5 when you haven't done much more than read a few blog posts is a sure-fire way of getting your resume nuked in a company's recruiting database, thus removing you from future consideration.)

While a beautifully formatted resume is always nice, don't agonize over it: using a Word resume template is just fine. Keep in mind that your resume doesn't always get through to the hiring manager in the format you sent -- so prepare a plain text version for textarea uploads. I know that typos sometimes make it in to a resume, and the occasional one will be forgiven or overlooked -- but do make sure to spell and grammar check everything! After all, if you don't QA your resume, how will a hiring manager know if you QA your code? (Need help? Read this and this.)

A Portfolio

To me, your resume is a formality of the hiring process, just metadata. Your portfolio is the real content which will be reviewed with a far more critical eye. The fact that portfolios aren't requested 100% of the time when seeking Web Developer positions only speaks to a hiring process which still treats the Web Developer role like a traditional programming job. Web Developers know otherwise, and if you truly want to be seen as a professional Web Developer, you'll have a portfolio at the ready. Do not slap something together on an as-needed basis -- proactively prepare a portfolio and send it even without request!

A portfolio should highlight your best work -- not all of your work. Don't include every project you've ever worked on. Choose three to five of your code samples which exemplify things like your coding style, ability to reconcile project requirements versus technical constraints, attempt to put HTML 5 into practice, etc. No one project will demonstrate all of those things, obviously, so make it clear why each project is included -- give a short narrative for each project to point someone to what you want them to focus on. Remember, you won't be the room when the portfolio is reviewed (unless it's brought up during an interview, which the portfolio will help you to score), so hand-hold the reader a bit.

I'm going to write a more in-depth post about what should go in a portfolio and how hiring teams review portfolios, so stay tuned.

A Web Site

May I vent for a moment? I can't believe how many Web Developers apply for jobs and don't have a Web site of their own. Where, pray tell, do all of these folks do their testing and noodling with servers and code? Why would you not want some online repository of your code? OK, venting done.

Yes, I do realize why some Web Developers don't have Web sites, but when you're searching for a new job, you need to have one. No, you don't need to have a blog with a lot of profound blabbering about technology, but yes, you should have an online copy of your resume and portfolio. When a recruiter or hiring manager Googles you (oh yes, we do!), you should want something more than your Facebook page to come up in the results.

I really think the most important reason for having the Web site is to host your portfolio. With an online portfolio, you can still highlight a few key projects while hosting copies of all of your code. This way, at a moment's notice, you can direct someone to (or, in an interview, walk someone through) a code solution that exemplifies a point you're discussing. Plus, you can preserve your code as it was when you finished it (delivered it, launched it) -- no longer will you have to make statements like, "I made the templates for the CMS but someone else maintains them now, plus the content folks don't know XHTML, so I don't know if the pages still validate." Worried about keeping copies of your code online? Just password-protect your site. If you give each recruiter a unique username/password to access your site, you'll be able to check your server logs to determine who's actually checked it out.


How will having all three of these things prepared and submitted help you in your job search? First and most importantly, it will get you in the door faster -- literally. If you have decent experience and great code samples which are hosted online, I'm more likely to tell a recruiter to just bring you in for an interview, rather than go through the preliminary phone screen. Why would you want to wait and let someone else get interviewed (and possibly get an offer) first?

If you're looking for your first Web Development job out of school, as a new career, or if you're switching from freelance to full-time employment, the portfolio can be especially helpful in leveling the playing field. If you're able to demonstrate strong skills but have little or no job experience, you're more likely to get an interview than someone with years of experience but no portfolio.

Of course, while you're in the midst of a job search, all of these tools are equally useful for getting short-term contract work, too!

What else do you think is crucial to a Web Development job search? Leave your thoughts in comments. If you have questions, I'm happy to answer those in the comments as well. Best of luck with your job search!

Kimberly Blessing

Geeky news stories you might have missed

2 min read

Some of these stories are a few weeks old -- sorry, that's what happens when you go to SXSW!

Kimberly Blessing

Honoring Ada, Inspiring Women

5 min read

Today is Ada Lovelace Day, an international day of blogging to draw attention to women excelling in technology. Ada Lovelace was a mathematician and, essentially, the first computer programmer (in an age where mechanical calculating machines were still ideas drawn on paper). Born in 1815, she envisioned machines which could not only compute calculations, but also compose music.

When computer science students are learning the history of the subject (assuming they get any historical teachings at all -- our history is "taught" via small anecdotes as footnotes in textbooks), Ada Lovelace is sometimes the only women ever mentioned. However the history of the field is strewn with the impactful and inspiring stories of women: Grace Hopper, Jean Bartik and the other ENIAC programmers, Milly Koss (why doesn't she have a Wikipedia page?), Fran Allen, Anita Borg, Telle Whitney, Wendy Hall, Ellen Spertus -- and those are just the high-profile women whose names are likely to be recognized. There are so many other women out there who have done, are doing, and will do great things for computing, technology, and the world -- and today's blogging event will expose all of us to a few more.

Although I've found many female role models in computing and technology, none were as important to me as the women I was surrounded by in college, when I was pursuing computer science as a major. Bryn Mawr's computer science department didn't exist yet -- in fact, we had only one full-time CS professor back then! But there were plenty of women on campus interested in technology and they were my primary motivators and supporters in those days.

Amy (Biermann) Hughes, PhD graduated from Bryn Mawr in 1995 and received her PhD in computer science from the University of Southern California in 2002. She is currently a member of the technical staff at MIT Lincoln Laboratory. I think I first met Amy when we were working together for Computing Services as student operators ("ops" for short) and she was an immediate inspiration. Amy seemed to know everything there was to know about networks, and she taught me a great deal. The fact that she'd decided to major in CS without there being an official major made the idea of me doing it seem feasible. Amy had done research as an undergrad -- another fact which amazed me -- in parallel computing! (That just flat out floored me.) On top of all of that, she loved Duran Duran. I'm not kidding when I say that there were times at which I'd say to myself, "Amy got through this somehow, I can too!" In fact, I'm still telling myself this, as every time I think about going back to school for my PhD, I wonder how I'll get over my fear of qualifying exams and I remember that Amy did it, so can I!

My compsci partner-in-crime from my own class was Sarah Hacker (yes, that's her real name). She graduated from Bryn Mawr in 1997 and went on to do graduate studies at SUNY Buffalo. She currently works in health care information systems at the University of Iowa. Sarah and I were in many classes together before we ever struck up a conversation. I was intimidated by her natural programming abilities -- to me, it seemed that she could pick up any language syntax and any programming concept so easily! -- but I came to greatly appreciate and sometimes rely on them. We also worked for Computing Services and frequently worked the night shifts together, drinking soda, eating candy, and making bizarre photo montages (such as Sarah's brilliant Child of the Moon series). In fact, it was Sarah who first showed me how to create a web page, so I really owe her quite a bit! Sarah introduced me to Pulp (the band), reintroduced me to Real Genius, and taught me LISP for an AI assignment. We started the Computer Science Culture Series together and were featured in the Philadelphia Inquirer for our robots, Jimmy and Timmy. Generally, she just kept me company and in good spirits, and I can only hope that I did the same for her.

Fortunately Amy and Sarah are still friends, so I continue to draw inspiration from their current lives and achievements as well. Of course, they weren't the only women who helped me make it through my undergraduate experience and early career -- Elysa Weiss, Helen Horton Peterson '79, and Jennifer Harper '96 (all Bryn Mawr Computing Services staff) were instrumental as well. And I have to give props to the men who were able to put up with supported a community of such strong women: Deepak Kumar, John King, Rodney Battle, and David Bertagni.

Those of us interested in computer science and technology are constantly looking forward, but today gives all of us a great opportunity to look back and highlight our common history and all of the people -- both men and women -- who've made today possible. Thank you, to all of them!

Kimberly Blessing

Programming, Old-School Style

2 min read

I have a fascination with old computers. Growing up, I heard stories of archaic devices used by my grandfather and his colleagues to accomplish their math and engineering work. Then I went through a few machines myself: the stand-alone Pong console, various TRS-80s, an Atari 2600, multiple Commodore 64s and a 128, finally making it into the x86 line. When I got a new computer, the old one didn't become obsolete trash; it gained a sort of revered status. I'd leave it hooked up, always at the ready, and occasionally I'd take a trip down memory lane and load up some old programs, tinker with something new, or perhaps just bask in the glow of the TV screen/monochrome monitor. Yes, I'm a strange girl.

A DEC PDP-11 Ever since my first visit to the Computer History Museum, I've been fascinated by the DEC PDP-11. The PDP-11 was a series of 16-bit minicomputers which were programmed with toggles. Their design was strangely attractive. I saw plenty of PDP-11 parts for sale on eBay and wondered what it would take to build one. I figured there had to be an emulator out there, but I didn't take much time to look around.

Well, it turns out there is. And there are instructions! Inspired by DePauw University's (slightly cheesy, but fun) videos on programming the PDP-11, lab[oratory] is posting detailed instructions on using the SIMH simulator to program a simulated PDP-11! So join along in the play and experimentation, and program your very own PDP-11. It may not be as cool as handling those purple toggles, but it's still fun.

Kimberly Blessing

Speaking up for Women in STEM

2 min read

With the Obama administration finally in office, women's issues have gained new focus. Of particular interest and importance to me is the focus on the lack of women in science, technology, engineering, and math (STEM).

The New York Times is writing about it (In 'Geek Chic' and Obama, New Hope for Lifting Women in Science) and public radio is talking about it (Breaking the glass ceiling for women scientists), as are so many other media outlets. So far I'm not hearing anything new -- meaning I'm not hearing any new ideas on how to affect change and bring in/retain women -- but I'm trying to remain positive. I have to hope that more coverage means more eyes and ears will consume this information, and that it may start to take hold with those unfamiliar with the issue.

Unfortunately, events of the recent past make that hope difficult to drum up sometimes. When pointing out statements made by men that were (intentionally or unintentionally) offensive or hurtful or discouraging towards women, I was told, in various ways, to shush and not get so emotional. Now, I have pretty tough skin, so I'm not pointing out statements and actions to defend myself, but to inform others of what their statements and actions may mean to other women. Maybe that's why I get the reaction I do -- perhaps my statements aren't seen as genuine, because I'm really not expressing emotion, and thus they are dismissed. Maybe I'm over-thinking this, but it does bother me, because I want to be a good servant in this area to my fellow women. Your suggestions and thoughts on how I can accomplish this are most welcome.

More reading...

Kimberly Blessing

I helped elect a female president!

2 min read

Yes, I wish I were talking about Hillary! But I'm not.

Instead I'm talking about the ACM elections, and the woman I'm referring to is Wendy Hall, CBE, Professor of Computer Science at the University of Southampton, Fellow of the Royal Academy of Engineering and the British Computer Society, co-founding director of the Web Science Research Initiative, and (if you couldn't tell) one of my role models. So the votes have been counted and, come July 1, Wendy will also serve a two-year term as President of the ACM. Congratulations!

I should also mention that Wendy received the Anita Borg Award for Technical Leadership from the Anita Borg Institute for Women and Technology at the 2006 Grace Hopper Celebration (GHC) of Women in Computing, for which I was the webmaster -- an awesome volunteer opportunity which just happens to be available! If you've got skills in WordPress then please apply!

And speaking of GHC, I also need to mention that registration for the 2008 conference is now open! After so many years of attending, stalking Telle Whitney, and volunteering, this year I'm finally going to be speaking on a panel! (Go me!) So, don't miss this opportunity to interact with thousands of smart, successful, techie women -- including Fran Allen!

Gosh I love being a woman in computing.