Such a great point from @sheena at the #pycon education summit: our students aren't learning in the same environment we did! Things that were obvious to us, like Sheena's example of learning return vs print in a compiled language, may no longer be NEARLY so obvious in the tech stack our students are actually learning!

I used a similar example in my #nbpy talk this year, where my students expect that clicking "no" on a modal will block them (because during their tech journey it often has!). I love this generalized observation, though.

So many student empathy problems could be anticipated by considering in advance how your students' environment differs from the environment you learned in.

It's been a few weeks since #NBPy 2026, and now you can watch all the talks we recorded, and relive all of the scheduled parts of an amazing weekend.

Linky link: https://www.youtube.com/playlist?list=PLaeNpBNgqQWsb59zqc_mng1OqG9XdFCiH

RE: https://social.coop/@cwebber/116528868052029156

Just as review, and testing (to an extent), and actual development methodology have become optional for many teams, so too is writing code that you actually understand.

Unrelatedly, watch my talk from #NBPy
(https://www.youtube.com/watch?v=d7AeWFbOTHg)