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.

Small, simple and smelly: What we can learn from examining end-user artifacts?

594 views

Published on

We are close to a future in which everyone can and will program. Whether it is some Javascript, some R or an extensive spreadsheet, programming happens everywhere. What do end-users do in the wild? And what can we learn from that as programming language designers?

In this talk Felienne will summarize her research on the topic of end-user testing, error finding and refactoring, as well as presenting a sneak peek into the future of her research as Delft University.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Small, simple and smelly: What we can learn from examining end-user artifacts?

  1. 1. Small, Simple & Smelly: What we can learn from examining end-user artifacts?
  2. 2. Ehm? DSLs and End-Users?
  3. 3. Ehm? DSLs and End-Users?
  4. 4. Ehm? DSLs and End-Users?
  5. 5. “In the future, everyone will be a programmer for 15 minutes”
  6. 6. Internet
  7. 7. The web
  8. 8. YouTube
  9. 9. “In the future, everyone will be a programmer for 15 minutes”
  10. 10. was 44% 10 years ago
  11. 11. Spreadsheets are code
  12. 12. Spreadsheets live 5 years on average
  13. 13. Are used by 12 different people
  14. 14. Spreadsheets are code Similar activities, power and problems
  15. 15. How to help everyone?
  16. 16. “Long method”
  17. 17. “Too many parameters”
  18. 18. 42% of spreadsheets have smells Detecting and Refactoring Code Smells in Spreadsheet Formulas, Herman Empirical Software Engineering, 2014
  19. 19. What are the tools needed to make this prediction true? Maybe smell detection is a good tool....?
  20. 20. The Scratch programming language
  21. 21. The Scratch programming language
  22. 22. Scripts
  23. 23. Each sprite can have scripts
  24. 24. One ‘good’ version
  25. 25. Two ‘smelly’ versions
  26. 26. Two ‘smelly’ versions Long method Duplicated code
  27. 27. Version N
  28. 28. Version D
  29. 29. Version D
  30. 30. Version D
  31. 31. Version D
  32. 32. Version D
  33. 33. Version D
  34. 34. Version N
  35. 35. Version N
  36. 36. Version L
  37. 37. Do code smells matter to kids?
  38. 38. tl;dr Yes
  39. 39. tl;dr Yes Kids performed significantly better on the non-smelly program
  40. 40. tl;dr Yes But, differences tasks are impacted differently
  41. 41. Let’s take a closer look!
  42. 42. Version N “When have you won the game?”
  43. 43. Version L “When have you won the game?”
  44. 44. Let’s take a closer look!
  45. 45. Version N “Make the game go to 10 points”
  46. 46. Version N “Make the game go to 10 points”
  47. 47. Version D
  48. 48. Version D
  49. 49. Version D
  50. 50. Let’s take a closer look!
  51. 51. Are smells common?
  52. 52. How do kids code in Scratch?
  53. 53. Available on GitHub! https://github.com/TUDelftScratchLab/ScratchDataset
  54. 54. How do kids code in Scratch?
  55. 55. 1 2 3 4
  56. 56. 3 1 2 4
  57. 57. 3 1 2 4 24 % 1% 8% 24 %
  58. 58. 3 1 2 4 24 % 1% 8% 24 % Any: 28% of the projects
  59. 59. Now what?
  60. 60. Educate!
  61. 61. Education is possible!
  62. 62. 0 50 100 150 200 250 300 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 Numberofstudents Age
  63. 63. What kids thought they learned
  64. 64. What they really learned
  65. 65. *Paper Under Review
  66. 66. *http://journals.plos.org/plosone/article?id=10.1371/journal.pone.0141357 Meet Dr. Pigeon
  67. 67. *http://journals.plos.org/plosone/article?id=10.1371/journal.pone.0141357 Meet Dr. Pigeon
  68. 68. *http://journals.plos.org/plosone/article?id=10.1371/journal.pone.0141357 Meet Dr. Pigeon 75% correct after 2 weeks
  69. 69. Sparrow Decks
  70. 70. Sparrow Decks
  71. 71. Now: • Q&A Then: • Hands on!! “In the future, everyone will be a programmer for 15 minutes”
  72. 72. More info? • www.felienne.com • github.com/TUDelftScratchLab Want to connect? • mail@felienne.com “In the future, everyone will be a programmer for 15 minutes”
  73. 73. What are the tools needed to make this prediction true?
  74. 74. What are the tools needed to make this prediction true?

×