Have to agree wholeheartedly. He seems to have a problem landscape that involves CRUD on single 'documents/tables' with no business logic involved or required.

Have to agree wholeheartedly. He seems to have a problem landscape that involves CRUD on single 'documents/tables' with no business logic involved or required. I suppose it is fine to have business logic in a client, but replicating that for every platform seems silly and a simple way to acquire huge amounts of technical debt and complex role out strategies. He says about being the only backend guy to ensure not much code gets written there. I feel like this is not a person I want to work for. Not even seeing the problem before telling me the solution. This article could have been much better framed if it discussed using his suggested tooling to solve simple CRUD applications in a bootstrap scenario perhaps. But it has been my experience that long term, complex business systems that are created in Javascript are black holes of lost time trying to maintain and extend. Especially ones written to 'configure' the backend based on client defined configuration which he also suggests is a good thing.