TXJS 2013 in 10 minutes

44
TXJS 2013 in 10 minutes As seen by Eugene Lazutkin 1

description

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

Transcript of TXJS 2013 in 10 minutes

Page 1: TXJS 2013 in 10 minutes

TXJS 2013 in 10 minutes

As seen by Eugene Lazutkin

1

Page 2: TXJS 2013 in 10 minutes

TXJS 2013 venue Paramount theatre

2

Page 3: TXJS 2013 in 10 minutes

TXJS 2013 Really early in the morning...

3

Page 4: TXJS 2013 in 10 minutes

Keynote Harper Reed

4

Page 5: TXJS 2013 in 10 minutes

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

Page 6: TXJS 2013 in 10 minutes

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

Page 7: TXJS 2013 in 10 minutes

Harper Reed

• The movie Groundhog Day is really just about multivariate A/B testing.

7

Page 8: TXJS 2013 in 10 minutes

TXJS 2013 HTML5 / CSS3 section

8

Page 9: TXJS 2013 in 10 minutes

HTML: do we really need L? Dave Rupert

9

Page 10: TXJS 2013 in 10 minutes

Dave Rupert

• New "home base":

• Tiny screen,

• Slow connection,

• Touch (fat fingers)

10

Page 11: TXJS 2013 in 10 minutes

Touch screens are everywhere, except on the one platform almost all web devs use.

11

Page 12: TXJS 2013 in 10 minutes

OOCSS and Preprocessor in a tree Nicole Sullivan

12

Page 13: TXJS 2013 in 10 minutes

Nicole Sullivan

• SASS and OOCSS

• Suggests constantly checking the output of CSS processors to control the quality.

13

Page 14: TXJS 2013 in 10 minutes

Nicole Sullivan

• The Inception rule of CSS:

• Never go more than three levels deep.

14

Page 15: TXJS 2013 in 10 minutes

CSS is for Computers Chris Coyier

15

Page 16: TXJS 2013 in 10 minutes

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

Page 17: TXJS 2013 in 10 minutes

TXJS 2013 Web applications section

17

Page 18: TXJS 2013 in 10 minutes

Beyond Front-end Developer Trek Glowacki

18

Page 19: TXJS 2013 in 10 minutes

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

Page 20: TXJS 2013 in 10 minutes

Apps that Build Themselves Rebecca Murphey

20

Page 21: TXJS 2013 in 10 minutes

Rebecca Murphey

• Discussed modern configuration-driven apps.

• Example: Octopress

• Used Firebird by bazaarvoice.com for the rest of the talk.

21

Page 22: TXJS 2013 in 10 minutes

Rebecca Murphey

• "For efficiency we don't create HTML with DOM, just shove in HTML snippets, then use classes to plug in behaviors."

22

Page 23: TXJS 2013 in 10 minutes

Rebecca Murphey

• "For loose coupling we use an app-wide global message bus."

• Message bus + Config = App (in ideal world)

23

Page 24: TXJS 2013 in 10 minutes

Culture change for creating better UX Frances Barriman

24

Page 25: TXJS 2013 in 10 minutes

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

Page 26: TXJS 2013 in 10 minutes

TXJS 2013 node.js section

26

Page 27: TXJS 2013 in 10 minutes

Faking Browsers for FFUU and Profit Jed Schmidt

27

Page 28: TXJS 2013 in 10 minutes

Jed Schmidt

• Discussed server-side tools to parse HTML, and work with web sites in general (scraping, testing, snapshotting, inspecting).

• PhantomJS

28

Page 29: TXJS 2013 in 10 minutes

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

Page 30: TXJS 2013 in 10 minutes

The Evolution of Node Isaac Schlueter

30

Page 31: TXJS 2013 in 10 minutes

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

Page 32: TXJS 2013 in 10 minutes

Isaac Schlueter

• Node is pretty stable, the core boundaries are set, 1.0 will be similar to what we have.

32

Page 33: TXJS 2013 in 10 minutes

Streeeams, probably Marco Rogers

33

Page 34: TXJS 2013 in 10 minutes

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

Page 35: TXJS 2013 in 10 minutes

TXJS 2013 Rethink.js section

35

Page 36: TXJS 2013 in 10 minutes

All Open Source Everything Charlie Robbins

36

Page 37: TXJS 2013 in 10 minutes

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

Page 38: TXJS 2013 in 10 minutes

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

Page 39: TXJS 2013 in 10 minutes

Execute Drew Wilson

39

Page 40: TXJS 2013 in 10 minutes

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

Page 41: TXJS 2013 in 10 minutes

Drew Wilson

• Design to delight.

• He likes to build for himself - no research.

• Build the smallest possible version to communicate your ideas.

41

Page 42: TXJS 2013 in 10 minutes

I can smell your CMS Phil Hawksworth

42

Page 43: TXJS 2013 in 10 minutes

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

Page 44: TXJS 2013 in 10 minutes

TXJS 2013 And it ends...

44