Înapoi la articole →

Cel mai recent articol

Ultima verificare

Urmăritori 0 urmăritori
Articole: 200
  1. A successful development team is like a bees nest.

  2. Woah, automatically convert your plain JavaScript React components to TypeScript.

  3. Watch out: You may unknowingly be addicted to complexity.

  4. "I've heard from several people that they've consolidated their companies tool dependencies into a single package and this worked really well for t...

  5. 6 years ago: I was terrified of public speaking.

  6. Slick way to update an element in an array in an immutable manner *without changing the array's order*.

  7. Seriously, if you haven't tried automated testing with @Cypress_io, do it now.

  8. Career tip: If your boss doesn't see it, you won't get credit for it.

  9. Three ways to design a reusable React component: 1.

  10. React tip: You often don't need to declare a constructor in class components.

  11. Speaker tip: Instead of asking "Who doesn't understand x?"

  12. Perhaps the most striking stat on the 2017 State of #JavaScript Survey: VS Code (@code) is by far the most popular editor - and it's only 2.5 years...

  13. Coding a simple prototype takes a little time, but saves a ton of time in discussion.

  14. Man, after using @prettiercode for a month, I'd love to have all the time back that I've wasted over the years manually formatting code!

  15. Just rewrote a Redux app in plain React.

  16. Creating a new feature

    Creating a new feature?

  17. Woah, prettier does a wonderful job formatting markdown files too!

  18. What Legos Can Teach Us About Reuse in React Apps React is a component library.

  19. Handy way to update npm packages: Use npx.

  20. Perf tip: Stop using babel-preset-es2015.

  21. Coming very soon: Use cipm instead of npm on your CI server for 20x faster install than npm 4!

  22. It's live

    It's live!

  23. Using the same JS lib on multiple apps?

  24. Extract your setState calls to pure functions.

  25. Tip: Does your project work better with @code (VS Code) extensions?

  26. Avoid repeating yourself by centralizing PropTypes There are three popular ways to handle types in React: PropTypes, TypeScript and Flow.

  27. Tip: With async/await, you can run multiple async operations in parallel.

  28. As a long-time OO developer, I've finally embraced the functional paradigm in #javascript.

  29. Is there a single good reason to ever use a static class in #javascript instead of simply exporting the public functions?

  30. Here's a handy pattern to easily build objects for #javascript tests.

  31. Just updated the "Tech Speaker Starter Kit" with some new resources including a list of over *800* conferences: https://github.com/coryhouse/speake...

  32. This is absolutely key

    This is absolutely key.

  33. Much of writing testable code boils down to this: Keep logic and I/O separate.

  34. Why blog

    Why blog?

  35. Spent the morning comparing React's syntax to Angular, Vue, and Ember's for my upcoming "React: The Big Picture" course...

  36. I'm a fan of Redux, but it's a power tool, not a "use it all the time" tool.

  37. Developer job security: Low road: Obfuscate so only you can understand.

  38. Woah, you can get most of TypeScript's benefits with plain JS by just slapping comments in your code?!

  39. I've found a VSCode setup I ❤️: Material Pale Night Material Icon Theme See settings in 2nd screenshot.

  40. Imagine your team just deployed an amazing todo list app.

  41. "Never Write another Higher Order Component" Excellent talk by @mjackson on an alternative pattern: Render props https://www.youtube.com/watch?

  42. To convey the big picture, I'm compiling a list of reasons *not* to use React for my new course.

  43. Deployment & release aren't the same thing.

  44. After watching my "Building JS Dev Environment" course, someone emailed me: "How do you keep up with JavaScript churn?"

  45. A Call For Speakers…From 40,000 Feet I’m writing this from a bar…that’s floating somewhere over Greenland.

  46. Remote work is much more productive for me.

  47. Developer

    Developer?

  48. After attending many conferences, I've realized: I don't attend to learn.

  49. "JavaScript fatigue is what happens when people use tools they don't need to solve problems they don't have." - Lucas F Costa #nejsconf

  50. Was about to create this, but great to find it exists!