1,146 karma · joined August 11, 2011
1988–1994 54.9
1999–2000 64.1
2001–2002 65.6
2003–2004 66.5
2005–2006 67.3
2007–2008 68.3
2009–2010 69.2
2011–2012 69.0
2013–2014 70.7
It's mesmerizing to scroll around looking for circles in the ocean. And then to spend all night reading depressing wikipedia articles about past behavior of the US government.
I recognize that this is not immediately an empirical claim, but I will observe that discarding it offhand in favor of the equally ideological dominant interpretation would be exactly the dynamic I'm pointing out.
What is the right amount of fuzzing for a news organization to perform on leaked documents, to protect a source while providing credible evidence to support a claim?
Meral, H. M., Sevinc, E., Ünkar, E., Sankur, B., Özsoy, A. S., & Güngör, T. (2007, February). Syntactic tools for text watermarking. In Electronic Imaging 2007 (pp. 65050X-65050X). International Society for Optics and Photonics.
Beginners want to make something happen. Like making alert windows pop up or (oooh!) modifying the text on a page. For these kinds of things, you actually don't need to know any of the underlying mechanisms. You just need to know that you put an id attribute on the thing you want to mess with and match it in the script. Similarly, throw the script at the bottom of the body, tell them to keep it there, and dispense with $(document).ready(). I haven't done the research (yet), but my experience tells me it's best to start people off somewhere in the middle of the ladder of abstraction, high enough that you can do something interesting right away, but low enough that you have some sense of the mechanism.
For beginners, brevity contributes to simplification. I used to write explanatory comments in scripts I gave my students. But their eyes don't parse the comments effectively, and therefore they perceive the comments as extra complexity. For this reason also, I would stick with jQuery.
But I'd love to find out. Anyone teaching intro CS who has time to run a comparison?
There are a huge number of ed-tech apps and products being developed with the intention of "teaching X to code," but they mostly seem to fit into a taxonomy of approaches that was already in place 30 years ago. Approaches such as interfaces where syntax errors are impossible (Scratch), toy worlds that present puzzles to solve (Karel the Robot), or full-power programming languages that are fundamentally oriented toward teaching by providing graphical feedback on program execution state (Swift).
I'm curious about others' sense of what's really new, but am not very interested in saying novelty is good or bad as compared to working on a previously identified approach. I thought Bret Victor's DBX talk (http://worrydream.com/dbx/) was an interesting exploration of this space.
I don't see much substantial disagreement between the OP's post and the comments here--she's basically making three points:
1. The (secondary) education system's role is to show students how to engage with the field, not tailor their training to the specifics of a job posting. It's more important that students be able to pick up new paradigms than it is that they know any particular language.
2. Education is iterative. It's ok to learn something that fudges the details or that's not a best practice if it means you're making things now. We all return to domains of knowledge with finer granularity when we need it.
3. Content knowledge is important for teachers, but their expertise is in pedagogical content knowledge--the knowledge and skills of how to productively open a domain to new learners.
Do we disagree about any of these? Sure, there's some unnecessary heat in the post. But that's true of the comments here too. I wish some folks here were able to bring more introspection and empathy to conversations about education (yielding insights about who they are as learners, and how others are different). And I wish we stopped dumping on teachers as the source of all our problems (let's talk more about why this is happening later...), so teachers didn't have to feel resentful and defensive in public fora.
If you're interested in CS education and you haven't spent any time in a classroom/after school club/coder dojo, I'd invite you to come get some firsthand experience. I teach in Palo Alto, come on over...
Or is that about as ethical as spiking trees to prevent illegal logging?