Archive TimeZone problem and its workaround

The problem we have been experiencing with the Archive listing being off from the blog entry listing is well known (and particularly prevalent in Hawaii!) See the thread here to follow the discussion and find out when the blogger folks implement the fix.

The temporary workaround is to use Pacific time, which of course makes the posting time off by a few hours. I've changed my blog to Pacific time and, voila, the problem disappears.

Software Development Communication Media

As I have maintained this online engineering log over the past couple of weeks, I have started to think more generally about the types of media used in a software development team to communicate and coordinate activities:

(1) Requirements and Design documents. These are relatively static documents, providing a high-level perspective. Relatively non-interactive.

(2) Mailing lists. Provide a forum for threaded communication. Generally ASCII oriented. Generally interactive.

(3) JavaDocs. Generated from the code itself. Communicates API-level information. Non-interactive. Context-sensitive with the code.

(4) Engineering logs. Semi-interactive way for an individual developer to document design issues, questions, and so forth. Others could potentially comment on log entries.

(5) CM Commit messages. Provides a record of the changes made to a set of sources.

(6) Issues. Provides a decomposition of the high level requirements/design documents into a set of tasks. Also records bugs found.

(7) IM. Generally non-persistent, highly interactive means for developers to get immediate, synchronous feedback and help.

(8) Face to face meetings.

Recently, I was thinking about an idea that I wanted to discuss with the Hackystat software development team, and I was unsure of how to do it:

• Send it as an email to the developer's mailing list?
• Write about it in my online engineering log?
• Write about it in my online engineering log, then send a link to that entry in an email to the developer's mailing list?
  

Online Engineering Logs

Overview
A traditional engineering log (EL) is a notebook. Developers maintain an EL to record information that facilitates software development, including "to do" lists, emergent designs, problems they are encountering, and rationales for implementation decisions. They serve as a kind of "offline memory", that helps engineers in several ways:

• It helps them to quickly re-establish what they were working on at the start of each day, or if they have been interrupted from the project for multiple days.
  
• It provides a media in which to work out issues and questions they are having during development.
  
• It supports management of the many 'micro-tasks' that emerge during development. By maintaining a "to do" list, the engineer can keep track of things that need to be done later without interrupting the current task.
  

For over 10 years, I have kept a traditional engineering log in a series of notebooks. This blog represents an experiment in moving my private, personal, offline EL into a shared, public, online setting. I am interested in understanding what the trade-offs are between private offline ELs and public online ELs.

Pros and Cons:

Advantages of Online Engineering Logs:

• People can comment on postings. So, you can indicate an issue you're having in your EL and someone might help you with it.
• By tagging a post with the issue ID, you can search the online EL later to recover design rationale information.
  
• Other developers in your workgroup can subscribe to your blog in order to keep track of what you're doing without interrupting you.
• It is easy to include images.
• It is easy to include links.
  

Disadvantages of Online Engineering Logs:

• There is a huge privacy hit. It is definitely way different to be writing in a public forum vs. your own notebook where no one is going to see it. I am interested to see whether this is ultimately positive or negative.
  
• You have to be online to manipulate them. I will perhaps be writing things on paper and transferring to this blog?
• At first, you spend a lot of time fooling around with formatting.
• It is hard to doodle.
  

Adapting the Blog media to Engineering Logs:

• It's not clear that you want to maintain strict timestamps. For example, I want to maintain this list within this entry over time and edit it repeatedly. It would not make sense to build up this list by scattering it across all of the days that I came up with items. I have edited this entry repeatedly over the past several weeks, which seems perfectly appropriate. This seems quite counter to the conventional wisdom for maintaining engineering notebooks, where timestamping your thoughts is a critical feature.
• Personal vs. Project Engineering logs. One could imagine keeping a single blog for a project, with multiple authors, or having each author keep their own blog, and use tags to indicate the project. I am not at all sure what the pros and cons these approaches are.
  

Related links:

Engineering notebooks are related to engineering logs but are more focussed on patent protection:

• http://www.williamson-labs.com/notebook.htm
• http://www.bookfactory.com/special_info/engr_notebook_guidelines.html
• http://www.cybertribe.com/mayer/wwweasel/node2.html
• http://web.cecs.pdx.edu/~warren/Capstone/index.cgi?PAGE=engineering_notebook
• http://www.ece.drexel.edu/SeniorDesign/notebook.pdf
  

Some example online engineering logs:

• http://sendes.posure.com/
• http://www.missioncode.org/blog/
• http://www.naic.edu/~cima/cima_engineering_log.html
• http://people.msoe.edu/~rothede/twiki/bin/view.cgi/SeniorDesign/EngineeringLogs

None of these seem to fully exploit the possibilities of modern blogging infrastructure for supporting online engineering logs.