I think you can read the statement through a charitable or uncharitable lens - the uncharitable way is "throw 30 engineers at a problem and it'll get faster"
However, in the context of the other comments the GP made, I interpreted it as, "You can have a larger team with a properly built system with usability and maintainability, with good separation of concerns, and speed things up that way, but we have a smaller team and so bubble serves us well by allowing us to get things done quickly".
> I have serious doubts about this 'no code' movement.
I think the GP was pretty transparent about what it is good for and what it is not - I think the "wordpress for apps" is a good description. Wordpress is great for a particular class of problem, and then when you get to a certain level of complexity, you end up throwing it out and rewriting it, or putting so much on top of/around it that it is unrecognizable.
However, in the context of the other comments the GP made, I interpreted it as, "You can have a larger team with a properly built system with usability and maintainability, with good separation of concerns, and speed things up that way, but we have a smaller team and so bubble serves us well by allowing us to get things done quickly".
> I have serious doubts about this 'no code' movement.
I think the GP was pretty transparent about what it is good for and what it is not - I think the "wordpress for apps" is a good description. Wordpress is great for a particular class of problem, and then when you get to a certain level of complexity, you end up throwing it out and rewriting it, or putting so much on top of/around it that it is unrecognizable.