Readability Counts

Readability Counts



April 26, 2012


  1. Readability Counts and/or Things that annoy me about JS @thattommyhall

  2. About me • mathmo by training • sysadmin historically, •

    devops@forward, • long time pythonista, • quite recent rubyist, • newer javascripter, • coffeescript convert
  3. ==

  4. _.isEqual

  5. ASI

  6. clever is not a compliment

  7. From twitter bootstrap clearMenus() !isActive && $parent.toggleClass('open')

  8. Why not this? if(!isActive) { $parent.toggleClass('open'); }

  9. What does this do? var fun1 = function() { return

    42 } var fun2 = function() { return 'something' } var stuff = ['apples' , 'pears' , 'oranges'] -1 == fun1() || fun2() console.log(stuff)
  10. 'used by those tall enough to ride'

  11. Why NPM Style?

  12. None
  13. None
  14. None
  15. Beautiful is better than ugly. Explicit is better than implicit.

    Simple is better than complex. Complex is better than complicated. Flat is better than nested. Sparse is better than dense. Readability counts. Special cases aren't special enough to break the rules. Although practicality beats purity. Errors should never pass silently. Unless explicitly silenced. In the face of ambiguity, refuse the temptation to guess. There should be one-- and preferably only one --obvious way to do it. Although that way may not be obvious at first unless you're Dutch. Now is better than never. Although never is often better than *right* now. If the implementation is hard to explain, it's a bad idea. If the implementation is easy to explain, it may be a good idea. Namespaces are one honking great idea -- let's do more of those!
  16. Links • • • • • • • xml#Semicolons • • •