How principles impact my work, selection of tools and code that I write. This talk is a work-in-progress for me as well, but I believe it is way too easy for us to use new frameworks and tools only for the sake of using them. This talk won't answer all your questions but it may help you look at things in a different way.
44. “Our strategy around recruiting is to find the best
and brightest engineers. We don’t bring them in
specifically because the engineer knows Erlang,”
Jamshid Mahdavi
45. “Our strategy around recruiting is to find the best
and brightest engineers. We don’t bring them in
specifically because the engineer knows Erlang,”
Jamshid Mahdavi
46. “Our strategy around recruiting is to find the best
and brightest engineers. We don’t bring them in
specifically because the engineer knows Erlang,”
Jamshid Mahdavi
87. • Web dev in 2016: https://twitter.com/iamdevloper/status/694198210894520320
• You could be better: https://twitter.com/andrestaltz/status/698958921717964800
• Simple Made Easy by Rich Hickey: http://www.infoq.com/presentations/Simple-Made-Easy
• Beyond Features by Dan North: https://www.youtube.com/watch?v=lz5HBtDl-1A
• Choose Boring Technology by Dan McKinley: http://mcfunley.com/choose-boring-technology
• Law of the Instrument: https://en.wikipedia.org/wiki/Law_of_the_instrument
• http://codeinthedark.com/
• http://standardjs.com/
• XKCD Standards: https://xkcd.com/927/
• You Don’t Know JS by Kyle Simpson: https://github.com/getify/You-Dont-Know-JS
• 8 Lines of Code by Greg Young: http://www.infoq.com/presentations/8-lines-code-refactoring