When does automation become coding? (My response to Atwood)
workingsoftware.com.au
workingsoftware.com.au
The guy in blitzlang (something) does programs as XML that only convert to text as a "view", so you can see the same "code" as a variety of syntaxes just as you can, say, change icon size in a file manager.
The very word is tricky: Code. Like in cypher? Like in codex (book)? Like in instruction code?
Once you take algorithm out of the hardware realm, then how can we really say which code is script and which is real? Every single thing that ends up in github has been algorithmically transformed. Isn't a config file a Domain Specific Language? Why not? And could we not say an endless stream of mouse-pointer coordinates together with clicks is just as code: Non-executable data that has somehow to be "compiled"?
Just random musings...
Many people who write scripts in Perl, Python, Ruby, etc. call themselves coders.
But if they were tasked with writing in assembly or C they could not do it.
And how do we know Atwood himself can even do it.
Show us Atwood's C programming and let's have a look.
It's probably full of security holes.
Many people who write code in C, Ada, Pascal, etc. call themselves programmers.
But if they were tasked with writing machine instructions or even assembly they could not do it.
And how do we know throwaway63-90 himself can even do it.
Show us throwaway63-90's machine code and let's have a look.
It's probably full of security holes.