draft syllabus statement on code, plagiarism, and generative AI: spencergreenhalgh.com
@spgreenhalgh I wonder if you are doing them a disservice by forbidding use of LLMs and specifically Code Interpreter. In my own teaching, I want students to experiment with these tools as I believe they will be in common usage going forward. I want them to understand the strengths and limitations. Ethan Mollick has been worth following on this topic, for example: www.oneusefulthing.org/p/the-hom…
@agilelisa To be clear, I’m not forbidding these tools so much as discouraging them! I’m sympathetic to your perspective, and I’m going to work generative AI into a content management class on similar grounds; this data science class is for real beginners, though, and I think they need more programming experience before they can evaluate strengths and weaknesses.
@spgreenhalgh Yes, and I agree that we should learn the basics before turning our work over to the tool (see also kids and calculators). But the tools are evolving so quickly, see Mollick again “Things that took me weeks to master in my PhD were completed in seconds by the AI, and there were generally fewer errors than I would expect from a human analyst. Human supervision is still vital, but I would not do a data project without Code Interpreter at this point.” www.oneusefulthing.org/p/what-ai…