Just a quick roundup of strengths behind building your next application with nocode tech... #bubble

So let's talk about the strengths behind some of these concepts. Why don't we start with no code first?

That it's fast, it is cheap error. Yes. It's easier to maintain. And for me, I think, especially if you're a less tech savvy founder, biggest advantage is that you can actually understand what you're building. You can go in and with not too much of a learning curve. There is a learning curve. You can read your application, you can look at the workflows, you can understand what's going on, you can make changes. If you so des, the most important thing is you can understand it so that you actually have your fingers on the pulse of your product. Now, if you're a very tech savvy coder, then you have that advantage. When you do pro code, you know, when you do, you know, traditional software development because you can go in and understand what's going on, or you conceivably can. But a lot of founders don't have that luxury and that means that they're married to their developers or to their cto.

But I've seen bubble developers who are bringing up bubble because it's what we use, but it applies to other no.

Code platforms.

I've seen traditional developers move away from pro coding to no code.

Of course it's faster.

Because it's faster.

It'S cheaper, you can get to market quicker, you can pivot easily. It has a lot of advantages.