TXJS 2013 in 10 minutes

336
-1

Published on

TXJS 2013 as seen by me presented at ClubAjax (Dallas, TX).

Published in: Technology, Design
1 Comment
0 Likes
Statistics
Notes
  • Be the first to like this

No Downloads
Views
Total Views
336
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
2
Comments
1
Likes
0
Embeds 0
No embeds

No notes for slide

TXJS 2013 in 10 minutes

  1. 1. TXJS 2013 in 10 minutes As seen by Eugene Lazutkin 1
  2. 2. TXJS 2013 venue Paramount theatre 2
  3. 3. TXJS 2013 Really early in the morning... 3
  4. 4. Keynote Harper Reed 4
  5. 5. Harper Reed • CTO at Threadless • CTO of Obama for America • Obama 2012 hired engineers to do engineering • a B$ op, 18 months, web scale, from zero, 1000s servers, ~290 products. 5
  6. 6. Harper Reed • Manage by outbox, not inbox. • Build great team, practice failure, facilitate community. • The AWS rule: if Netflix down, you are down too, if Netflix is up, but you are down - you are screwed. 6
  7. 7. Harper Reed • The movie Groundhog Day is really just about multivariate A/ B testing. 7
  8. 8. TXJS 2013 HTML5 / CSS3 section 8
  9. 9. HTML: do we really need L? Dave Rupert 9
  10. 10. Dave Rupert • New "home base": • Tiny screen, • Slow connection, • Touch (fat fingers) 10
  11. 11. Touch screens are everywhere, except on the one platform almost all web devs use. 11
  12. 12. OOCSS and Preprocessor in a tree Nicole Sullivan 12
  13. 13. Nicole Sullivan • SASS and OOCSS • Suggests constantly checking the output of CSS processors to control the quality. 13
  14. 14. Nicole Sullivan • The Inception rule of CSS: • Never go more than three levels deep. 14
  15. 15. CSS is for Computers Chris Coyier 15
  16. 16. Chris Coyier • All the web is just a layer of abstractions. • SASS is just one layer higher than CSS. • CSS is for computers, write SASS. 16
  17. 17. TXJS 2013 Web applications section 17
  18. 18. Beyond Front-end Developer Trek Glowacki 18
  19. 19. Trek Glowacki • Gave a historic overview of presenting content. • Skip Photoshop. It doesn’t present your medium. • Designers should know JS. • "How to add two numbers in JS? - I think there is a jQ plugin for that!" 19
  20. 20. Apps that Build Themselves Rebecca Murphey 20
  21. 21. Rebecca Murphey • Discussed modern configuration-driven apps. • Example: Octopress • Used Firebird by bazaarvoice.com for the rest of the talk. 21
  22. 22. Rebecca Murphey • "For efficiency we don't create HTML with DOM, just shove in HTML snippets, then use classes to plug in behaviors." 22
  23. 23. Rebecca Murphey • "For loose coupling we use an app-wide global message bus." • Message bus + Config = App (in ideal world) 23
  24. 24. Culture change for creating better UX Frances Barriman 24
  25. 25. Frances Barriman • Building web apps requires radical changes in culture. • Principle #8: build services, not apps. • Be clear in your goals: users come first. 25
  26. 26. TXJS 2013 node.js section 26
  27. 27. Faking Browsers for FFUU and Profit Jed Schmidt 27
  28. 28. Jed Schmidt • Discussed server-side tools to parse HTML, and work with web sites in general (scraping, testing, snapshotting, inspecting). • PhantomJS 28
  29. 29. Jed Schmidt • Single-page apps do not lent themselves for crawlability and SEO. • Google has defined (and Bing adopted) #! convention to retrieve snippets via _escaped_fragment_ parameter. 29
  30. 30. The Evolution of Node Isaac Schlueter 30
  31. 31. Isaac Schlueter • Slowness is a bug. • "Errors must be handled" not ignored, the system should enforce this paradigm. • callback => EventEmitter => stream. • When you grok event stream, you grok node.js. • Like Unix - assemble rather than invent. 31
  32. 32. Isaac Schlueter • Node is pretty stable, the core boundaries are set, 1.0 will be similar to what we have. 32
  33. 33. Streeeams, probably Marco Rogers 33
  34. 34. Marco Rogers • Node streams are modeled on Unix piping, it is an async way to deal with streaming. • Streaming/piping leads to smaller code, and less buffer memory. • Base classes - readable/ writeable, transform, duplex, passthrough streams. 34
  35. 35. TXJS 2013 Rethink.js section 35
  36. 36. All Open Source Everything Charlie Robbins 36
  37. 37. Charlie Robbins • CEO at Nodejitsu • Thinks that 3D printing is the next big thing after the internet, and it will grow much faster. • Attribution - how to do it correctly? There is no law for that (yet). • Talks about open source and legal issues, which are forced by open source crossing into physical world (like 3D printing) 37
  38. 38. Charlie Robbins • When ideas (design, soft) are free, only raw materials matter - do we marginalize ourselves? • Soft is either free or not, no "enterprise version". • Not everything can be/ should be open sourced, or eventually you'll be a slave to raw material owners. 38
  39. 39. Execute Drew Wilson 39
  40. 40. Drew Wilson • “Execute” the book is written in 3 days, printed in 8. • Build when inspired. • Launch the simplest possible version, than improve - it is never finished. • A project should be validated; launch to validate. 40
  41. 41. Drew Wilson • Design to delight. • He likes to build for himself - no research. • Build the smallest possible version to communicate your ideas. 41
  42. 42. I can smell your CMS Phil Hawksworth 42
  43. 43. Phil Hawksworth • Url design is a craft, CMS and your technology should not dictate them. • Frequently CMS bleeds into a web site: urls, UI hooks, admin stuff, and so on • WYSIWYG is frequently WYSIWTF 43
  44. 44. TXJS 2013 And it ends... 44
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×