I wholeheartedly agree that software development as a whole, especially in the past few years, has been more in the spirit of 'wizardry'.
But with the speed at which the sheer amount of new software 'stuff' comes out each year, there's simply hasn't been enough time to develop rigorous engineering specs or best practices for all of those tools.
Perhaps we're starting to see an initial version of a universally accepted model, at least for the frontend, with the mentioned Typescript + Flux (I'll just say Redux).
Many assume that Redux is only a state container, and it is at face value, but more semantically it is (when implemented correctly) a very logical boilerplate where it puts everything related to state in its proper place, so any developer can look at the code base and immediately get a general idea of where state is set, what events exist and how the state is used throughout an application.
I'd like to see things like these very strict patterns emerge for other tools, like Node. For example, I could imagine a snippet of THE universally accepted express boilerplate for a login, given a specific backend... (can an email + password login really get _that_ customized?)
...argh, on second thought I suppose it can, but even then such a boilerplate could have sections with a freebie spot for customizations
Eh, it's late and I wonder if such universal pattern ideas are a pipedream... I suppose only time will tell...
Comments
I wholeheartedly agree that software development as a whole, especially in the past few years, has been more in the spirit of 'wizardry'.
But with the speed at which the sheer amount of new software 'stuff' comes out each year, there's simply hasn't been enough time to develop rigorous engineering specs or best practices for all of those tools.
Perhaps we're starting to see an initial version of a universally accepted model, at least for the frontend, with the mentioned Typescript + Flux (I'll just say Redux).
Many assume that Redux is only a state container, and it is at face value, but more semantically it is (when implemented correctly) a very logical boilerplate where it puts everything related to state in its proper place, so any developer can look at the code base and immediately get a general idea of where state is set, what events exist and how the state is used throughout an application.
I'd like to see things like these very strict patterns emerge for other tools, like Node. For example, I could imagine a snippet of THE universally accepted express boilerplate for a login, given a specific backend... (can an email + password login really get _that_ customized?)
...argh, on second thought I suppose it can, but even then such a boilerplate could have sections with a freebie spot for customizations
Eh, it's late and I wonder if such universal pattern ideas are a pipedream... I suppose only time will tell...