Before I lodge my criticism: the kid's right. DNS blocking has always been a non-solution to the "kids screwing around on school computers" problem. When I was

Before I lodge my criticism: the kid's right. DNS blocking has always been a non-solution to the "kids screwing around on school computers" problem. When I was his age, we'd pull up breadfish.co.uk on all the computers in a single pod in the library, then un-mute all of them at once. They blocked breadfish, but then we just started pulling it up on youtube. 1:1 ed tech (e.g. chromebooks) probably exacerbates the problem because kids have a single machine that's their own. They can customize it as they please, for better and worse. When I was his age, my school's thin clients would wipe most of your customizations every time you logged out. For the handful of standalone desktops, you'd still have to set stuff up on each machine individually. This limited the effectiveness of the various tricks we played to get past IT guardrails. I think the title is a little misleading, though. The essay details why DNS-level blocking doesn't work in educational environments. The title suggests it'd talk about why ed-tech fails in a more general case. Remember, projectors, document cameras, VHS players, and Smart boards were all red-hot tech at some point. Even today, ed-tech is more than just computers assigned to kids.