3 ms·
0. Define what problem you are trying to solve, make sure you understand the domain. 1. Come up with a set of options by doing research, talking to people who
by matt_kantor 6y ago
0. Define what problem you are trying to solve, make sure you understand the domain.
1. Come up with a set of options by doing research, talking to people who have solved similar problems before, etc.
2. Rank them by some criteria (e.g. availability of libraries, documentation, raw performance, hireability, support, quality of tooling, etc).
3. Do some prototyping in your problem domain using the top 2-3 (more if you aren't confident in your ranking) and pick whichever you like best.
4. Always be willing to change your mind down the road. Avoid the sunk cost fallacy and try not to lock yourself in too much until you're confident in your choice.