-
Been thinking about grouping FE dev tools. 3 main groups - Safety net: linters, git, spelling, etc - Transform (babel, postcss, typescript, etc) - makes future/alt code deployable - Post code: tests, CI, packaging, etc Suspect that's just one way to cut it. How would you group?
-
A question that highlights the problem with "tools" Is Atomic Design (for instance) a tool or a strategy? I'd say the later, but I can see you might say "tool". I say strategy as it's a _way_ of coding and doesn't actually touch code.