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
The reality is that there is not a single technology that is perfect for any scenario, but there are technologies that might work better than others depending on what needs to be solved and how.
The recommendation system should take into consideration several factors and how important they are for the user currently answering. The goal is to propose a short list of technologies for the user to evaluate/investigate.
Criteria
Because "everything is important" is not true, users should prioritize different criteria to know which ones to prioritize over others. This will also help decide what questions to ask.
The initial set of criteria I'm thinking of is (feel free to suggest others!):
E2E dev experience
How much of an integrated experience they expect: IDE support, test runner, best practices already established, etc.
Support
Pay for support in case of bug
Possibility to access the code to fix things themselves or contribute features
Green vs Brownfield
Does the new technology need to integrate seemlessly with an existing application
Look and feel
Does the developer want to have a consistent experience accross all the platforms?
Do they have resources to make it look good for all platforms?
Platform support
Does it need to be the same technology for all platform code base for all the wanted platforms or can it be different?
Some others I'm considering is distribution, type of end users (some technologies are better suited for enterprise than others), size of the team, etc. Not all the questions might be related to a criteria, but might help narrow things.
How to?
My initial thoughts are that each technology will have a score for each criteria. Then we will ask different questions to calculate a score considering the relative importance to the user and present the top 2-3.
The scores should live in the JSON files of each technology.
The text was updated successfully, but these errors were encountered:
Recommendation system
The reality is that there is not a single technology that is perfect for any scenario, but there are technologies that might work better than others depending on what needs to be solved and how.
The recommendation system should take into consideration several factors and how important they are for the user currently answering. The goal is to propose a short list of technologies for the user to evaluate/investigate.
Criteria
Because "everything is important" is not true, users should prioritize different criteria to know which ones to prioritize over others. This will also help decide what questions to ask.
The initial set of criteria I'm thinking of is (feel free to suggest others!):
Some others I'm considering is distribution, type of end users (some technologies are better suited for enterprise than others), size of the team, etc. Not all the questions might be related to a criteria, but might help narrow things.
How to?
My initial thoughts are that each technology will have a score for each criteria. Then we will ask different questions to calculate a score considering the relative importance to the user and present the top 2-3.
The scores should live in the JSON files of each technology.
The text was updated successfully, but these errors were encountered: