4 ms·
This is what we've resigned ourselves to, but it's very expensive. We're building crud apps, not doing cutting edge research, so I assumed we would be able to f
by pault 7y ago
This is what we've resigned ourselves to, but it's very expensive. We're building crud apps, not doing cutting edge research, so I assumed we would be able to find someone that is already up to speed on the language and frameworks. You also have to factor in the cost of senior developer time spent coaching, the lost productivity, and the code quality suffering in the meantime.
- gowld 7y ago> We're building crud apps Perhaps you shouldn't be using complicated faddish framework then?
- mixmastamyk 7y agoWas just thinking that too. Many folks like to complain about the quality of "the help," but don't look in the mirror.
- titusjohnson 7y agoYou might be shooting yourself in the foot by having not picking an ecosystem that better supports your business case. No one I know who's good at React+Redux would pick a CRUD app as the domain they'd like to exercise those skills in.
- pault 7y agoThe app in question is used by retail employees at hundreds of locations to manage inventory. It runs on a tablet, has to work offline, and has a very dynamic UI that has to keep thousands of complex relational entities in local state, and perform aggregate functions on them in real time. It's still a CRUD app, but it's very much the use case for a SPA.
- deleted 7y ago[deleted]