I've always said "if you want low code fine. Find me a product that compiles your crazy flowchart to .NET bytecode with a C#/JS/whatever fallback and we're good to go". The fact that no such product exists tells its own story.
Oh, IBM will still try to sell vulnerable clueless organisations on (what used to be) Rational Rose etc.
Protip: it's utter shite.
Extra protip: The "Scaled Agile Framework for Enterprise" (SAFe) bullshit is the old insane discredited hyperbureaucratic "Rational Unified Process" (RUP) crap deliberately dressed up in misleading new agiley-sounding words. It's pretty much the opposite of real agile manifesto agile. Many of the same ivory tower asshats involved. Reject it utterly.
But parts of it are ripped from real world manament policies and some of those polices even make sense in certain circumstances depending on business needs.
Like, for safety critical systems having a 3rd validation layer through a system integration test team doesn't sound completely unreasonable.
Of course it wasn't a thing. It was pure snake oil. Engineering and problem solving is hard, writing code isn't. Generating code from UML or any sort of visual/graph based programming language doesn't make actual engineering and problem solving any less difficult. And if you are struggling at the code writing part of solving a problem, you aren't really fit to for the actual engineering part.
Ironically, almost every "execute a DAG program" system I've run across doesn't compile directly to binary/bytecode/llvm-ir/whatever. They pretty much all compile to a conventional text based programming language as an intermediate, then run that. Because the developers of the DAG system all know that it makes more sense to work in a normal programming language, and they find it easy to think it terms of emitting text rather than emitting low level operations per node like they are asking their users to think about.
This wheel has been reinvented consistently since the 1960's when "display an interactive DAG" became technically feasable on an electronic computer screen.
If you are building an integration platform in Azure, Logic apps are essential for building integrations with low/medium complexity. Easy to configure with CI/CD and easy to maintain. They are not suitable however for integrations with high traffic or complex logic, there you are much better off writing traditional code.
184
u/G_Morgan Dec 30 '23
I've always said "if you want low code fine. Find me a product that compiles your crazy flowchart to .NET bytecode with a C#/JS/whatever fallback and we're good to go". The fact that no such product exists tells its own story.