http://www.makinghistorypodcast.com Fri, 18 Feb 2011 02:06:57 +0000 hourly 1 http://wordpress.org/?v=3.2.1 http://www.makinghistorypodcast.com/2011/02/17/upcoming-schedule-for-the-past-tense-lectures-at-the-huntington-library/#comment-292 Tweets that mention Upcoming Schedule for the Past Tense Lectures at the Huntington Library | Making History Podcast -- Topsy.com Fri, 18 Feb 2011 02:06:57 +0000 http://www.makinghistorypodcast.com/?p=1042#comment-292 [...] This post was mentioned on Twitter by Douglas Dechow, Academic Technology . Academic Technology said: Marcy Norton to speak on "Writing the Long Duree" @theHuntington, March 22 for the Past Tense seminar: http://bit.ly/h1n4QQ [...] [...] This post was mentioned on Twitter by Douglas Dechow, Academic Technology . Academic Technology said: Marcy Norton to speak on "Writing the Long Duree" @theHuntington, March 22 for the Past Tense seminar: http://bit.ly/h1n4QQ [...]

]]> http://www.makinghistorypodcast.com/2010/09/01/a-room-of-ones-own/#comment-166 Zack McCune Fri, 03 Sep 2010 05:43:38 +0000 http://www.makinghistorypodcast.com/?p=931#comment-166 Can I just stress the white board (or chalk board based on your prefs) as an addition to your new office (congrats btw!). You see, whiteboards organize tasks/meetings/ideas/people/feelings/obligations et cetera. You will be so happy to have them written down outside of your mind or computer you will be happy happy happy! Can I just stress the white board (or chalk board based on your prefs) as an addition to your new office (congrats btw!). You see, whiteboards organize tasks/meetings/ideas/people/feelings/obligations et cetera. You will be so happy to have them written down outside of your mind or computer you will be happy happy happy!

]]> http://www.makinghistorypodcast.com/2010/09/01/a-room-of-ones-own/#comment-161 Melissa Wed, 01 Sep 2010 05:34:03 +0000 http://www.makinghistorypodcast.com/?p=931#comment-161 the poll only lets me pick one! But I recommend bookshelves, family photos, a whiteboard, tech stuff, plants, and a comfy chair. The coffeemaker might be better replaced with an electric kettle and an assortment of teas (knowing you!). Oh, and plants if you have good lighting. Make it a place you WANT to be, not a place you have to be. the poll only lets me pick one! But I recommend bookshelves, family photos, a whiteboard, tech stuff, plants, and a comfy chair. The coffeemaker might be better replaced with an electric kettle and an assortment of teas (knowing you!). Oh, and plants if you have good lighting. Make it a place you WANT to be, not a place you have to be.

]]> http://www.makinghistorypodcast.com/2010/07/13/history-over-the-air/#comment-157 Adam Arenson Thu, 26 Aug 2010 21:18:11 +0000 http://makinghistorypodcast.com/?p=801#comment-157 Thanks! We try to keep it interesting, informative, and frequent; check out the latest here: http://www.makinghistorypodcast.com/?p=922 Thanks! We try to keep it interesting, informative, and frequent; check out the latest here: http://www.makinghistorypodcast.com/?p=922

]]> http://www.makinghistorypodcast.com/2010/07/29/identity-crisis-day-or-one-week-one-tool-day-3/#comment-139 One Week | One Tool: Interim Report Tue, 17 Aug 2010 15:02:26 +0000 http://makinghistorypodcast.com/?p=840#comment-139 [...] Wednesday, Thursday, and Friday were each long days of code, design, and writing. The group quickly established a daily routine, which started with an all-project check-in meeting at CHNM’s offices at 10:00 a.m., was punctuated by a return to the Mason Inn at about 6:00 p.m., and ended with yet more work at the hotel bar, usually until well past closing. Communication, leadership, and even membership among the teams were fluid, with teams spontaneously reconfiguring as particular skills were required for particular tasks. Moreover, throughout this "doing" phase, Tom, Dan, Jeremy, and Trevor encouraged additional CHNM staff—including Sharon Leon, Sheila Brennan, Ammon Shepherd, and John Flatness—to be available to help participants solve problems and make tough decisions. By Saturday morning, the One Week | One Tool team had designed and built the software; established an open code repository, a ticketing and bug tracking system, and a set of open source community development channels; and mounted an outreach and marketing campaign that consisted of an original name, logo, and website, as well as promotional bookmarks and stickers, a CafePress storefront, a formal press release, a media contact sheet, a set of public use cases, an FAQ page, and other end-user support channels. [...] [...] Wednesday, Thursday, and Friday were each long days of code, design, and writing. The group quickly established a daily routine, which started with an all-project check-in meeting at CHNM’s offices at 10:00 a.m., was punctuated by a return to the Mason Inn at about 6:00 p.m., and ended with yet more work at the hotel bar, usually until well past closing. Communication, leadership, and even membership among the teams were fluid, with teams spontaneously reconfiguring as particular skills were required for particular tasks. Moreover, throughout this "doing" phase, Tom, Dan, Jeremy, and Trevor encouraged additional CHNM staff—including Sharon Leon, Sheila Brennan, Ammon Shepherd, and John Flatness—to be available to help participants solve problems and make tough decisions. By Saturday morning, the One Week | One Tool team had designed and built the software; established an open code repository, a ticketing and bug tracking system, and a set of open source community development channels; and mounted an outreach and marketing campaign that consisted of an original name, logo, and website, as well as promotional bookmarks and stickers, a CafePress storefront, a formal press release, a media contact sheet, a set of public use cases, an FAQ page, and other end-user support channels. [...]

]]> http://www.makinghistorypodcast.com/2010/08/01/pencils-down-day-or-one-week-one-tool-day-6/#comment-152 One Week | One Tool: Interim Report Tue, 17 Aug 2010 14:59:35 +0000 http://makinghistorypodcast.com/?p=870#comment-152 [...] John Flatness—to be available to help participants solve problems and make tough decisions. By Saturday morning, the One Week | One Tool team had designed and built the software; established an open code [...] [...] John Flatness—to be available to help participants solve problems and make tough decisions. By Saturday morning, the One Week | One Tool team had designed and built the software; established an open code [...]

]]> http://www.makinghistorypodcast.com/2010/07/27/some-initial-thoughts-from-my-dh-summer-one-week-one-tool/#comment-122 One Week | One Tool: Interim Report Tue, 17 Aug 2010 14:59:22 +0000 http://makinghistorypodcast.com/?p=808#comment-122 [...] Monday was originally designed as the "teaching" phase of One Week | One Tool, during which CHNM staff members would provide participants with some lessons in software development best practices. This was ultimately the least successful portion of the program. Although introductory talks on technical aspects of software development (Jeremy Boggs), outreach mechanisms and community building (Trevor Owens), and the state of the art of digital humanities tools (Dan Cohen) were well received, participants were eager to get down to brass tacks, and we made a strategic decision to cut short the lectures and begin brainstorming tool choices a half day early on Monday afternoon. [...] [...] Monday was originally designed as the "teaching" phase of One Week | One Tool, during which CHNM staff members would provide participants with some lessons in software development best practices. This was ultimately the least successful portion of the program. Although introductory talks on technical aspects of software development (Jeremy Boggs), outreach mechanisms and community building (Trevor Owens), and the state of the art of digital humanities tools (Dan Cohen) were well received, participants were eager to get down to brass tacks, and we made a strategic decision to cut short the lectures and begin brainstorming tool choices a half day early on Monday afternoon. [...]

]]> http://www.makinghistorypodcast.com/2010/07/31/risk-strategy-or-one-week-one-tool-day%c2%a05/#comment-150 One Week | One Tool: Interim Report Tue, 17 Aug 2010 14:49:01 +0000 http://makinghistorypodcast.com/?p=862#comment-150 [...] Thursday, and Friday were each long days of code, design, and writing. The group quickly established a daily routine, [...] [...] Thursday, and Friday were each long days of code, design, and writing. The group quickly established a daily routine, [...]

]]> http://www.makinghistorypodcast.com/2010/07/30/pants-day-or-one-week-one-tool-day-4/#comment-147 One Week | One Tool: Interim Report Tue, 17 Aug 2010 14:48:25 +0000 http://makinghistorypodcast.com/?p=850#comment-147 [...] Thursday, and Friday were each long days of code, design, and writing. The group quickly established a daily [...] [...] Thursday, and Friday were each long days of code, design, and writing. The group quickly established a daily [...]

]]> http://www.makinghistorypodcast.com/2010/07/28/decision-day-or-one-week-one-tool-day-2/#comment-131 One Week | One Tool: Interim Report Tue, 17 Aug 2010 14:48:15 +0000 http://makinghistorypodcast.com/?p=832#comment-131 [...] outside feedback into account, the group conducted two rounds of voting of its own, making a final consensus decision by mid-afternoon on [...] [...] outside feedback into account, the group conducted two rounds of voting of its own, making a final consensus decision by mid-afternoon on [...]

]]>