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
We're still in the process of building expertise in our preferred JavaScript frameworks, Gatsby and React, so this issue is for the medium to long term. Once we have developed sufficient and shared expertise in the core concepts and patterns of our stack, let's ask ourselves: Are our tools working for us? What do we like? What don't we like? Are there better (for us) alternatives? (One name that came up is Svelte.)
The text was updated successfully, but these errors were encountered:
I think this is plenty actionable. Let's set a time during R&D to have an intentional team discussion about what we like and dislike about our JavaScript tools. We did this for our devops stack, and it was very helpful in surfacing pain points and providing priorities for areas of improvement that we could measure proposed changes against.
We're still in the process of building expertise in our preferred JavaScript frameworks, Gatsby and React, so this issue is for the medium to long term. Once we have developed sufficient and shared expertise in the core concepts and patterns of our stack, let's ask ourselves: Are our tools working for us? What do we like? What don't we like? Are there better (for us) alternatives? (One name that came up is Svelte.)
The text was updated successfully, but these errors were encountered: