TXJS 2013 in 10 minutes As seen by Eugene Lazutkin 1
Jan 21, 2015
TXJS 2013 in 10 minutes
As seen by Eugene Lazutkin
1
TXJS 2013 venue Paramount theatre
2
TXJS 2013 Really early in the morning...
3
Keynote Harper Reed
4
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
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
Harper Reed
• The movie Groundhog Day is really just about multivariate A/B testing.
7
TXJS 2013 HTML5 / CSS3 section
8
HTML: do we really need L? Dave Rupert
9
Dave Rupert
• New "home base":
• Tiny screen,
• Slow connection,
• Touch (fat fingers)
10
Touch screens are everywhere, except on the one platform almost all web devs use.
11
OOCSS and Preprocessor in a tree Nicole Sullivan
12
Nicole Sullivan
• SASS and OOCSS
• Suggests constantly checking the output of CSS processors to control the quality.
13
Nicole Sullivan
• The Inception rule of CSS:
• Never go more than three levels deep.
14
CSS is for Computers Chris Coyier
15
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
TXJS 2013 Web applications section
17
Beyond Front-end Developer Trek Glowacki
18
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
Apps that Build Themselves Rebecca Murphey
20
Rebecca Murphey
• Discussed modern configuration-driven apps.
• Example: Octopress
• Used Firebird by bazaarvoice.com for the rest of the talk.
21
Rebecca Murphey
• "For efficiency we don't create HTML with DOM, just shove in HTML snippets, then use classes to plug in behaviors."
22
Rebecca Murphey
• "For loose coupling we use an app-wide global message bus."
• Message bus + Config = App (in ideal world)
23
Culture change for creating better UX Frances Barriman
24
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
TXJS 2013 node.js section
26
Faking Browsers for FFUU and Profit Jed Schmidt
27
Jed Schmidt
• Discussed server-side tools to parse HTML, and work with web sites in general (scraping, testing, snapshotting, inspecting).
• PhantomJS
28
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
The Evolution of Node Isaac Schlueter
30
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
Isaac Schlueter
• Node is pretty stable, the core boundaries are set, 1.0 will be similar to what we have.
32
Streeeams, probably Marco Rogers
33
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
TXJS 2013 Rethink.js section
35
All Open Source Everything Charlie Robbins
36
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
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
Execute Drew Wilson
39
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
Drew Wilson
• Design to delight.
• He likes to build for himself - no research.
• Build the smallest possible version to communicate your ideas.
41
I can smell your CMS Phil Hawksworth
42
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
TXJS 2013 And it ends...
44