3 ms·
> Another way of looking at low-code is to take an even bigger step back, and look at the history of programming from the start. Python is low-code relative to
by wiseowise 5y ago
> Another way of looking at low-code is to take an even bigger step back, and look at the history of programming from the start. Python is low-code relative to C++; C and FORTRAN are low-code relative to assembler; assembler is low-code relative to machine language and toggling switches to insert binary instructions directly into the computer’s memory.
That is the most stupid thing I've read in a while.
- not-elite 5y ago> That is the most stupid thing I've read in a while. Arrogance. It takes 10 lines of Python to compute a multiplicative inverse mod p, using arbitrary precision integers. [1] Try doing the same thing with nothing but x86 assembly and Volume 2 of Knuth's AOCP. It's a useful, humbling exercise. [1] https://karpathy.github.io/2021/06/21/blockchain/ https://karpathy.github.io/2021/06/21/blockchain/
- wiseowise 5y agoThat doesn't make it no-code or low-code. It's just a high level programming language that's more efficient at solving one problem than another.
- rvense 5y agoYou're really just arguing about the definition of the word "code".
- Chris2048 5y agoarguably, higher level language use higher level general code features, where-as no/lo-code solutions are using specialised/domain features. This would make them similar to a framework like chef/ansible/puppet that requires a large library of "knowledge" on how to do various things (all written in traditional low/high-level general code).
- fargle 5y agoAgree! I think the problem is twofold. First, it's not "low-code" or "no-code", it's high-level code vs. low-level code vs. non-traditional non-text-based code like labview. But it's still code, there's always the code. Second, learning "code" or "coding" isn't the problem in democratizing "programming" in the first place. Code is the easy part. Software engineering, architecture, debugging & troubleshooting, logic, math, configuration management, project management - that stuff is the hard part. It's of absolutely no help to have a bunch of smart domain-experts happily "no-coding" away in matlab or labview or excel or ms. access and then stumbling right into the same bad engineering practices that you might find in struggling projects using traditional tools. That's because we don't need "coders" or "programmers" at all. We need people to be engineers. And part of good engineering is picking the right tool and system to use, not jumping on the next over-hyped fad.