That's fine, but it seems like the target audience of the article is the people who hope to become the next Van Rossum. It might even be aimed at people decidi

That's fine, but it seems like the target audience of the article is the people who hope to become the next Van Rossum. It might even be aimed at people deciding whether their team at work should pursue a new language for some specific task. Maybe this could be solved with a special badge that tells people which of the Three Tribes of Programmers you're writing for... For purely toy projects, I'm not sure if any code blog advice at all is that helpful, except possibly "Make stuff really small if you want to impress other programmers". Best Practices don't apply the same way to this kind of thing, since in a real industry project the best practice would probably be "Just don't".