问 HN：面向三年级学生的第二代编程入门课程
6 分•作者: xrd•8 个月前
我去年发过这个帖子，寻求帮助，为三年级的学生创建一个软件开发入门课程：
```
“下周我要去我女儿的班级，教他们软件工程。我想让他们了解其中的神奇之处。”
```
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> "Next week I'm going into my daughter's classroom to teach about software engineering. I want to teach them about the magic of it."
</code></pre>
https://news.ycombinator.com/item?id=42056775<p>The best suggestion was<p><pre><code> "I think about the PB&J demo a lot."
</code></pre>
It was a big hit! I took a lot of the suggestions and had so much fun. I'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 "Well, you said JELLY, and this says JELLY!"
</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?