Sunday, February 17, 2008

washingtonpost.com redesign, round 3

Last April, I wrote a full-length post here on this blog on what I thought was wrong with the washingtonpost.com redesign. Two days later, I wrote a follow up on this blog containing my posted comment to washingtonpost.com editor Jim Brady. Shortly after that post, I wrote a short follow-up on Edward Tufte's Ask E.T. forum topic on the redesign. The text of my post in the Ask E.T. forum appears below.

You might appreciate seeing this marketing piece on Apple's website that profiles both Mr. Jim Brady, executive editor of washingtonpost.com and Ms. Jenn Crandall, the producer of OnBeing. It sheds a lot of insight as to why washingtonpost.com is the way it is today.

http://www.apple.com/pro/profiles/washingtonpost/

A couple of things to put into perspective... washingtonpost.com is an entity separate from The Washington Post newspaper, both part of Washington Post Newsweek Interactive (WPNI). Obviously, the web site draws from the work of the print newspaper as well as from its reporters, but from what I've read in the corporate information, washingtonpost.com is there to cull highlights from the paper for the web and provide web-only features. What I'm saying here is that the organizational hierarchy probably plays into the organization of the website. Hence, the washingtonpost.com logo is not the same as the masthead of the print paper and we see that the "print edition" or "today's paper" as it's labeled now has always seemed kind of detached from the remainder of the page.

Second, I'm sure we're all aware of the pressures that traditional newspaper organizations face. Subscriptions are decreasing, ad revenue is decreasing, and as a result, newsrooms are shrinking. I get the feeling that washingtonpost.com has become the experimental proving grounds to find a new revenue source to make up for lost traditional revenue. In the words of one of my friends in the news industry, "we're trying anything and everything to see what sticks.

Hence, they are trying to work all sorts of media into washingtonpost.com. Not all of it is bad, but of course, the problem is as Mr. Tufte stated, the Washington Post is a news organization -- that is its reason for existence. The fanciest multimedia and the neatest interface can't make up for a lack of depth in the content, which is going to be the trend if they continue to shrink the newsroom.

-- Kendrick Hang (email), April 12, 2007

The marketing video has changed since then, but the spirit of it is still the same. And if you go to washingtonpost.com right now, you will still see two logos: one for washingtonpost.com and one for the Washington Post. I have a correction to my above post though: the parent company is not Washingtonpost.Newsweek Interactive (WPNI), but rather The Washington Post Company. WPNI is in charge of washingtonpost.com and newsweek.com, while The Washington Post Company is parent to The Washington Post, WPNI, Express, Newsweek, Slate, Arthur Frommer's Budget Travel, and Kaplan (the educational services company), among other ventures.

Now, in this week's Washington City Paper, a story on what I mentioned above: One Mission Two Newsrooms. In addition to the story, the City Paper made a video to show how geographically separated washingtonpost.com is from The Washington Post.



