|
Clearly this will be an unpopular opinion here, but I believe low/no-code has its place. And honestly I've seen it proven out a few times where I work. I agree that it will never replace full development in all instances, but there are times when having a developer or even an intelligent power user quickly (point #1) build out simple (point #2) solutions with very little interference from security (point #3). At least this is what I have seen first-hand in the projects that have succeeded at my place of work.
The "inflexibility" of low/no-code is, in my opinion, guardrails preventing the power user from destroying more than a few decks of the Deathstar. If you want the whole thing blown up, that's when you need a full stack developer! 
|
|
|
|
|
You aren't the only professional developer that has a distaste for low-code/no-code. I recently did something in low-code/no-code just to try to please management. The program ran horridly slow, had poor version control and was difficult to debug. Now, I'm nearly finished rewriting the equivalent program in a conventional language and the former issues are gone.
In this particular case, the conventional language solution is far superior to the low-code/no-code solution.
|
|
|
|
|
Just wait till they discover COBOL. Anybody can read or write COBOL code (even managers) because it's in human language! 
|
|
|
|
|
I worked for a startup company developing such a tool and put many years of thought into it. The goal, of course, was to come up with a way to simplify mobile application development to reduce the time and skill needed to generate an app. It started with trying to do as much as possible with drag and drop in some sort of visual interface. We generated many custom mobile apps with the system for customers, but what we learned that you can only do so much with drag and drop, more custom control was needed. So we allowed more detailed configuration via direct manipulation of the underlying data. Then we learned, configuration can only take you so far, more control was needed. It turns out, there are some things that are actually easier and more concise to define in code than configuration or drag and drop! Trying to break down code into configurable data, at some point actually becomes more complicated than the code you are trying to replace. Then we started looking into defining our own scripting language, our own debugger, etc... which was crazy. So here we are trying to eliminate code and it came full circle and we are trying to define a new language. It failed in the end. I think a better approach is to actually build similar tools, but build it on an existing language like C++. Don't try to eliminate the developer, but give him tools to generate code and dramatically improve productivity. Go after the best of both worlds. You get the best possible end result with native generated C++ code, best possible user interface, best possible performance, and if customization is necessary (it always is), you are building on the best possible language with the best extensibility, cross platform at the code level, etc... What say you?
|
|
|
|
|
The suggestion that C++ is "the best possible language" will probably elicit some choice words from a large section of the profession!
I notice how defensive all you coders are (I'm one myself, by the way, nearly a half century of coding experience behind me, come of it on very complex applications) at the idea that "nocode" systems may have merit. I remember way back when Pascal was similarly and widely derided by "real programmers" as a limited language of no merit outside beginners' classrooms, and then found myself managing and supporting a network of CAD workstations running a very stable multi-user, multi-tasking Unix-like operating system written wholly in....Pascal! Not such a Mickey Mouse language after all.
Decent programmers will always be in demand, especially those who can adapt to new approaches. Those who can't or won't will wither away, and being defensive about progress or contemptuous towards those who see opportunity in it isn't going to change that.
|
|
|
|
|
By best possible end result I mean the best possible compiled native performance. Not necessarily the easiest to program, but the best result for the end user of the app. I think some of the higher level languages suffer from the same problems and shortcomings of no-code but to a lesser degree. Higher level languages such as Java, C#, and even web programming in general were created to save coding time. But they all sacrifice something to get there, runtime performance. I think we need to find better solutions that increase developer productivity without sacrificing native performance and native user interface capabilities.
|
|
|
|
|
I completely agree. Think of it this way, if you make a "program" that only increments an INT by a number, but then someone asks you to increment by 0.5  . Originally it was an INT. The no code says the same, I can only work with INTs, so don't change the parameter.
No code = More Work = Hype = forgotten in 1 Year. 
|
|
|
|
|
This is exactly what I experienced when trying to build such a system. What would be a better approach in your opinion to provide tools to dramatically enhance the productivity of developers?
|
|
|
|
|
No-Code is just snake oil for incompetent project managers...
|
|
|
|
|
Preach Brother Preach.
No Code means
NO Repair when you need it
NO UpDate when you need it
and
LOTS AND LOTS OF UNNEEDED AND UNWANTED OVERHEAD!
|
|
|
|
|
Still a long way to go, but ... it's a start: Breakthrough in nuclear fusion energy announced[^]
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Hmm, I saw that somewhere[^] yesterday. Though it is an interesting subject and bears repeating.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
Every time I eat at Taco Bell some kind of conversion occurs and the result is a energy release of some proportion.
If they could just find a way to harness that energy.
PartsBin an Electronics Part Organizer - An updated version available!
JaxCoder.com
|
|
|
|
|
|
Exactly
PartsBin an Electronics Part Organizer - An updated version available!
JaxCoder.com
|
|
|
|
|
Light a match? 
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
Kinda reminds me of;
A man went into the proctologist's office for his first exam. The doctor told him to have a seat in the examination room and that he would be with him in just a few minutes. Well, when the man sat down in the examination room, he noticed that there were three items on stand next to the doctor's desk: a tube of K-Y jelly, a rubber glove, and a beer.
When the doctor came in, the man said, "Look Doc, this is my first exam...I know what the K-Y is for. ...and I know what the glove is for...but what's the BEER for?"
At this instant, the doctor became noticeably outraged and stormed over to the door. The doc flung the door open and yelled to his nurse, "Dammit!! I said "a BUTT LIGHT!!"
PartsBin an Electronics Part Organizer - An updated version available!
JaxCoder.com
|
|
|
|
|
I have a memory of several times before having heard that 'we have crossed the break-even point'. It could possibly hold up this time - who knows?
I'm not holding my breath.
|
|
|
|
|
|
Giving but finish in debt ? (8)
Life should not be a journey to the grave with the intention of arriving safely in a pretty and well-preserved body, but rather to skid in broadside in a cloud of smoke, thoroughly used up, totally worn out, and loudly proclaiming “Wow! What a Ride!" - Hunter S Thompson - RIP
|
|
|
|
|
ENDOWED
END - finish
OWED - in debt
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
|
|
|
|
|
Oops wrong tense.
ENDOWING
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
|
|
|
|
|
Second attempt is correct YAUT 
Life should not be a journey to the grave with the intention of arriving safely in a pretty and well-preserved body, but rather to skid in broadside in a cloud of smoke, thoroughly used up, totally worn out, and loudly proclaiming “Wow! What a Ride!" - Hunter S Thompson - RIP
|
|
|
|
|
Over a year ago I made a funny function to take a rectangle (x1,y1,x2,y2) and "split" it by another rectangle, to yield up to 4 resulting rectangles by punching a second rectangle shaped hole in the first rectangle.
I thought it might be useful someday.
Today I used it. I was optimizing battery life for a remote I built, so I wanted to minimize the amount I was communicating to the display on it.
I used this spit() function to knock out areas that were to be replaced with dynamically rendered bits so that when I rendered the background I wasn't rendering any area that would later be drawn to anyway.
Ergo, I am never painting the same pixel twice.
Woo! I feel smart right now. 
To err is human. Fortune favors the monsters.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
