3 ms·
Low code is still a code. It is just matter of time before some office worker will create large and humungous low code project which then will be used by half o
by TheLoafOfBread 4y ago
Low code is still a code. It is just matter of time before some office worker will create large and humungous low code project which then will be used by half of the office. Because worker never coded before, whole project will slowly (or quickly) become unmaintainable mess where one change will brake 3 features.
Then they will call a developer to sort this mess out and it needs to be done yesterday.
- jrochkind1 4y agoPeople who have spent years coding are also perfectly capable of creating unmaintainable messes where one change will break 3 features, thank you very much.
- TheLoafOfBread 4y agoWhen you will be now "maintaining" 1000+ row VBA macro script in Excel linking dozens of files to generate a report and office folks will ask you to fix it because it does not work properly and author was laid off month ago, you will have different opinion.
- jrochkind1 4y agoPerhaps same opinion as if you're maintaining a, I dunno, 50K+ line software package as a development-team of one, which was developed by a single developer (who learned to code on the job) over a 10-year period and he left a few months ago. (Yes, this happens). Many "low-code" solutions definitely give you enough rope to hang yourself. In this regard, ironically, they are more similar to than different from other kinds of coding. I'm not even sure Excel should count as "low-code". A multi-thousand line VBA macro script doesn't sound "low code" at all, right?
- TheLoafOfBread 4y agoAs I wrote in first post, low code is still a code. And there will be some office worker who will have enough time to pile up a massive project which is not documented, nobody knows how it works, the worker is gone, but half of office is dependent on it.
- jrochkind1 4y agoAgreed.