You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In our repo we have a client-side/javascript doc that needs some contributions. Ideally we will link to the Google JS standards and all of us together will create a style guide for how we write JS.
The text was updated successfully, but these errors were encountered:
Do we want to add JS specific best practices to the best-practices/native page? What has helped in the past when writing, styling and running javascript?
@michaelachrisco I had a very eye-opening talk the other day with a more senior dev I know and he challenged me to ask myself the why. In other words, are we reinventing the wheel by writing our own versions of these JS best practices? Is there an existing resource we can link to that would be just as effective, but would take us less time? What are your thoughts?
I would say that compiling resources is fine. Often times people will lightly curate resources and guides. Part of best practices for a shop is defining a common standard. Javascript is an especially open ended language that allows many different approaches. It's helpful to have resources that support shop style. For instance, we encourage using TypeScript for most Javascript projects and Flow for React.
In our repo we have a client-side/javascript doc that needs some contributions. Ideally we will link to the Google JS standards and all of us together will create a style guide for how we write JS.
The text was updated successfully, but these errors were encountered: