Workaround for expiring attachment URLs

Hi Harini, and welcome to the forum.

I haven’t used Rowy much, but I’ve developed an interesting viewpoint about it. I believe Rowy, and other tools like it, define what’s next. And by “next”, I mean when the no/low-code database product segment must undergo a transformation to meet new demands related to artificial general intelligence.

I don’t think the founders and CEOs of the current crop of market-leading no/low-code platforms are ready for what happens after AI reaches the knee of the curve.

We’ve been talking about AI for a few decades now, and quietly, largely undetectable progress has continued. Nothing really big, nothing really impressive. Last year, we hit the"knee" of the curve. (Chain of Thought)

I have a hunch that Rowy is “AGI-ready”. This is to say that it has an underlying design that would support the ability to build applications based purely on instructions abstracted from an AI process. Am I wrong or premature about my hunch?

I recently wrote …

No-code front-ends and back-ends will flourish in the coming years. It will become a race of specialists. No-code solutions will transition into best-of-breed components beginning with the fundamental decision point - Which front-end and back-end do I choose for this project?

I wrote in a little more depth about this here.

BTW, last week I literally wrote a task for myself -

“Try to get in touch with the CEO of Rowy and ask her if she envisions a time when her platform will be able to respond to an AI prompt that describes a database system, and just build it.”

2 Likes