I absolutely hate no-code systems.
-
I like only such systems which I have developed myself. Even then, I can rarely remember how to use them.
You did document them, right? No? Well there you go....
-
and yes I know I am speaking to the choir here. But I just have to vent. so I am working in this system that is based upon data and everything I am sure is in SQL somewhere in the clouds. but am I allowed to connect with like SQL management studio or heck even some sort of command terminal? Nope! so no SQL select available. You HAVE to use their interface. you have to select the whole table first and then you deselect the fields you dont want then you can apply a where clause it is all a stupid IDE with no way to write any freakin Code! and yes I know THEY "think" and THEY "say" you don't need a tech to do this. But only a real tech can actually figure it out. So the no code is less than useless because you actually haven't eliminated a tech job. You have just made it harder.
To err is human to really elephant it up you need a computer
The great thing about no-code systems is that you create more coding jobs. What about AI? Well, someone has to code those systems too. The problem is like you found, the interface layer will drive a tech-minded person insane because these tools are not made for us. They are made for and sold to managers who spent time in a marketing seminar watching a few examples that were perfectly crafted for the data. They pay incredible amounts of money for a tool that doesn't require health insurance and think they are saving a bundle. Suddenly there's a job opening for a SharePoint/App manager, and too often, it ends up being some non-tech-minded ex-business manager and friend of the HR lady you can't stand that suckered their last organization into moving everything to the cloud...and they need to hire some fakers - "tech-minded" assistants - to actually do the work, and they bother you all day because they can't figure out how to Google.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
-
and yes I know I am speaking to the choir here. But I just have to vent. so I am working in this system that is based upon data and everything I am sure is in SQL somewhere in the clouds. but am I allowed to connect with like SQL management studio or heck even some sort of command terminal? Nope! so no SQL select available. You HAVE to use their interface. you have to select the whole table first and then you deselect the fields you dont want then you can apply a where clause it is all a stupid IDE with no way to write any freakin Code! and yes I know THEY "think" and THEY "say" you don't need a tech to do this. But only a real tech can actually figure it out. So the no code is less than useless because you actually haven't eliminated a tech job. You have just made it harder.
To err is human to really elephant it up you need a computer
I'm actually working on building a no-code tool for our staff to use for custom reports for our customers, and I'm trying to avoid "... only a real tech can actually figure it out" at all costs. I am putting a great deal of effort into making it make sense and be easy for those with little to no clue about SQL to be able to generate these reports without having to go into the db themselves or waiting for us to do it for them. I wonder if I can do it - make it easier/quicker for those who are uncomfortable with SQL, and maybe no harder nor slower for us. I'm giving it my best shot.
-
You did document them, right? No? Well there you go....
A simple readme file, plus example scripts.
-
and yes I know I am speaking to the choir here. But I just have to vent. so I am working in this system that is based upon data and everything I am sure is in SQL somewhere in the clouds. but am I allowed to connect with like SQL management studio or heck even some sort of command terminal? Nope! so no SQL select available. You HAVE to use their interface. you have to select the whole table first and then you deselect the fields you dont want then you can apply a where clause it is all a stupid IDE with no way to write any freakin Code! and yes I know THEY "think" and THEY "say" you don't need a tech to do this. But only a real tech can actually figure it out. So the no code is less than useless because you actually haven't eliminated a tech job. You have just made it harder.
To err is human to really elephant it up you need a computer
Yeah, many of these are a joke, just as you describe. The vendors oversell the systems, showing shiny examples of working systems neglecting to tell the potential customers that they were either built out by the vendor, at a silly cost, or built by customers who threw their IT department at the project. I actually sat in on a zoom meeting where I had to explain the SQL to the vendor. I turned off my video and audio after a while and explained it to my dog sitting next to me. She at least tilted her head; which beat the blank stares from the vendor's so-called SA and Dev. :omg:
-
and yes I know I am speaking to the choir here. But I just have to vent. so I am working in this system that is based upon data and everything I am sure is in SQL somewhere in the clouds. but am I allowed to connect with like SQL management studio or heck even some sort of command terminal? Nope! so no SQL select available. You HAVE to use their interface. you have to select the whole table first and then you deselect the fields you dont want then you can apply a where clause it is all a stupid IDE with no way to write any freakin Code! and yes I know THEY "think" and THEY "say" you don't need a tech to do this. But only a real tech can actually figure it out. So the no code is less than useless because you actually haven't eliminated a tech job. You have just made it harder.
To err is human to really elephant it up you need a computer
This makes me thing of a soldering project from a while ago. It came with a couple pushbuttons and an instruction sheet on how to get stuff done with those pushbuttons. Not exactly impossible, far from that, but I found that digging through the code & uploading a custom binary to the MCU is sooooo less hassle than controlling this thing with the buttons.
-
and yes I know I am speaking to the choir here. But I just have to vent. so I am working in this system that is based upon data and everything I am sure is in SQL somewhere in the clouds. but am I allowed to connect with like SQL management studio or heck even some sort of command terminal? Nope! so no SQL select available. You HAVE to use their interface. you have to select the whole table first and then you deselect the fields you dont want then you can apply a where clause it is all a stupid IDE with no way to write any freakin Code! and yes I know THEY "think" and THEY "say" you don't need a tech to do this. But only a real tech can actually figure it out. So the no code is less than useless because you actually haven't eliminated a tech job. You have just made it harder.
To err is human to really elephant it up you need a computer
"Working as intended". Companies sell this stuff to those in charge who don't know any better. They sell it as a way to "not require actual techies to manage, selling the idea that the company will save money by not needing to hire full techs. Instead they can hire low level techs that don't really understand how things work. The higher level techs that actually understood everything got tired of being locked out of making improvements and left for a company that values their skills. All the time, the vendor is pulling the company in deeper the more systems they set up for them. Eventually the company is left with nothing but low level techs that only understand the cookie cutter system that the company is now locked into paying for. With no way to innovate and adapt. Companies beware. You want to be successful, hire smart people that understand the system and can design the system you need to continue being successful.
-
You seem to assume it's SQL Server, but it may not be, and even if it is it may not be next year. If you code against the database directly your work will break when the data is moved, to another server, another database system, or whatever. I imagine the system designers want to prevent that. The system is not there for your convenience, it's there to benefit the business and you are presumably engaged for your professional skills in working with it. Why not suggest improvements to the interface that would simplify matters, instead of ranting that it doesn't suit your skill level? If you can show how much time and cost they would save, you might find them welcomed....
What you are saying may be right on some level. The OP wants to vent. Let’s let him do that. And why don’t you pull your lip over your face and swallow.
-
Problem is, that it's not less work (as it's meant to be), just less flexible
Wrong is evil and must be defeated. - Jeff Ello
-
Problem is, that it's not less work (as it's meant to be), just less flexible
Wrong is evil and must be defeated. - Jeff Ello
...and less efficient in development and performance. PowerBI and DAX are perfect examples.
-
You seem to assume it's SQL Server, but it may not be, and even if it is it may not be next year. If you code against the database directly your work will break when the data is moved, to another server, another database system, or whatever. I imagine the system designers want to prevent that. The system is not there for your convenience, it's there to benefit the business and you are presumably engaged for your professional skills in working with it. Why not suggest improvements to the interface that would simplify matters, instead of ranting that it doesn't suit your skill level? If you can show how much time and cost they would save, you might find them welcomed....
I think the heart of the problem is all these "no code" systems, fully commit into themselves and leave no room for traditional coding or scripting. I can't stress how much I hate "Flow" and "Power Automate" because of this. These systems need to be more like the Office/VBA marriage. Sure... you can do some mighty complex stuff in Excel... and spread your calculations and sub-calculations across multiple columns and worksheets and everything... BUT... if you know how to write some VBA code, you can do all that work in a macro much faster. Traditional Excel for the "benefit of businesses" and the "code" side for the power users and developers.
-
and yes I know I am speaking to the choir here. But I just have to vent. so I am working in this system that is based upon data and everything I am sure is in SQL somewhere in the clouds. but am I allowed to connect with like SQL management studio or heck even some sort of command terminal? Nope! so no SQL select available. You HAVE to use their interface. you have to select the whole table first and then you deselect the fields you dont want then you can apply a where clause it is all a stupid IDE with no way to write any freakin Code! and yes I know THEY "think" and THEY "say" you don't need a tech to do this. But only a real tech can actually figure it out. So the no code is less than useless because you actually haven't eliminated a tech job. You have just made it harder.
To err is human to really elephant it up you need a computer
I think that is the basic problem with these "no-code" platforms. They all assume that whatever data they need is a ready for them, all packages up with a bow on top. The reality is most data is a mess, or wasn't designed for this particular set of views that the no-code app is expecting. You still need someone to apply a set of views or similar to pull in meaningfull data in a format that makes sense for that particular application. I do not see developers losing their jobs over no-code systems. Maybe our hair from pulling it out in frustration.... 😜
-
"A little time, a little trouble, your better day" Badfinger
Which went back to coding in ILE. Ah the joys of RPG calcsheets.
-
and yes I know I am speaking to the choir here. But I just have to vent. so I am working in this system that is based upon data and everything I am sure is in SQL somewhere in the clouds. but am I allowed to connect with like SQL management studio or heck even some sort of command terminal? Nope! so no SQL select available. You HAVE to use their interface. you have to select the whole table first and then you deselect the fields you dont want then you can apply a where clause it is all a stupid IDE with no way to write any freakin Code! and yes I know THEY "think" and THEY "say" you don't need a tech to do this. But only a real tech can actually figure it out. So the no code is less than useless because you actually haven't eliminated a tech job. You have just made it harder.
To err is human to really elephant it up you need a computer
Vendors have been trying this nonsense for years with the hopes that something will work to allow them to acquire a large share of the development market. It has never worked and never will. Users simply do not have the training to handle technical details as we do. But idiots will keep on trying until this fad goes the way of all the others...
Steve Naidamast Sr. Software Engineer Black Falcon Software, Inc. blackfalconsoftware@outlook.com
-
and yes I know I am speaking to the choir here. But I just have to vent. so I am working in this system that is based upon data and everything I am sure is in SQL somewhere in the clouds. but am I allowed to connect with like SQL management studio or heck even some sort of command terminal? Nope! so no SQL select available. You HAVE to use their interface. you have to select the whole table first and then you deselect the fields you dont want then you can apply a where clause it is all a stupid IDE with no way to write any freakin Code! and yes I know THEY "think" and THEY "say" you don't need a tech to do this. But only a real tech can actually figure it out. So the no code is less than useless because you actually haven't eliminated a tech job. You have just made it harder.
To err is human to really elephant it up you need a computer
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! :-)
-
I assume you code exclusively in assembler, to preserve 'flexibility'?
I prefer IBM System\360 Machine Language, entered via toggle switches, one for each bit.
-
and yes I know I am speaking to the choir here. But I just have to vent. so I am working in this system that is based upon data and everything I am sure is in SQL somewhere in the clouds. but am I allowed to connect with like SQL management studio or heck even some sort of command terminal? Nope! so no SQL select available. You HAVE to use their interface. you have to select the whole table first and then you deselect the fields you dont want then you can apply a where clause it is all a stupid IDE with no way to write any freakin Code! and yes I know THEY "think" and THEY "say" you don't need a tech to do this. But only a real tech can actually figure it out. So the no code is less than useless because you actually haven't eliminated a tech job. You have just made it harder.
To err is human to really elephant it up you need a computer
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.
-
and yes I know I am speaking to the choir here. But I just have to vent. so I am working in this system that is based upon data and everything I am sure is in SQL somewhere in the clouds. but am I allowed to connect with like SQL management studio or heck even some sort of command terminal? Nope! so no SQL select available. You HAVE to use their interface. you have to select the whole table first and then you deselect the fields you dont want then you can apply a where clause it is all a stupid IDE with no way to write any freakin Code! and yes I know THEY "think" and THEY "say" you don't need a tech to do this. But only a real tech can actually figure it out. So the no code is less than useless because you actually haven't eliminated a tech job. You have just made it harder.
To err is human to really elephant it up you need a computer
Just wait till they discover COBOL. Anybody can read or write COBOL code (even managers) because it's in human language! :laugh:
-
You seem to assume it's SQL Server, but it may not be, and even if it is it may not be next year. If you code against the database directly your work will break when the data is moved, to another server, another database system, or whatever. I imagine the system designers want to prevent that. The system is not there for your convenience, it's there to benefit the business and you are presumably engaged for your professional skills in working with it. Why not suggest improvements to the interface that would simplify matters, instead of ranting that it doesn't suit your skill level? If you can show how much time and cost they would save, you might find them welcomed....
Migrating to a different DB would mean re-writing the SQL anyway, plus possible changes to the interface as well. I don't see how removing the ability to work directly with SQL would help with this, unless the people using the system can't be trusted with SQL (in which case, maybe there are bigger problems). I also don't get how you can design the structure and indexing on a DB without knowing how the data is going to be used.
-
Reminds me of the report generator in CR, or the venerable BizTalk or any number of systems designed to move the coding to the power user, not just a waste of time by the bane of any developer.
Never underestimate the power of human stupidity - RAH I'm old. I know stuff - JSOP
Now that reminds me of a time we (my boss) thought to do the same. The project was scuttled after we tested the proof of concept on fellow employees and managers. They couldn’t/wouldn’t do it, so we decided against rolling out to clients. :(( :)
Time is the differentiation of eternity devised by man to measure the passage of human events. - Manly P. Hall Mark Just another cog in the wheel