Please log in to watch this conference skillscast.
The Scenario: You have thirteen weeks to build a prototype login system for businesses to use government services. The code will be thrown away afterward, but it must be able to evolve rapidly in response to feedback about what a user journey should look like. Half your team have never used Clojure or Emacs before. How do you convince the government that building a prototype in Clojure is a good idea? And if you manage that, how do you ensure the prototype is successful?
Clojure offers fast feedback and the ease of spinning up simple web services. It let us adapt quickly and explore complex flows of data. Our talk will be about how we got on, things we learnt, and what we'd do differently next time.
YOU MAY ALSO LIKE:
Clojure in the service of Her Majesty's Government
Rachel is a developer at ThoughtWorks and functional programming newbie.
Philip Potter is a Web Operations Engineer for the Government Digital Service. He was a member of the infrastructure team that built GOV.UK, the website of the British Government.