The point in time to do this is NOT NOW, however, we should maybe think about this at some point.
Besides the core lbadd, there will be static analysis tools (at least for the parser) that help developers develop better and more easily.
Other than analysis tools, there might be custom written code generator tools at some point, as well as a documentation homepage.
Maybe we even want to outsource certain components instead of having everything in one big repo. This would also allow other developers to re-use components that we built (like uber does with its libraries, we could outsource the parser, so that other projects have a working SQL parser (we keep the IR)).
Before doing this, we should build a sensible structure that works for us.
The point in time to do this is NOT NOW, however, we should maybe think about this at some point.
Besides the core lbadd, there will be static analysis tools (at least for the parser) that help developers develop better and more easily.
Other than analysis tools, there might be custom written code generator tools at some point, as well as a documentation homepage.
Maybe we even want to outsource certain components instead of having everything in one big repo. This would also allow other developers to re-use components that we built (like uber does with its libraries, we could outsource the parser, so that other projects have a working SQL parser (we keep the IR)).
Before doing this, we should build a sensible structure that works for us.