O slideshow foi denunciado.
Utilizamos seu perfil e dados de atividades no LinkedIn para personalizar e exibir anúncios mais relevantes. Altere suas preferências de anúncios quando desejar.
Five ways to be a happier JavaScript developer
Chris Heilmann (@codepo8) Feburary 2018
tar -cvzf here.tar.gz thisone
christianheilmann.com/2017/12/05/so-you-learned-javascript-what-now/
ways to be a
happier
JavaScript
developer
ways to be a
happier
JavaScript
developer
▪ Concentrating on the now
▪ Limiting our development
environment
▪ Making it ha...
Concentrating on
the now…
Worries of the past
shouldn’t prevent
us from creating…
Focusing exclusively
on the next cool
thing is as stifling
and depressing
developer.mozilla.org/en-US
caniuse.com
Limiting our
development
environment
The web development trinity
BrowserTerminalEditor
▪ Where we code
▪ Where we tweak themes
▪ Where we mix spaces and
tabs –...
That is a lot of
duplication and
multiplication
with choice
Tooling is starting
to overtake that
historically grown
trinity.
Good editors
consolidate
features to avoid
context switching.
VS Code (@code)
code.visualstudio.com
▪ Open Source, Cross-platform
▪ Hundreds of extensions
▪ Highly theme-able
▪ Built-i...
smashingmagazine.com/2018/01/visual-studio-code
vscodecandothat.com
Instead of using
your own
machine, why not
try online before?
glitch.com
jsbin.com
codepen.io
Making it harder to
write bad code.
Applying a
stricter ruleset
pre-empts
mistakes
Linting > Debugging
code.visualstudio.com
▪ Find mistakes while you make them
▪ Based on the experience and
consensus of m...
Overall, I give linting
high marks
Moving from
knowing .*
to
learning by
making mistakes
Auditing
▪ Audit your work before you go live
▪ Learn from explanations of why
these are mistakes
▪ Keep iterating until i...
Linting and
validation tools can
be part of your
release process.
sonarwhal.com
Getting to know our
tooling
It is true that our
tools have become
much more complex.
Knowing them gives
you superpowers
and insights how to
build great solutions
Step one is to stop using
console.log() and use
breakpoints instead.
code.visualstudio.com/Docs/editor/debugging
smashingm...
Giving back to
others
Not everybody
cares about the nuts
and bolts and has
endless time to
invest
twitter.com/headjs_ru/status/955333399564161024
My plea to you:
Be the person you’d like to
meet. Be kind, be supportive,
and avoid unnecessary
drama.
Thanks!
Chris Heilmann
@codepo8
Terminal photo by Terminal 5 Insider
Editor photo by John Oxley Library
Browser photo by J...
Próximos SlideShares
Carregando em…5
×

Five ways to be a happier JavaScript developer

A ten minute reminder for the SmashingConf London 2018 Jam Session

  • Seja o primeiro a comentar

Five ways to be a happier JavaScript developer

  1. 1. Five ways to be a happier JavaScript developer Chris Heilmann (@codepo8) Feburary 2018
  2. 2. tar -cvzf here.tar.gz thisone christianheilmann.com/2017/12/05/so-you-learned-javascript-what-now/
  3. 3. ways to be a happier JavaScript developer
  4. 4. ways to be a happier JavaScript developer ▪ Concentrating on the now ▪ Limiting our development environment ▪ Making it harder to write bad code ▪ Getting to know our tooling ▪ Giving back to others
  5. 5. Concentrating on the now…
  6. 6. Worries of the past shouldn’t prevent us from creating…
  7. 7. Focusing exclusively on the next cool thing is as stifling and depressing
  8. 8. developer.mozilla.org/en-US
  9. 9. caniuse.com
  10. 10. Limiting our development environment
  11. 11. The web development trinity BrowserTerminalEditor ▪ Where we code ▪ Where we tweak themes ▪ Where we mix spaces and tabs – like animals ▪ Where we do version control ▪ Where we run build tasks ▪ Where we deploy ▪ Where we tweak themes ▪ Where we assume everyone runs OSX ▪ Where we debug ▪ Where we check and tweak visual output ▪ Where we audit ▪ Where we annoy the end user with odd log messages.
  12. 12. That is a lot of duplication and multiplication with choice
  13. 13. Tooling is starting to overtake that historically grown trinity.
  14. 14. Good editors consolidate features to avoid context switching.
  15. 15. VS Code (@code) code.visualstudio.com ▪ Open Source, Cross-platform ▪ Hundreds of extensions ▪ Highly theme-able ▪ Built-in source control support ▪ Built-in terminal ▪ Integrates into build processes ▪ Written and extensible in TypeScript ▪ Straightens and lightens teeth with repeat use ▪ Possibly is good against hair loss ▪ Gluten free, macrobiotic
  16. 16. smashingmagazine.com/2018/01/visual-studio-code vscodecandothat.com
  17. 17. Instead of using your own machine, why not try online before? glitch.com jsbin.com codepen.io
  18. 18. Making it harder to write bad code.
  19. 19. Applying a stricter ruleset pre-empts mistakes
  20. 20. Linting > Debugging code.visualstudio.com ▪ Find mistakes while you make them ▪ Based on the experience and consensus of many others ▪ Learn from explanations of linting results ▪ Install and configure, or use in-built linting.
  21. 21. Overall, I give linting high marks
  22. 22. Moving from knowing .* to learning by making mistakes
  23. 23. Auditing ▪ Audit your work before you go live ▪ Learn from explanations of why these are mistakes ▪ Keep iterating until it becomes second nature.
  24. 24. Linting and validation tools can be part of your release process. sonarwhal.com
  25. 25. Getting to know our tooling
  26. 26. It is true that our tools have become much more complex.
  27. 27. Knowing them gives you superpowers and insights how to build great solutions
  28. 28. Step one is to stop using console.log() and use breakpoints instead. code.visualstudio.com/Docs/editor/debugging smashingmagazine.com/2018/02/javascript-firefox-debugger/
  29. 29. Giving back to others
  30. 30. Not everybody cares about the nuts and bolts and has endless time to invest twitter.com/headjs_ru/status/955333399564161024
  31. 31. My plea to you: Be the person you’d like to meet. Be kind, be supportive, and avoid unnecessary drama.
  32. 32. Thanks! Chris Heilmann @codepo8 Terminal photo by Terminal 5 Insider Editor photo by John Oxley Library Browser photo by Joseph Brent

×