4 ms·
No one would call crayons and comic books bullshit, because they are artistic mediums where the expression can stand by itself, has the intrinsic value of being
by rektide 14y ago
No one would call crayons and comic books bullshit, because they are artistic mediums where the expression can stand by itself, has the intrinsic value of being expressive.
Yet in CS there are very smart people such as Alan Kay and the Constructivist types such as former-OLPC now-Sugar, all screaming about how we're learning brain-dead languages on machines doing their worst to make it impossible to become useful and literate without a ten year breaking in period until we become journeymen codesmiths. These machines & languages are not trying to help all of us become fluent about what it is that is running: they are there so that those who already know the language and the program can continue advancing it, until it's shippable, at which time it will execute: when we say learn to program, more often than not we mean learn to fit yourself in to that production cycle.
I'm not trying to argue one way or another about the learning to code merits, but it's important not to think of coding as this completed worthwhile thing in the way we do it! OP is an example of systems research to allow us to create agency in systems: that is programming, coding of behaviors, and one who gets good at it has gained a coding literacy. Ditto for spreadsheet wizards!
My point is that we are free to build entirely new forms of literacy both akin and unlike the programming languages we have now, and that the one's we have now are arbitrary. And, judging purely from the size of assumed knowledge passable programmers rely on, I'd contend, as do others, we'd do a lot better at making a literate society with different languages and forms, more tailored to introspection and mirroring their behaviors than towards producing a running application artifact: if we want people to learn systems, make the systems be more about being learnable and meddle-able than about being execution engines. It's our agency we need to see reflected, and IFTTT and OP are great examples of coding where seeing our agency at work at the end is far more of a direct path: it is radically different than how programming today works, in a good, different and fundamentally very important way.
In leaving, I'll point to a perspective on these better machines: these are machines that build agency by way of using APIs of other machines. I'm convinced that machine to machine interface is the key to making programming not suck, not a drain for this planet, for those who would be composers of code. rektide's gentle suggestion- machine to machine systems interfacing is the way to beget human/machine interface.
- lifeisstillgood 14y agoThank you. In the spirit of understanding, can I try to summarise your points as I get them 1. Programming as it is currently practised is still very focused on implementation / procedural. 2. Anyone who uses a DSP / other system to perform a task they want (agency) is doing some form of programming, and that is valid, as it is a step on the path of literacy. 3. The path of literacy might not be towards the current endpoint of neckbeards and Assembler and 10 years to be good. 4. There is likely to be new languages, new systems that will enable people to do programming / achieve agency at different points and with different degrees of abstraction 5. Its Lisp isn't it :-) I agree with you. Which tells me I may have misunderstood! But I am perfectly happy to agree that some form of code literacy is a good thing, and that the language of the future has not yet been invented I am also quite prepared to believe. Aw, hell, it is Lisp :-) Edit: I like the idea of OLPC etc being about how to meddle. I suspect that the machine you are referencing might be the one in Nand2Tetris - an interesting project that takes undergrads from Nand gates through to compilers and languages on a virtual machine interpreting the CPU built from the interpreted Nands.
- anigbrowl 14y ago2. Anyone who uses a DSP / other system to perform a task they want (agency) is doing some form of programming, and that is valid, as it is a step on the path of literacy. Well, it's the path to literacy in signal processing (or whatever domain it happens to be). I learned to code >25 years ago and I still sort of like doing small things in assembler or throwing something together quickly in C. But I really don't like dealing with collections of big lengthy text files for projects of any magnitude. It's like reading a description of a painting that begins in the top left corner. Put another way, text is the problem. Why, I ask myself, don't IDEs automatically generate dynamic flowcharts? Why do I have to spend so much time typing to create structure, when I want to focus on algorithms? Have a look at this software, which is aimed at roboticists but has other applications; it has modules that let you drop into Ruby as needed (and there's another version that allows entry of C or assembler) but doesn't require you to work that way if you don't need it. this is what an IDE ought to look like.
- 14y ago