Print This Post
As the MECA staff were describing the application, I didn’t have a clear sense of how beneficial our work would be. To illustrate how our application would help people, they showed us a video of a student going to a gym. In the first clip, the student has trouble following directions and signage about the use of gym equipment. In the second clip, the student is following auditory prompts and exercising at the gym with little trouble. Another student was able to prepare a meal with the help of visual prompts from a PDA. It was illuminating to see the difference that prompts could in someone’s daily life and spurred us to work even harder.
We decided to split the application into 3 components:
We had a team of about eight people, and we knew we had to separate tasks somehow. There were some individuals with iPhone experience (mostly novice stuff like simple view demos), and some with Ruby experience, and then there were two designers with CSS and some jQuery experience.
We figured Trevor, who has extensive Rails experience should lead the API effort, and that Brian, who has done the most, albeit little, iPhone development using MonoTouch should lead the student application effort, while the designers should focus on designing and implementing some of the builder code. (The interface for the user application had already been worked out by group consensus.)
I decided I could best help with the API, so I worked with Trevor on that. Something that I think amazed all of us was that once we had assigned ourselves to teams and broken the project up, we functioned seamlessly, all of us entering the zone in our respective areas. It’s the kind of synergy and flow you get when the majority of your team knows their shit. It was an incredible experience to be a part of that.
We had a good framework and sample response API for the student interface and builder to start building plumbing by the time we left on Friday. Meanwhile, the iPhone app team had gotten some samples working using Monotouch. The builder interface was looking really sharp. We were off to a good start when we decided to break for the night around midnight.
In the next post, I will describe some of the insights behind the API.
Print This Post
Print This Post
Dani led us into a different conference room from the main room that most of the other conference attendees stayed in the entire weekend. We met MECA members Gloria, Kaori, and Avi who teach autistic individuals how to function independently. They discussed some of their current work and successes, including the Preparing Adolescents for Adult Life (PAAL) program.
There a number of programs that are used to make an individual’s life easier. One, used by an individual with speech impairment, is a Powerpoint presentation featuring images of common items. Clicking on an image plays a sound file that represents the image. In this way, the individual can communicate with others.
Another program is a sort of flash-card program. This program helps guide a student through daily tasks by breaking the tasks into granular steps. The program also provides a choice option that prompts the user to choose among a set number of options. Although the user program is fairly effective, the authoring application for these files is cumbersome to use. Two drawbacks of this program exist:
MECA wanted a program that not only was easy to use for students, but also a program easy to use for instructors to author lessons. Additionally, a program that incorporated a task-list and monitoring component would be especially helpful.
While the staff explained some of the requirements, we were joined by other team members: Brian, Erik, Sebastian, and then Joe. There was another person who came to help during the night but he didn’t come on subsequent days. Much of that first Friday evening was spent just gathering requirements and attempting to fully understand the problem.
When we finally thought we had enough to start, it was around eight or nine at night. In the interest of time, we decided we would not work on a monitoring component. We decided to break the remaining problem into three components:
The next post will discuss the reason for this split.
Print This Post
Last weekend, Lisa and I took off Friday to attend Philly Give Camp. The Camp-type unconference is held to provide technical expertise and work to nonprofit groups. I first heard about the event through coworkers at Wharton, and I decided to sign up. I told some friends about it, and got Kosal and an ex-coworker from ABC, Jonathan to come as well.
I sometimes think about how great my life has been, and how fantastic it is now, and I’m disappointed in myself that I haven’t given much back. Philly Give Camp provided an opportunity to use the skills that I so love towards a noble goal. That’s one of the reasons I decided to sign up. The Give Camp was held at Microsoft’s Malvern office, where they do mostly sales, in a complex shared with other companies. There’s a fountain in the shared lobby with plenty of parking outside. In the lobby of the office, there were plush couches, along with a Guitar Hero setup. They have small offices across from their primary conference rooms that they call “Chat Rooms.”
Lisa and I went around 11AM that morning but there wasn’t much to do. We helped Dani retrieve Give Camp T-shirts from his car, and list all of the available projects on two large whiteboards. We were the first there (along with Kosal) so Dani Diaz, who organized the event, let us choose a project to work on. We chose to work on an application for Mission for Educating Children with Autism (MECA) which sounded like the most challenging project.
We had lunch at King of Prussia mall while Dani was busy shopping. When we returned, there were several developers already there. We waited for more people to arrive. Soon Trevor came, who I had met recently at Philly ETE and who I knew was a frequent attendee at Philly RB meetings. We decided to work together on the MECA project.
Our meeting with the MECA staff is described in the next post.
Print This Post
Print This Post
Print This Post
Print This Post
Print This Post
Print This Post
