3 ms·
I tend to agree, but I do enjoy the direction we are headed. At first, the solutions will be clunky and more often than not incomplete or wrong. However, with t
by zabomber 4y ago
I tend to agree, but I do enjoy the direction we are headed. At first, the solutions will be clunky and more often than not incomplete or wrong. However, with time, the great solutions will prevail, opportunity will present itself and lead to innovation and we will end up utilising tools like this to get 80% of the work done so we can focus on the real value of the product or solution.
- skrtskrt 4y agoSeriously I see no reason why a no-code config tool couldn’t autogenerate vast swaths of Django or Rails or Next.js projects for common usecases
- jeltz 4y agoBut why not just do that with code? Or use a framework which requires less boilerplate?
- stitched2gethr 4y agoYou would because you can without a subscription. If no code tools were free we might see different uses, but I really can't see people who can code paying for tools like this.
- skrtskrt 4y agoSo a nontechnical user can basically mock up what they want and a backend dev can touch it up and get it production ready without having to slog through all tedious model and handler writing and can focus on non-solved problems. This is already a workflow that works relatively well in big data stuff - analyst makes a dashboard with some spark queries, which work but are slow and inflexible, data engineer tweaks into a production-ready pipeline and data warehouse view using more professional-level code. The vast majority of stuff where you just log users in, sell some stuff or subscriptions, and collect payment is already done with tedious identical piles of Django and Rails code anyway.
- pydry 4y agoI'm surprised we havent seen more of this. I guess the problem is that you dont have a competitive moat. It's too easy for your users to just take the code, find their own developers and host it themselves.