SOMEJAM: Mistä Apua Nuorelle Nyt?

DSC_4195
Youth activity center Happi where the event was held on the left.
DSC_4071
Various projects that participants were pitching to be developed

 

For SomeJam, I joined a project that wanted to unify various online youth services. There are many different support groups and person-to-person chats provided by different charities. It can be confusing for a young person to track all these different services each with their own opening hours. Our team consisted of two youth service workers, myself, and another software developer, who was not a student at Helsinki University.

After brainstorming for a few hours, we came to the conclusion that persuading all the different organizations to adopt new software would probably not work. Thus, we felt it wiser to provide our own portal service, that displays the currently open support discussions at a glance. A worker on behalf of the portal service would monitor the schedules of the various services and maintain the information on the site.

Once the project had been defined, it was quite straightforward to implement the site. Our second software developer had other work to attend to, so for the first half of saturdayI didn’t need to worry about development environments and other details of group software development. I quickly hacked together a JQuery/JavaScript frontend that used a static JSON file as a data source. The data source listed the events, grouped in personal and group events, and contained the links and opening hours of the event. This was organized by the front-end and displayed to the user.

Later in the afternoon saturday, the other software developer joined, and started work on integration with a calendar service. He had previous experience with Google App Engine, and so chose that as the platform. Using the Google Calendar API, he created a parser that parsed the events on the current day to the same kind of format I had used on my front-end. The parts fit together neatly, and we had a working prototype by sunday.

 

DSC_4106
Development environment
DSC_4145
Another team at work

DSC_4294

 

Thoughts for future SomeJams

Thoroughly discussing the problem paid off, since the original problem setting was not something that we could have feasibly answered in the given 48h constraint.

By focusing our efforts into a small and obvious problem, our product has a good chance of becoming a real service. The feeling that we can actually build something for the betterment of society was an invaluable source of motivation for the team.

 

Leave a Reply

Your email address will not be published. Required fields are marked *