What "naming conventions and file structures" are you referring to? I don't think Dan ever really popularized anything like that for _React_. If you're thinki

What "naming conventions and file structures" are you referring to? I don't think Dan ever really popularized anything like that for _React_. If you're thinking of _Redux_, are you referring to the early conventions of "folder-by-type" file structures? ie `actions/todos.js`, `reducers/todos.js`, `constants/todos.js`? If so, there's perfectly understandable reasons why we ended up there: - as programmers we try to "keep code of different kinds in different files", so you'd separate action creator definitions from reducer logic - but we want to have consistency and avoid accidental typos, especially in untyped plain JS, so you'd extract the string constants like `const ADD_TODO = "ADD_TODO"` into their own file for reuse in both places To be clear that was never a requirement for using Redux, although the docs did show that pattern. We eventually concluded that the "folder-by-feature" approach was better: - https://redux.js.org/style-guide/#structure-files-as-feature-folders-with-single-file-logic https://redux.js.org/style-guide/#structure-files-as-feature... and in fact the original "Redux Ducks" approach for single-file logic was created by the community just a couple months after Redux was created: - https://github.com/erikras/ducks-modular-redux https://github.com/erikras/ducks-modular-redux which is what we later turned into "Redux slices", a single file with a `createSlice` call that has your reducer logic and generates the action creators for you: - https://redux.js.org/tutorials/essentials/part-2-app-structure#redux-slices https://redux.js.org/tutorials/essentials/part-2-app-structu...