问HN:针对三年级学生的软件开发入门第二代课程

6作者: xrd25 天前原帖
我去年发过一条帖子,请求帮助为三年级学生创建软件开发的介绍: “下周我将进入我女儿的课堂,教授软件工程。我想让他们了解其中的魔力。” https://news.ycombinator.com/item?id=42056775 最好的建议是: “我经常想起PB&J的演示。” 这非常受欢迎!我采纳了很多建议,并且玩得很开心。我要为我的四年级和五年级班级再做一次,并希望能得到一些改进的建议。 去年的几个亮点: * 我带了一把锯齿刀和一些番茄酱包。当他们说用刀把果酱涂在面包上时,我握住锯齿的一端,假装我的手指流血(番茄酱非常适合作为血液)。 * 我带来了凡士林,也就是石油胶。当他们说把果酱涂在面包上时,我大声思考:“好吧,你们说的是果酱,而这个上面写的是果酱!” 我还提议把三明治送给一个幸运的孩子,但令人惊讶的是,没有人愿意接受这个用花生酱、凡士林和番茄酱做的三明治。现在的孩子真是太娇惯了,6-7岁! 今年我想再做一次。但我想添加一些想法: * 团队合作的重要性:我认为这区分了优秀的软件团队和糟糕的团队。 * 良好沟通的重要性:我在考虑教他们沟通和计划的重要性。去年我准备了一些纸条,请不同的记录员写下指令,然后我根据班级的意见重新排序,再采取行动。但也许我可以在这方面深入讲解,让他们真正理解计划和良好书面沟通的价值。 * 经理角色:我在考虑谈谈经理通常薪水最高的原因,因为他们负责所有的动态部分,以及项目的成功或失败。我预计这可能会在HN上引发争议! 有什么建议吗?
查看原文
I posted this last year asking for help in creating an introduction to software development for 3rd graders:<p><pre><code> &quot;Next week I&#x27;m going into my daughter&#x27;s classroom to teach about software engineering. I want to teach them about the magic of it.&quot; </code></pre> https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=42056775<p>The best suggestion was<p><pre><code> &quot;I think about the PB&amp;J demo a lot.&quot; </code></pre> It was a big hit! I took a lot of the suggestions and had so much fun. I&#x27;m going to do it again for my 4th and 5th graders classes and could use some help in improving it.<p>A few highlights from last year:<p><pre><code> * I brought a serrated knife and ketchup packets. When they said put the jelly on the bread with the knife, I gripped the serrated end and pretended my fingers bled (ketchup works great as blood). * I brought in vaseline AKA petroleum jelly. When they said put jelly on the bread, I contemplated aloud &quot;Well, you said JELLY, and this says JELLY!&quot; </code></pre> I offered to give the sandwich to one lucky kid afterward, but surprisingly, no one took me up on the opportunity to eat a sandwich with peanut butter, vaseline and ketchup. Kids these days are so spoiled, 6-7!<p>This year I want to do it again. But, I want to add some ideas:<p><pre><code> * importance of teamwork: I think this differentiates good software teams from bad teams. * importance of good communication: I was thinking about teaching them about how important communication and planning is. Last year I had slips of paper where I asked a different scribe to write down the instructions, and then I took those, reordered them with class input and then took action. But, perhaps I can expand on that and really drill into them the value of planning and good written communication. * managers: I was thinking about talking about how the managers are often the best paid, because they take responsibility for all the moving pieces, and the success or failure of the project. I expect this might be a controversial take here on HN! </code></pre> Any suggestions?