[knighthack]

> You can throw 30 software engineers and have a system and increase velocity that way.

This makes absolutely no sense at all. You obviously have not read _The Mythical Man-Month_, and judging by what you've written I completely doubt the entirety of what you've said.

Speed is one thing. The long-term maintainability and usability of a system is another thing altogether. I have serious doubts about this 'no code' movement.

[mattzito]

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.

[Uehreka]

Given the kind of cocky tone elsewhere in that comment, I read it as “the biggest problem with Bubble is that if you’re an engineering manager who likes maintaining a fiefdom of 30 engineers, you won’t get to do that anymore”. No-code folks often try and make it seem like their biggest antagonists are corrupt middle managers, because they make for better rhetorical punching bags than individual contributor developers.

You’re right about the mythical man month, but I have a feeling this person is trying to grind an axe more than make a coherent point.

[zubairlk]

Ok I'll elaborate.

I really really miss git, version control systems, pull requests, automated ci checks etc.

Imagine a world without git and version control systems. Then apply that to NoCode.

Who changed which line. When did it happen. These things are normal with code/git. But not with NoCode/bubble (yet Jul2021).

Which file is the master. Which change to merge.

And then throw 30 software engineers at the project. Chaos will happen.

The comment was less about architecture and more about version control and merging which is still early days in the world of bubble compared to software engineering