Node.JS Practices

@nodepractices

Cherry picked Node.JS best practices

github.com/i0natan/nodebe…
Vrijeme pridruživanja: lipanj 2016.
98 fotografija ili videozapisa Fotografije i videozapisi

Tweetovi

Blokirali ste korisnika/cu @nodepractices

Jeste li sigurni da želite vidjeti te tweetove? Time nećete deblokirati korisnika/cu @nodepractices

  1. 26. sij

    Given the immense popularity of Docker and the need to harden it differently per platform - we'd like to start writing a Docker best practices section Contribute an idea or just join the discussion here:

    10 proslijeđenih tweetova 29 korisnika označava da im se sviđa
    Poništi
  2. proslijedio/la je Tweet
    13. sij

    Node.js CI blueprint - 2020 q1 Don't get overwhelmed, it's just a pool of ideas and tools to pick from Did I forget any valuable steps or tools? let's enrich it Full version with tools list here:

    1 reply 13 proslijeđenih tweetova 59 korisnika označava da im se sviđa
    Poništi
  3. proslijedio/la je Tweet
    7. sij

    📣 I'm working now on a comprehensive Node.js testing course (11 hours) To ensure the quality is high, the lessons are shared first at no cost with a preview group Wanna join and get the lessons? The registration is open now for 2 hours, 10 seats left:

    9 proslijeđenih tweetova 36 korisnika označava da im se sviđa
    Prikaži ovu nit
    Prikaži ovu nit
    Poništi
  4. proslijedio/la je Tweet
    6. sij

    What's new in Node.js testing? My talk from Verona is now online:

    10 proslijeđenih tweetova 34 korisnika označavaju da im se sviđa
    Poništi
  5. 31. pro 2019.

    Unsurprisingly the event loop is the bottleneck of everything Surprisingly, it's very easy to monitor it. Even easier with this great article:

    1 reply 10 proslijeđenih tweetova 25 korisnika označava da im se sviđa
    Poništi
  6. proslijedio/la je Tweet
    20. pro 2019.

    Glad that finds my testing best practices guide attractive Working now on a comprehensive backend testing course, updates will follow soon

    Node.js & JavaScript Testing Best Practices (2019) via
    3 proslijeđena tweeta 30 korisnika označava da im se sviđa
    Poništi
  7. proslijedio/la je Tweet
    12. pro 2019.

    🌟 Just published '20 ways to become a better Node.js developer in 2020' 🌟 You'll find inside strategic advice that deals with enriching our toolbox, JavaScript flavors, testing, concurrency, production run-time, and... sleep 🛌

    48 proslijeđenih tweetova 71 korisnik označava da mu se sviđa
    Poništi
  8. 19. stu 2019.

    Fine-tuning your IDE and linters for delightful coding experience is no less than critical knocks it out of the park here:

    4 proslijeđena tweeta 13 korisnika označava da im se sviđa
    Poništi
  9. 17. stu 2019.

    We have begun to include a example beneath each of the ~100 code examples Thank you, Kevyn Bruyere, for this epic commit 💚

    12 proslijeđenih tweetova 39 korisnika označava da im se sviđa
    Poništi
  10. proslijedio/la je Tweet
    5. stu 2019.

    This Node.js Best Practices guide by has some great security guidance.

    14 proslijeđenih tweetova 46 korisnika označava da im se sviđa
    Poništi
  11. 3. stu 2019.

    A useful compilation of logging best practices for Node.js Best advice: 'The log should not evaluate to throw an exception' - write safely, beware of method calls within log statements

    7 proslijeđenih tweetova 23 korisnika označavaju da im se sviđa
    Poništi
  12. proslijedio/la je Tweet
    30. lis 2019.

    I draw a thing about ! Thanks and for the great course on Visual Thinking!

    18 proslijeđenih tweetova 82 korisnika označavaju da im se sviđa
    Poništi
  13. 29. lis 2019.

    It's time to thank our great contributors for their amazing work in Sep/Oct Highlights: - The repo is now fully translated to Russian 🇷🇺 - A new best practice ✅ - 7.2 'Don't block the event loop' with examples - WIP: code examples in TypeScript

    3 proslijeđena tweeta 8 korisnika označava da im se sviđa
    Poništi
  14. proslijedio/la je Tweet
    28. lis 2019.

    Having a new component, we sometimes have doubt whether it should be a Microservice or a package We know the theory but as human beings, we might overlook some considerations My new post is a gamified checklist to ensure we don't forget any criteria

    5 proslijeđenih tweetova 7 korisnika označava da im se sviđa
    Poništi
  15. 26. lis 2019.

    This movie worth its length in gold 💎 Docker and Node.js Best Practices from Bret Fisher 👇

    8 proslijeđenih tweetova 32 korisnika označavaju da im se sviđa
    Poništi
  16. proslijedio/la je Tweet
    11. lis 2019.
    Odgovor korisniku/ci

    +1 And you can also do that in-memory very easily to achieve both reliability and speed Mongo has a build-in in-memory egine. For pg and mySQL we can map the data drive to tmpfs 👇

    2 proslijeđena tweeta 6 korisnika označava da im se sviđa
    Poništi
  17. 11. lis 2019.

    The linting world is alive and kicking with super useful linters pop up frequently. To name a few example beyond the standard: - Dependency-cruiser - Eslint-plugin-promise - Eslint-plugin-import - lockfile-lint - Others Familiar with any new useful linter?

    7 proslijeđenih tweetova 16 korisnika označava da im se sviđa
    Poništi
  18. proslijedio/la je Tweet
    6. lis 2019.

    Using complex Hexagonal-like architecture only to separate your app core from the end points, a thing that could easily achieved using 3 simple folders, is like using a ferrari to catch a lame rabbit

    1 reply 6 proslijeđenih tweetova 15 korisnika označava da im se sviđa
    Poništi
  19. proslijedio/la je Tweet
    25. ruj 2019.

    Happy and excited to speak next week at days Italy about the latest 2019 trends and opportunities of testing: - Shift right / continous testing - Component test - Testing with prod - Traffic shadow - Results of my testing survey (300+ dev) - More

    1 reply 4 proslijeđena tweeta 13 korisnika označava da im se sviđa
    Prikaži ovu nit
    Prikaži ovu nit
    Poništi
  20. 23. ruj 2019.

    Great article that outlines a typical package release flow along with useful packages (e.g. standard-version, semantic-release, commitzen, others) to help us get there safely Can be useful also for a typical Microservice release flow

    8 proslijeđenih tweetova 11 korisnika označava da im se sviđa
    Poništi

@nodepractices još nije objavio nijedan Tweet.

Čini se da učitavanje traje već neko vrijeme.

Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.

    Možda bi vam se svidjelo i ovo:

    ·