Back when all lessons had to run in a single file, it made perfect sense to hide boilerplate code. Particularly given that we couldn't guide learners to the salient part of the code like we can now.

However, this comes with downsides. A curious learner cannot easily access this code to experiment with it and there's potential for weird bugs when they accidentally do. Also, as we expand the kinds of lessons we want to write, it's starting to feel more and more like tech debt.

I ran into this recently when trying to support multifile React lessons - the head (--before-user-code--), contents (user's code) and tail (--after-user-code--) ended up being compiled into the same module three times, each overwriting the one before. The end result being the user code was lost, replaced by the tail. I can work around this, but it illustrates the kind of problem they cause.

If there's a still a solid reason to keep the head and tail around, that's okay. If not, I think we can save ourselves some future pain by getting rid of them.