Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Growing Ember, One Tomster at a Time

Growing Ember, One Tomster at a Time

From EmberConf 2015

Bbbcbbdc9e73179d5e86a6244459ec4f?s=128

Jamie White

March 05, 2015
Tweet

Transcript

  1. hello

  2. @jgwhite

  3. With Associates http://withassociates.com

  4. http://emberlondon.com

  5. Ember London is… Over 600 meetup.com members 2 events per

    month 42 talks recorded 11.4K plays
  6. Ember London ❤️’s… Our speakers SapientNitro Wingman Events 54B

  7. None
  8. None
  9. None
  10. None
  11. None
  12. None
  13. None
  14. None
  15. None
  16. None
  17. None
  18. Growing Ember,
 One Tomster at a Time

  19. design and engineering

  20. 1. tomster 2. language 3. user interface 4. hackability 5.

    roles
  21. 1.

  22. None
  23. None
  24. None
  25. None
  26. None
  27. None
  28. None
  29. None
  30. None
  31. None
  32. good defaults

  33. – Leah Silber “If you have a brand and/or a

    mascot that correctly emotes something specific, it makes it easier for the people in the leadership roles to then actually meet those ideals.”
  34. composing concepts

  35. – Leah Silber “Our tagline is ‘The framework for ambitious

    apps’ and it’s actually really hard to juxtapose friendliness and ambition next to each other. They’re not two things that you would normally package up.”
  36. None
  37. None
  38. hackability

  39. – Lindsey Wilson “When you create characters… you pick things

    that are iconic but also adaptable.
 
 Tomster wasn’t overly done and he could embody what a developer is. He doesn’t have a lot of distinct features but just enough to say: okay, this is for me.”
  40. None
  41. 2. language

  42. – Tom Dale “When you’re operating at the edge of

    something oftentimes one of the biggest hindrances to making progress is not having a shared vocabulary. 
 We like to help ourselves frame our thinking
 by trying to coin terminology.”
  43. None
  44. “stability without stagnation”

  45. “data down, actions up”

  46. “functionally diverse core team”

  47. “glimmer”

  48. None
  49. None
  50. None
  51. None
  52. BYOP (Bring Your Own Project) Project Nights are all about

    jumping in, getting help and giving back. Be that working on an upstream change to Ember itself or a side project using Ember. The sessions are informal, friendly and agenda-less.
  53. documentation

  54. “Documentation, at a very high level, is essentially defining public

    API. There have been several cases where attempts to document either Ember or related libraries have turned into public API changes”
  55. – Trek Glowacki “If something’s difficult to explain, it probably

    means we’re exposing the wrong primitives.”
  56. 3. user interface

  57. None
  58. None
  59. None
  60. None
  61. None
  62. None
  63. – Yukihiro Matsumoto “Programmers often feel joy when they can

    concentrate on the creative side of programming, so Ruby is designed to make programmers happy. I consider a programming language as a user interface, so it should follow the principles of user interface.”
  64. None
  65. None
  66. sandraor:master (#1904) emberjs/website:master yaymukund:meetups-dot-js (#1) wifelette:patch-3 (#5) andrewbranch:master (#6) lzcabrera:master

    (#7) alexclarkofficial:master (#9) solsberg:rake_geocode (#10) lzcabrera:rake_findorganizers (#11) solsberg:rake_geocode (#12) lzcabrera:meetup-list (#13) jgwhite:new-community-pages-top-nav-tweak (#14) wifelette:final-tweaks (#15)
  67. – Kasper Tidemann “I’ve come to find that having a

    solid visual base of operations is sometimes more important than having code that’s perfect.”
  68. 4. hackability

  69. – Stefan Penner “[An open project] has that mud on

    the floor from the construction workers; you don’t mind walking in again with your boots on. It has to feel hackable, parts have to be accessible.”
  70. – Yehuda Katz “It’s really important that the feeling you

    get when you’re an active contributor is pretty close to the feeling of being a core contributor, minus the cases where an executive decision has to be made.”
  71. – Alex Matchneer “Ember has a philosophy that there’s nothing

    really set about the technology today. It’s more the idea that there should be conventions around these problems we’re solving every day.”
  72. – Lindsey Wilson “When you create characters… you pick things

    that are iconic but also adaptable.
 
 Tomster wasn’t overly done and he could embody what a developer is. He doesn’t have a lot of distinct features but just enough to say: okay, this is for me.”
  73. 5. roles

  74. creator benevolent dictator early adopter bug reporter bug fixer documenteer

    designer blogger author podcaster mentor student feature proposer feature author
  75. event organiser speaker attendee sponsor swag creator swag consumer aggregator

    curator follower diplomat explorer evangelist critic antagonist
  76. documenteer

  77. mentor

  78. student

  79. explorer

  80. critic

  81. critic

  82. critic

  83. None
  84. None
  85. in conclusion…

  86. 1. tomster 2. language 3. user interface 4. hackability 5.

    roles
  87. – Trek Glowacki “The value of a framework is not

    the source code at all. The value is really the patterns and the understanding that people got working through what the problems were.”
  88. the code is a snapshot
 of the best ideas in

    our community at given point in time
  89. a home for good ideas

  90. thanks!

  91. ❤️ Leah Silber Yehuda Katz Trek Glowacki Adolfo Builes Alex

    Matchneer Brian Cardarella DeVaris Brown Erik Bryn Giovanni Collazo Igor Terzic Kait Olson Kasper Tidemann Lindsey Wilson Tom Dale Stefan Penner Robert Jackson Matt Beale Luke Melia Peter Wagnet Taras Mankovski Owain Williams Drew Neil Tom Stuart Laura Navas de Maya
  92. None
  93. http://peertopeer.io/h/jwdn/ use coupon ‘emberconf’ for ⅓ off

  94. None
  95. meetup organisers
 meet-and-greet