Leading takeaway from all the conversations I had today with folks from the #NoCodeConf is this:

WE can finally build the products and services we previously could only dream up or design, but couldn’t actually create.

1/

This is a PROFOUND shift because many of us have developed local expertise of a specific problem or an idea for a specific service, and we no longer need to rely on traditional SW developers to build the thing we’ve envisioned. We can just do it ourselves.

2/

Not only can we do all this ourselves, but the resulting products we are building (and there were some cool ones shown today) are not just on par with those built with more traditional methods, they’re better! And they’re a lot more flexible and upgradeable.

3/

And, the pace of change here is non-linear. More and more tools and capabilities are being built on these platforms all the time. So while what we have to work with today is *good*, the toolset we’ll have tomorrow will be much much better..

4/

All this begs the question: is the balance of power shifting from the coder to the no-coder? Said differently, if you were going to start something today, which path would you take? Where does it make sense to go nocode? And where does traditional dev make more sense?