4 ms·
I just took a look at this and I don't think that the real win in terms of productivity is the fact that you are building an app with a visual environment or co
by vjeux 9y ago
I just took a look at this and I don't think that the real win in terms of productivity is the fact that you are building an app with a visual environment or code. Both of them are roughly equivalent.
What likely set them apart is the building blocks they provide. If you are a consulting company and building apps for businesses, you are likely doing the same thing over and over and over again for every business. Once you build an hospital management system for three hospitals, the fourth one isn't going to look that different. There are tens of thousands (more?) hospitals in the world which all need such a system.
So the likely next step is to invest in good building blocks that are needed: I want a dashboard with last week patient intake. All of this logic is put inside of a component ready to be dragged & dropped / included in your project and it saves you weeks rather than trying to rebuild it for the nth time.
- petra 9y agoI think the article is about the first version, not about reuse. But I could be wrong. But in any case, code is difficult: it requires deep attention, good memory - both short and long term(and long term memory doesn't work so well if you don't exercise the knowledge repeatedly ),good learning capabilities, and good abstractions capabilities. Visual systems are fundamentally easier. So if they can scale well to the required level of complexity and offer similar or better levels of productivity , they may become the 'easy' route.