4 ms·
That's a weird thing to despise. You know it's not necessary to try and put everything on a level playing field. I don't think your argument is valid on that fr
by nameisname 5y ago
That's a weird thing to despise. You know it's not necessary to try and put everything on a level playing field. I don't think your argument is valid on that front because when you code, you're inputting code. Nobody says "I'm going to do some text based programming" unless there's a need for that distinction in that situation. I think low code and no code are perfectly valid because you're inputting no or close to no code to achieve the task.
- tempacct3575 5y agoThe main reason I despise it is that the term is often used to imply that there is "no technical debt" or "no maintenance costs" or that this is "not real programming". In reality, users are still creating software, so technical debt and other maintenance costs will still build over time. Project management, feature prioritization, data/schema design, system design, module decomposition, testing, etc are all still important tasks and don't go away just because the tools are visual. A lot of it is due to perceptions - in my experience senior non-tech managers misunderstand the term, whereas "visual programming" still emphasizes that this is a software project with all that entails, just constructed in a more accessible way.