Working for a consultancy company reveals patterns in the market; becomes beneficial to get familiar with multiple products, multiple engineering teams and multiple user's needs.
One common problem is using a known tool for everything, in this case react/redux/sagas, even for the simplest of the projects, ending up engineering something like this:
Why not use a simple tool instead?
The 4 dimensions are:
Data source: centralized/relational (middleware) -> real time/non-relational (observables)
Presentational purpose: consumption only -> manipulation
View complexity: single purpose screen -> multiple views interaction screen
Data life-cycle: volatile -> persistent
The purpose of the article will be to trigger skepticism and analytical prowess on the engineering teams, to assess the product with more appropriate tooling instead of picking the most complex ones and making grandma remotes.
sadasant
commented
6 years ago
Working for a consultancy company reveals patterns in the market; becomes beneficial to get familiar with multiple products, multiple engineering teams and multiple user's needs.
One common problem is using a known tool for everything, in this case react/redux/sagas, even for the simplest of the projects, ending up engineering something like this:
Why not use a simple tool instead?
The 4 dimensions are:
The purpose of the article will be to trigger skepticism and analytical prowess on the engineering teams, to assess the product with more appropriate tooling instead of picking the most complex ones and making grandma remotes.