2 ms·
I run into this scenario particularly in large React code bases. Multiple developers building their own half baked abstractions on top of a framework with its o
by cooperadymas 6y ago
I run into this scenario particularly in large React code bases. Multiple developers building their own half baked abstractions on top of a framework with its own continually shifting abstractions. Lack of uniting engineering leadership and not enough time to devote to code discipline - it's a real joy.
- kevsim 6y agoOh yeah! Nothing like a bunch of old poorly thought out "render props" style high level components getting mushed together with a bunch of new poorly thought out custom React hooks :-)
- searchableguy 6y agoMy problem with react is that there are so many ways to do the same things that reusability and refactoring becomes harder than it should be. I usually found 3-4 ways of styling in a medium codebase on github. I find varying degrees of state management - some built with context and hooks, some imported and traditional mobx/redux. I haven't found many significant opportunities to reuse code without refactoring a lot or doing micro files of 7 lines of code and separating logical components. I now think of react as a library to build your own frameworks. It aligns perfectly with the javascript ecosystem mentality.
- randompwd 6y agoJust started looking at Spring Boot (w/Kotlin). Never try it. A bazillion ways to do basic web service & web things and every google search returns different methods. Nightmare.
- vips7L 6y agoDid you look at https://spring.io/guides https://spring.io/guides ? Building a REST service is one of the examples. https://spring.io/guides/tutorials/rest/ https://spring.io/guides/tutorials/rest/