Well said.
I would also add that it is perfectly fine to have a list of red flags, and it is perfect fine to define your own bondaries.
Graphql is a red flag for me too, as well is React and node.js, and even git to some extend.
I love simplicity when designing web apps, their backend, their frontend and the deployment process in between.
Although the tech is old , I came up that vue3+pouchdb+quasar is an amazing combination for a stable replicable dev environment, pwa, supports offline usage, and introduces possible p2p replication between browser's pouchdb instances trough webrtc.
React , imo, is a good over engineered library suffering from fragmentation.
Angular is less fragmented, and Vue is the most elegant, performant and versatile of the 3.
Good Devs choose Vue after having worked with both react and angular.
React Dev never tried Vue, nor Angular Dev try React.
Vue Dev usually know all 3.
Having a red flag like graphql can tell a lot about technical overview and experience in failure.
Graphql solves a caching issue that Facebook has. Makes the frontend team life easy, making the backend team life hell , big big hello. Scope changes in the backend are terrible.
Unless your team is engineered driven, and engineers take tech decision, and setup the sprints, going graphql in the backend is a recipe for disaster.
React , imo, is a good over engineered library suffering from fragmentation. Angular is less fragmented, and Vue is the most elegant, performant and versatile of the 3. Good Devs choose Vue after having worked with both react and angular. React Dev never tried Vue, nor Angular Dev try React. Vue Dev usually know all 3.
Having a red flag like graphql can tell a lot about technical overview and experience in failure.
Graphql solves a caching issue that Facebook has. Makes the frontend team life easy, making the backend team life hell , big big hello. Scope changes in the backend are terrible.
Unless your team is engineered driven, and engineers take tech decision, and setup the sprints, going graphql in the backend is a recipe for disaster.