Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime. SSWC 2013


Published on

"How do we get people to understand programming?
We change programming. We turn it into something that's understandable by people."
– Bret Victor, UX guru from Apple, etc.

Anyone can start writing with a word processor, or draw something with a drawing program. Why should only engineers be able to create software?

Why is programming still synonymous with writing code in a text window, 70 years after the birth of the digital computer?

What would be possible if designers, economists, artists, and others could create software themselves?

Published in: Technology
  • Be the first to comment

  • Be the first to like this SSWC 2013

  1. 1. Programmering für alle! für alle! @ SSWC 2013@tomsoderlund #programmeringfuralle
  2. 2. Varför kan inte alla skapa mjukvara?
  3. 3. Bret Victor
  4. 4. Creator UserUX designer Programmer
  5. 5. – Dan Ingalls (co-creator of Smalltalk), Xerox PARC “If a system is to serve the creative spirit, it must be entirely comprehensible to a single individual.”
  6. 6. Summary •Great ideas get lost in their translation to code. Creators should not have to think like computers. •Ideas also get lost when transferred between people. There is value in having a single person being able to create an application.
  7. 7. Visual Programming
  8. 8. Behavior without Code • Smart components • Linked parameters • Fill-in-the-blanks templates • Step-by-step recording (macros) • Pipes • Natural language input (computerized or human translation) • other?
  9. 9. Smalltalk
  10. 10. Etoys
  11. 11. Scratch and Hopscotch
  12. 12. Visual Basic and Flash
  13. 13. Yahoo Pipes
  14. 14. Lego NXT-G
  15. 15. App Builders
  16. 16. Caspio
  17. 17. and Codiqa
  18. 18. Fliplet and OpenRatio
  19. 19. My ideas (
  20. 20. Who would want this? •Designers (UX, graphics) and artists •Business people (finance, accounting, etc) •Expert system builders •other?
  21. 21. Design Principles •Visual & tangible: see & feel what you create. •Rapid: design, develop, test - simultaneously •Collaborative: design, develop, test - together •Friendly: zero startup time, don’t crash/hang, error informative messages.
  22. 22. So, what does that mean? •Drag-and-drop UI builder. •Smart components, linked parameters. •Develop on your target platform. •Always online, always running. •Never crash, friendly errors. •Web as core platform, export to native apps.
  23. 23. Thank you! •Sign up for newsletter: •People/co-founders needed (tech, design)! •Contact:, @tomsoderlund
  24. 24. Simplifying the problem •Narrowing the target group. •Encapsulating functionality in smart components.