George Boole (1815-1864) was a mathematician best known as the progenitor of the Boolean algebra, the system of logic that acts as a fundamental layer within digital systems. Although he never gained a college degree, he spent many productive years as the chair of mathematics at Queen’s College, Cork. Desmond MacHale’s The Life and Work of George Boole is a well-written exploration of Boole’s life, personality, and impact.
In 1971, three college roommates developed an educational computer game. Titled OREGON, it was a simulation of westward migration along the Oregon Trail and proved to be a hit among the students. One of the designers, Don Rawitsch, later carried a copy of the source code to his new employer, Minnesota Educational Computing Consortium (MECC). From 1975 to 1983, OREGON was MECC’s most popular courseware on their timeshare service. When MECC decided a new version was merited, which became The Oregon Trail, they mandated the design team to “preserve whatever made the original so popular.” With the availability of the source code for the 1975 and 1978 versions, we explore the design and implementation of OREGON and why it was popular and memorable.
In Fifth Edition (5e) Dungeons & Dragons™ (D&D), druids can transform into certain Beast forms using the Wild Shape ability. Similarly, casters of the Polymorph spell can transform allies and enemies into Beasts. Players often find selecting a Beast form onerous (there are 84 forms defined in the System Reference Document (SRD) alone) as this is a multi-dimensional decision problem.
On August 15th, 1971, President Nixon declared a 90-day freeze on wages, rents, and prices. The next day, the Office of Emergency Preparedness (OEP) was charged with implementing the Freeze. OEP launched an administrative crash program, leveraging the expansive power of the federal government, and also took the risky step of developing novel software to facilitate coordination of hundreds of federal employees. Originally called the Emergency Partyline, the software was soon known as EMISARI. EMISARI aided the OEP with internal communications, reporting, and conduct of their mission. Leveraging early time-sharing technology and a dialect of the BASIC language, EMISARI supported communications in the styles of chat, forums, and email as well as providing a flexible data collection and reporting workflow system. We explore the design and implementation of EMISARI and PARTY-LINE, the adjunct synchronous chat program, how EMISARI compared to the other software systems used by the OEP during the Emergency, and what lessons may be applied to modern startups and crash programs.