Please see below for posts that individual students wrote during the semester.
If you perhaps did not catch Paul Ford’s Business Week essay, What is Code? in your end of semester haze, it is worth reading.
In particular, I was about to send Stephen to read Section 3.4 on Object Orientation when I realized the rest of you could read it, too.
Dear Team #dhpraxis14,
We could not have gotten here without each and every one of us. This class has been a great challenge, and I like to think that rather than a Big Brother/Survivor style show, we have kicked no one off the island, but have come out of this challenge as a team.
Back when I was unsure of the name “TANDEM”, I made this video to get myself on board. Sometime musical theater is all you need to bring it together.
I am sharing it here in the event that it might bring any one of you some positive spirit moving into our presentations.
Thank you all.
We were happy to have the chance to see everyone’s presentations last week. Over the course of the semester we’ve all been working so intently on our own projects, it sometimes felt like we didn’t have enough opportunity to fully appreciate what everyone else has been working on.
Not surprisingly, all of the projects are awesome!
This has been an amazingly group of classmates, and we would like to thank you all for your support and input over the last few months. We’re excited to see where things go from here–not just for the projects, but for everyone individually as well.
Looking forward to Tuesday, you’re all rockstars!
Gossip Girl Team Digital HUAC
We are excited to end the year with a great presentation! and great group of classmates!
During the semester we:
- Successfully changed project direction
- Negotiated group schedules
- Created our own work flow communication process
- Learned from project complications
Our group was interested in how to work with audio in a DH capacity and we have created a process to work with audio with a community of users!
This last week has concluded work on final paper and presentation and continued touch ups to the websites functionality.
With continued help from from prof Hickman we continue to step further and further forward with web functionality.
And with some helpful class members we move forward with a better more mobile site.
A warm thanks to everyone!
See you all Tuesday.
This week, everyone rehearsed at the Sky Lounge and got feedback for the showcase. which will be held next Tuesday. Our group’s running time was properly set. The speech would take approximately 8 minutes. We will show the running Python script (attached in the About section) and cover theories, progress, and future aspects of the studies.
Please plan to be in Room 9205 by 4 pm on Tuesday (or have at least one member of your group there at that time) so we can verify setup ahead of the event. More details will be coming about an afterparty in the MALS Lounge, but I want to issue two quick reminders about your presentations.
- First, be sure you’re as precise and specific with your language as you can possibly be. This goes for your written work as well, but you’ll need to remember you’re presenting to people unfamiliar with your work and in many cases your methods. Clarity will be key to getting across what you’ve accomplished.
- Second, make sure your presentations include a statement of the current state of the project. Is it useable? Is it a proof of concept that’s viewable, but that’s not functional in an interactive way? What each group has produced absolutely passes muster for the requirements of the course (even if tied together in certain spots with string and duct tape). You can feel comfortable giving the audience an honest sense of what they’ll get when they visit your urls.
Finally… I have been working with a couple of you to fine tune your pitches, and Amanda and I are available to give that feedback right up to the time of the launch. If you want to run anything by us, need some help with language, or are confused about anything at all… just holler.
We’re meeting in room 9205 today.
This week we’ve been working on our presentation and also fine-tuning narrative elements that will go into our paper. We’re thrilled to be at this stage and are looking forward to Tuesday and sharing in our classmates’ presentations.
WEEK 14 (Can it really be?)
TANDEM PROJECT UPDATE:
Presses have rolled (to some extent). Word of mouth is spreading and will only grow. The launch is upon us and we are ready to go.
Friday Chris and Jojo presented at the GC Digital Initiative’s Media Res #1. It was exciting to see TANDEM rolling with the NYCDH crowd. Not only were useful contacts made in the other presenters, but it gave us a chance to see how our final presentation should go. In under five minutes, Chris was able to describe the basic objectives and accomplishments and the proto-website easily stood up to the standard of the other presentations (even as a definite pre-rollout version). Chris also got first hand experience with areas that need more or less explaining. Optimizing 10 speaking minutes will be a challenge, but it was a productive and constructive exercise to give it a dry run. It also allowed the team to make more focused and concise presentation slides.
Thanks to tips from Tim Owens and Zach Davis, we have fixed the bug that was causing unpredictable results. The bug meant that some users would experience a session crash (unhandled error), others would go through all the steps and get back an empty result set, while still other users would get results with other project results inexplicably mixed in. The solution was based on the ‘aha!’ realization that the web is a stateless environment and that the programmer must take steps to ensure that a session across multiple requests and responses remains a single logical whole. The way to do that is to use anonymous cookies to identify the session and store the project-id in that cookie. Using the project-id, the program looks up in the database all the information required including the location of the files and folders in use for that project. There is no doubt that we have achieved our MVP and it is a good reliable user experience. There is a tiny bit of styling left to be done and the program is finished as far as version 0.5.