Time constraints mean we’ll be uploading final presentation videos later. Let’s pretend this is an exclusive deal for attendees thing – rather than us just not wanting to sit waiting for uploads to complete when we could be travelling home!
A closer look at the bouncy fitlike.
A quick UI demo of the fitlike app.
A few folk asked for a link to “that other hack in The Hague”.
So here you go –> http://hackunamatata.nl/
You can see that teams are pushing out more code already on Sunday – #moredoinglesstalking
A lot of the themes we are covering this weekend were also touched on during the Northern Lights Conference on Friday. Northern Lights is a tech conference held in Aberdeen each Autumn, and was held just around the corner the day before #ctc2. A large part of the conference is dedicated to open space, where this year 16 sessions were held, all proposed by attendees and speakers at the event. Some of those conversations have directly influenced work this weekend.
Photos from the event are tagged #northlightconf on Flickr
Links to all the speakers are on http://northernlightsconf.co.uk/
We’ll likely have fewer updates through the day today – as most of the teams are keen to put their time into delivery of more prototype iterations – and battling some data dragons.
We’ll do our best to keep you posted without distracting them *too* much.
HOW SUNDAY WORKS AT CODETHECITY
By the end of Sunday you should aim to have the following in place to document your project at Codethecity
- Github repo associated with the codethecity organisation account
- Your code pushed to the repo
- A descriptive README in the root of the repo
The README will ideally contain the following sections:
- TEAM : A list of your team members
- CHALLENGE : A very brief overview of the problem you are tackling
- RESULTS : A screenshot / diagram / photograph of your project, and a brief explanation of what you did
- LINKS : Links to any demos, videos, blog posts etc… about your project for people to find out more. Especially interesting are progress reports, results of any research you have done, lists of similar apps, etc…
If you don’t have any code as such, still create a repo and your report README file. Ask another team for help if you are unsure how to do this. The README doesn’t need to be long and complicated. Take 10 minutes to create a draft, don’t sweat the details. You can always fix things later.
If you have video, text, photos that you would like to post direct to the codethecity tumblr or one of our other channels please just ask.
3PM – Demo your project
By now you should have your README in good shape. Just like the progress updates throughout the day, we’d love to hear what you’ve ended up with. Time limited, we want the headlines of…
- where you started,
- what you did,
- what you learned, and
- what you would do next if you could pick the project up again.
Our view from the room – a much finer morning today – hackers are arriving, loading up on coffee and oj, and discussing their projects.