[PaulHoule]

I’ve worked at places where we’ve been building very speculative high-tech platforms, others where we built a few complex apps for the long term over the course of years, and others where we knocked out a stupendous number of simple to moderate complexity applications (70 in 8 months!) for a wide range of customers.

That last case has gotten me excited about no code because “excellence” in a place like that is standardizing what your team does to produce a good enough product with minimum effort, particularly no wasted effort.

I also spent some time looking at applications of “semantic technology”, ontologies, and ideas from the old symbolic A.I. with a business development guy and one thing we researched in depth was “low code”.

As a dev my concerns are: (1] low-code gets productivity by imposing defaults, if management/customers are happy with those defaults that’s great but if they insist they want something different that could eliminate many of the benefits or worse it could be a lot more expensive to get it right. (2) on successful projects devs spend much more time maintaining than building greenfield systems, if low-code is really going to be competitive in the long term it has to have a great story for that.

Look up my profile and shoot me an email, I’d love to talk some more.

[Aaikansh22]

Thanks for sharing your thoughts – really interesting stuff!

I totally see your point about low-code defaults and the maintenance hustle. Balancing efficiency and customization is key, and yeah, keeping things running smooth is where the real game is at.

Writing to you now. Would be great to chat more.