React / Typescript / Mobx / Dependency Injection / MVVM / Repository pattern

Hi all,

We are working on a front end project that uses Mobx with React and typescript for the scripting.

Someone introduced some patterns into the mix about using MVVM model which makes sense, but the other team members said that the controllers on the components are like the view models, so that's whatever.

Repository pattern was introduced and decided upon to use for the apis and such. Not sure if that is needed, though how it was done is hard for anyone else to follow but the developer that did it.

Then it was pushed to use Dependency Injection on all the react components view/models, and the other team said this is getting way too complex, so they are doing their own thing, while the other couple devs are doing the DI. It was claimed that it will make unit testing easier, but unit testing is just fine without it.

Do you think introducing all these patterns / methods are making things too complex? It seems to be slowing us down on development now and I don't see the need as we can still unit test stuff anyhow..

Meanwhile, the other team is blowing through work and looking like heros because they are getting shit done as they are following the "keep it simple" method.

I don't mind learning about incorporating all these patterns into the mix, but not sure if it's worth it for this project. What do you all think? I can see how to do what this dev recommended, but I don't see the value… It seems like everyone on the internet is pro DI anyhow

submitted by /u/mingnobee
[link] [comments]

from Software Development – methodologies, techniques, and tools. Covering Agile, RUP, Waterfall + more! https://ift.tt/3G38Rtu

Leave a comment

Design a site like this with WordPress.com
Get started
search previous next tag category expand menu location phone mail time cart zoom edit close