3 ms·
There's no such thing as "no code". There's just interfaces which are more-or-less capable, and more-or-less intuitive. Any time you define a set of instruction
by Wowfunhappy 7y ago
There's no such thing as "no code". There's just interfaces which are more-or-less capable, and more-or-less intuitive. Any time you define a set of instructions for a computer to execute, you are creating code.
We use Scratch at my Girls Who Code club. It requires students to consider branching paths, and data types, and asynchronous execution. It does not require the students to type, but thank god for that, because they're 9 years old and type at approximately 1 words per minute.
Scratch is still code just like Java, and Lego Mindstorm's EV3, and Automator, and IFTTT. Not all of these systems are Turing complete, and each one contains different restrictions in an attempt to stop users from shooting themselves in the foot: Java doesn't have manual memory management, Automator doesn't have conditionals, and IFTTT is limited to a single trigger and action. But there're still code. Users of these tools need to carefully consider input and edge cases, and test and iterate to see if the code is doing what they intended.
IMO, the primary reason "professional programmers" type their code is because once you know what to type, keyboards are fundamentally faster than mice. That's also why Excel power users frequently rely almost entirely on keyboard shortcuts, and why the command line for an experienced user is often faster than a GUI.
---
Edit: BTW, for the same reason that HTML isn't a programming language, I don't consider most "website builders" to be code, even though I do consider IFTTT to be code.
Code in this context means creating instructions for a computer to follow. Laying out elements on a page (which then adapt to different screen sizes based on predefined behavior) is just that, laying out elements.
I don't know about you, but I can feel myself entering a "coding mindset" when I load up IFTTT—it's simpler than writing Javascript to be sure, but it's the same type of brain muscle, and there's no avoiding it.
- satyrnein 7y agoThis made me wonder: which side would other activities fall on, if event handling was the defining characteristic of "code"? Not code - Excel, SQL, HTML, CSS Code - Email inbox rules, IFTTT. Alarm clock?
- jimbokun 7y ago> Not code - Excel, SQL, HTML, CSS > Code - Email inbox rules, IFTTT. Alarm clock? All of those are code, just varying in their level of Turing-completeness.
- Wowfunhappy 7y agoHmm, y'know what, I'm now reconsidering that part of my post. Setting an alarm clock is definitely not coding. All the instructions are built into the clock: if (currentTime == alarmTime) { soundAlarm(); } All the user does is set the value of alarmTime, a single variable. But, what if the user can choose from a set of alarm sounds? I feel like that's still not coding, but I also can't describe how it's different from IFTTT. There's a spectrum here for sure—any time you interact with a computer, you're giving it instructions. I was thinking about this in terms of the mindset required. When I volunteer at GWC, there's a very specific skill that I see the students coming to grips with over the course of the class. I don't have a word to describe it.
- satyrnein 7y agoYeah, I was thinking of the alarm clock app on your phone rather than a hardware clock by the bedside, so you're practically hitting "add rule, set trigger, define action" much like IFTTT or email inbox rules. When I've taught (adults) some basic coding, it's typically been state that's the challenging concept. You have a bunch of logic, but what was the state of your program (or the world) when the logic executed? If it's not what you expected, how did it get into that state? These questions seems fundamentally different to me compared to working on an Excel spreadsheet (which of course can still be complicated and have bugs).