Best practices

Best practices

Should we trust "best practices"? A take on dogmatism in the development industry.

37500337ba5d2aebc962959ed83928e5?s=128

Matthias Le Brun

February 27, 2019
Tweet

Transcript

  1. Hello

  2. None
  3. Is there a great divide?

  4. styling data a11y perf

  5. Different jobs ?

  6. styling data a11y perf Every company has its own definition

  7. JS-JS-JS vs HTML-CSS-JS

  8. Different belief system

  9. Best practices

  10. Separation of concerns

  11. SEPARATION OF CONCERNS Is the separation worth it now ?

  12. SEPARATION OF CONCERNS CSS-in-JS

  13. SEPARATION OF CONCERNS

  14. SEPARATION OF CONCERNS

  15. SPAs

  16. Semantic tags

  17. ARIA

  18. DRY

  19. KISS

  20. a.map(f).map(g) vs a.map(x !=> g(f(x)) KISS

  21. YAGNI

  22. Don't reinvent the wheel

  23. DON'T REINVENT THE WHEEL Reinventing isn't bad

  24. YAGNI Owning your code can be good

  25. Organise your files this way Make smart and dumb components

    Use redux with ducks Write tests first You must respect HTTP verbs Premature optimisation is root the root of all evil …
  26. And there's some truth to all of them

  27. but …

  28. they are not necessarily accurate for your context

  29. Your postulate might be different

  30. Reassess over time

  31. Best doesn't mean forever

  32. Best doesn't mean forever

  33. None
  34. Thank you

  35. Matthias Le Brun @bloodyowl Questions ?