My point still remains the same: why should readers care and have to differentiate what the corporate organization of The Washington Post Company is? Why are there two navigation structures on their website: one for washingtonpost.com and an alternate structure for the print edition of Washington Post (under the link Today's Paper)? To us, it's all one single newspaper. If I spot an article in the Food section on Wednesday, I have to figure out if it appears in the Arts and Living section on the washingtonpost.com main page or if I have to go under the Today's Paper link to find it the Food section under the print edition Washington Post.

Maybe this is just a classic problem in DC. Is the Washington Post just a reflection of the turf wars and bureaucratic infighting that is so common in so many workplaces around the region? This is definitely not the first time I've encountered multiple people or divisions in an organization vying for influence without regard for the greater organization. I will admit however that integration, within organizations and within the context of design is quite challenging. However, I still believe in the bottom line: people external to an organization, particularly customers and users, should not have to be exposed to the bureaucracy within the organization, especially in the form of design.

Labels: ,

licensing versus certification

The following is a short, informal piece I wrote for a class last year while we were debating whether or not software engineers should be licensed. The debate continues in real life as the software industry as a whole is trying to find agreement on the issue of whether or not software engineers should be licensed.

In casual English, licensing and certification have similar meanings. However, in the context of the debate on whether software engineers should be licensed like traditional Professional Engineers (PEs), licensing and certification have very distinct meanings.
The following are definitions from Knight and Leveson (2001), ACM Task Force on Licensing of Software Engineers Working on Safety-Critical Software. The notion of licensing is to have some authority grant permission to an individual to engage in an activity that is otherwise unlawful.

Similarly, certification assures that an individual meets a minimum set of requirements.

Licensing and certification differ primarily in the permission to act. Licensing is mandatory and is a state or federal activity (usually state) while certification is voluntary.
The local governments in Texas and provinces in Canada are licensing software engineers today as PEs with legal rights. Meanwhile, other professional organizations in industry are in the business of certification. For example, the IEEE has the Certified Software Development Professional (CSDP) program, the Project Management Institute has the Project Management Professional (PMP) program, and of course many are familiar with the gamut of technical certification programs like the Microsoft Certifications.

My point is, if we software engineers are going to discuss/debate this topic and be understood, we should aim to be precise in our wording. It's the only way we can all understand what someone really is saying instead of making assumptions and implications. I know, this sounds like an advertisement for good requirements analysis and specification techniques.

Now for the alarming part. If one takes note of the Texas PE exam requirements one will find that their exam has little to do with software engineering as it is typically treated in academia and in industry. Searching around on their website, I found Texas Board of Professional Engineers meeting minutes (pdf) (2005) where they decided to use the IEEE CSDP certification exam for licensing software engineers as PEs in Texas until a better exam comes around. From the minutes, "IT WAS MOVED AND SECONDED (Frailey/Rodriguez) that the Board accept the CSDP examination as an interim substitute for a PE exam in software engineering, until such time as a national exam is provided by NCEES and reconsider the licensure of software engineers."

To me, this is not a real confidence builder in their system of licensure -- I just think Texas jumped the gun a little. Before we as a software community have understood what the implications of licensing are and before we decided on what the best means of licensing are, Texas already started issuing licenses to legally allow people to do things, while considering to use a minimum certification exam to allow them to do it. One would like to think that if licenses are being issued to people who are trusted to do something safety-critical like design software for an aircraft system or a medical device, they should know more than the minimum requirements. The Texas exam, and any exam really, determines a minimum level of knowledge, but it does not determine competence or mastery.


References
IEEE Certified Software Development Professional Program. Retrieved May 30, 2007, from http://www.computer.org/certification

Knight, J., Leveson, N. et al. (2001, August). ACM Task Force on Licensing of Software Engineers Working on Safety-Critical Software. Retrieved May 30, 2007, from http://www.acm.org/serving/se_policy/safety_critical.pdf

Microsoft. Microsoft Certifications Overview. Retrieved May 30, 2007, from http://www.microsoft.com/learning/mcp/default.mspx

Project Management Institute. Certification Project Management Professional Overview. Retrieved May 30, 2007, from http://www.pmi.org/info/PDC_PMP.asp

Texas Board of Professional Engineers. Examination Information. Retrieved May 30, 2007, from http://www.tbpe.state.tx.us/lic_exams.htm

Texas Board of Professional Engineers. (2005, August). Minutes, Industry Advisory Committee, August 16, 2005. Retrieved May 30, 2007, from http://www.tbpe.state.tx.us/minutes/ind_81605.pdf

Labels:

Wednesday, February 13, 2008

spring 2008 dc film festivals

10 February 2008
Our City Film Festival
Ok, the one-day Our City Film Festival came and went and I missed it. But I like the concept of the festival: to feature films that feature DC. I'll keep an eye out for it again next year.

6-16 March 2008
DC Independent Film Festival

11-22 March 2008
DC Environmental Film Festival
In it's 16th year, the DC Environmental Film Festival will be screening 115 films at over 45 different venues around town over the course of 11 days. I checked out the listing of films and there are many that I would love to see, including: All In This Tea, Ansel Adams, Darwin's Natural Heir (a biopic on E.O. Wilson), and Galapagos: Born of Fire. I will miss seeing the films this year (I'm hoping some of them will be released on DVD) as I will be out with my camera in the Galapagos! Although I will not be retracing the voyage of HMS Beagle, I will be wandering from island to island on this wooden schooner:

Galapagos - Wooden Schooner
Photo credit unknown. (This photo was all over the web without attribution.)

24 April - 4 May 2008
Filmfest DC International Film Festival
From their website: "Films will encompass a global range of cultures, music, and politics from over 30 countries. Festival highlights will include the cinema of Latin America and Politics on Film."

16-23 June 2008

Silverdocs: AFI/Discovery Channel Documentary Festival
Still accepting submissions from filmmakers, the regular deadline is this Friday 15 February.

If you want to keep an eye out for the fall film festivals, some links to follow: DC Shorts Film Festival (September), National Geographic All Roads Film Festival (October), DC APA Film Festival (September-October), Latin American Film Festival, Reel Affirmations (October), and the Washington Jewish Film Festival (December).

Labels:

Monday, February 11, 2008

potomac primary voter info

Courtesy of Maria F., voter information for tomorrow's Potomac Primary, Chesapeake Primary, or Mid-Atlantic Primary. Whatever you want to call it, the info for Va., D.C., and Md. is below.

Virginia
Voter registration status
Polling place locator

District of Columbia
Voter registration status
Polling place locator

Maryland
Voter registration status and polling place locator

Labels: