This screams naivete to me (but maybe perhaps I'm naive myself ...). I can't imagine how this system would possibly scale or how integration with all the small parts would work. Software is unique in the world of engineering. People know how to build bridges. We, for whatever reason, just don't know how to build software on that scale at the same reliability and with the same consistency that we build bridges.
Software is not made up of interchangeable parts in the sense that you can't outsource each individual function in a giant library and hope for seamless integration. This guy's working at a lesser granularity than that, but I'm just waiting for the day when some unexpected behavior from his controller causes massive failure in his backend and no one knows how to fix it because no one understands the whole system (or at least a big enough chunk of it).
Edit: Just saw his response:
Am doing this to give myself time to continue to talk to possible investors and decide where I want to locate.
If you're prototyping for investors, that may be reasonable, as long as you throw it away and start with a fresh coherent team at some point.
Software is not made up of interchangeable parts in the sense that you can't outsource each individual function in a giant library and hope for seamless integration. This guy's working at a lesser granularity than that, but I'm just waiting for the day when some unexpected behavior from his controller causes massive failure in his backend and no one knows how to fix it because no one understands the whole system (or at least a big enough chunk of it).
Edit: Just saw his response:
Am doing this to give myself time to continue to talk to possible investors and decide where I want to locate.
If you're prototyping for investors, that may be reasonable, as long as you throw it away and start with a fresh coherent team at some point.