Designer and technologist Tom Armitage argues that learning to write computer code means learning to think in a modern way, and that it should spur creativity: the possibility of doing entirely new things.
Tagged with “code” (5)
Seb is known for large scale installations and events that bring people together using technology, like his interactive digital fireworks, glowstick voting, and PixelPhones - a system that connects all the smart phones together, turning each member of the audience into a single pixel of a huge pulsating display.
Hardware and software is evolving so fast that creative coders can barely keep up, and we’ve just scratched the surface of what depth sensors, projectors and smart phones are capable of.
In this down to earth session, Seb will explore how technology can create huge interactive playful events and encourage a sense of community rather than everyone having a private experience with their own screens.
Lest you think that Seb dabbles only in the realm of pixels, he has been known to use the physical world as his canvas too, making digital fireworks and projections with Processing.
The driving force behind modern computers, Alan Turing was born a hundred years ago. He launched the digital age, founded the fields of computer science and artificial intelligence, and helped the British win WWII by cracking the Nazi "Enigma" codes. He was persecuted by British authorities for the crime of being homosexual, and committed suicide at age 41. His life ended tragically, but his brilliance lives in the computers we use every day. We celebrate the Alan Turing Year.
Timothy Fitz believes that it is best to use the concept of Continuous Deployment in software development. He thinks that by deploying small changes constantly, problems will appear quicker and can be solved more easily. He joins Phil and Scott to discuss the topic and how he is using it in the real world.
In addition, he also talks about the concept of Lean Startup and how it relates to Continuous Deployment. He cites a number of examples of the two ideas and discusses related work being done by others.
In our discussion, Nathan and I first defined design pattern libraries and component libraries. A pattern library is a repository for ideas and solutions to design interaction problems. Component libraries are comprised of actual functioning parts with real code. An example would be a log-in process. Your pattern would define the experience of logging into your application, from the interaction, and often visual standpoint. Your component would be the chunk of code that represents the set of fields and controls that can be replicated across your organization’s web properties, so that you can easily create a consistent experience for your users, no matter where they may enter your system.