Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Recommendation system #54

Open
molant opened this issue Sep 21, 2021 · 0 comments
Open

Recommendation system #54

molant opened this issue Sep 21, 2021 · 0 comments
Labels
enhancement New feature or request

Comments

@molant
Copy link
Member

molant commented Sep 21, 2021

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!):

  • 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.

@molant molant added the enhancement New feature or request label Sep 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant