Everything else was just leading to this. Our goal is for you to leave the class with a clear idea of how to approach your app, the tools that will help you get there, and the beginning of the actual application. Armed with these things, you have a high chance of success.

We'll take one or two days to plan and start on a project of your choice. You can choose to work on your own or — better still — in pairs. The goal is to have a working prototype of your app by the end of the day. We'll help each other to imagine audacious projects, and give help and advice for continuing the projects after the course is over.

Here are some examples of projects you could take on:

• Building a web service to characterize well logs.
• Design a web app to make polarity cartoons.
• Making a service to compute seismic attributes on traces.
• Building a tool to interpret well UWIs as spatial data.
• Providing a way for people to get a 'seismic data quality' score for a dataset.
• Making a decompaction calculator for well logs.

The list is endless!

Check out the short video from our 2017 Paris hackathon to see what we get up to.

Ready to give it a try? Get in touch!

Format

• Find projects of interest
• Filter down to the best projects
• Form pairs or teams 
• Find relevant data to work with
• Find useful tools and libraries
• Start coding towards a solution
• Code for 6 to 12 hours
• Prepare a short demo
• Share demos with the class
• Share feedback

Why do this?

Focusing on projects of business interest is a great way to find the motivation to continue working on the craft of coding. It also generates ideas, and perhaps even solutions, that are interesting to the business.

Social coding environments also promote skill sharing and mutual support, and build a culture of collaboration.

With a good skill base, a short hackathon gives the biggest bang for your training buck!