Live data from Hacker News

Ask HN: What do you think about the no-code movement?

news.ycombinator.com

351–360 of 404 posts

Re: Ask HN: What do you think about the no-code movement?

#352
I think that nocode could be very useful for many small companies. Yet it's very hard to build a truly scalable nocode service. You would need to be able to easily expand it with full-code components and all components must be able to interact with each other freely. UI must be accessible for ordinary people.

Hard task. But doable.

Re: Ask HN: What do you think about the no-code movement?

#354
I think it stems from the inability to realize that it's not the fact that programming is currently done by typing words and symbols into text files that makes it hard for some people. But that it requires some ability to break up a problem into simpler tasks and then solving those tasks using discrete actions.

The people who can program in no-code environments can also program in all other environments.

Sure, there are _LOTS_ of ways to improve the status quo, and any idea should be tried, but I'd much rather explore more interactive programming environments than focus on the input method.

Re: Ask HN: What do you think about the no-code movement?

#355
Software engineering is too hard. A relatively easy project still needs a coder that has had lots of training and then the never ending maintenance comes after. Even the no code version takes lots of work.

We need the ikea version of software development where a lay person can put together a common type of app and maintenance is mostly automatic. I think the nocode "movement" is here to stay and it's only going to get bigger, in terms of number of apps, and ease of use.

Re: Ask HN: What do you think about the no-code movement?

#358
post #10

It's interesting, but always calibrate their claims against the fact this is about the tenth time this movement has come around. This movement literally goes back to COBOL. That is not a typo. It's not only likely older than you are, but probably much older than you are. I recognize COBOL may not seem like "no-code", but that's just because "no-code" is a stupid label. "No-code" doesn't mean "no code" just like "serv…

I remember my father coming home in the 80s from work with a book detailing an environment they built at the company he worked at for creating complete business systems by just configuring building blocks; no code at all. You modeled the data, modeled the screens, modeled the processes by picking options of screens covered in dropdowns and input fields: the end result was a working system. Sounds familiar? It was extremely close to Bubble with a different GUI. It worked until clients asked feature that were very hard or impossible to make and they add to add features or code extensions; after a while they noted that many projects were just extensions upon extensions. They ended up taking out the modeling part and use it like UML type of thing, but the no code was removed in favor of people writing it manually following the modeled parts.

Re: Ask HN: What do you think about the no-code movement?

#359

Earlier quoted context omitted.

On the other hand, the market has expanded beyond economies where users have the space, power and physical safety to actually own a desktop. For some people their first, last and only "PC" is their smartphone. Your choice then becomes embracing those users or not having those users at all.

"One size fits all" fits no one.

You build where your money is; our clients are asking for phone versions of dashboards, reports etc as they simply don't have or don't want to use desktops. Maintaining software for it is just not worth it.

Re: Ask HN: What do you think about the no-code movement?

#360
post #10

It's interesting, but always calibrate their claims against the fact this is about the tenth time this movement has come around. This movement literally goes back to COBOL. That is not a typo. It's not only likely older than you are, but probably much older than you are. I recognize COBOL may not seem like "no-code", but that's just because "no-code" is a stupid label. "No-code" doesn't mean "no code" just like "serv…

COBOL never claimed to be "no code", but what it did claim was that it would significantly lower the level of training required to program. Which it absolutely did. Before compilers, you had to program in machine code which was extremely tedious and error prone and required a detailed understanding the microprocessor and computer architecture.

COBOL may seem clunky compared to modern languages, but the productivity improvement going from machine code to COBOL was likely larger than going from C++ to Python. COBOL have a bad reputation these days, but this is only because of how successful it was, leading it to still being used for mission-critical systems.

Post reply on HN