[grantbachman]

Tutorials that actually validate whether they currently work.

One use case would be tutorials on deploying to IAAS/PAAS providers. Deploying always seems to be the hard part after I build something; I don't like using the same language and IAAS/PAAS twice for learning purposes. It's complicated even more so as many tutorials don't reference when they were written or which code versions they used. The site would require this information, and then use it to periodically attempt to deploy that sample to AWS/Digital Ocean/etc (whichever the tutorial is covering), and prominently display whether the tutorial currently works.

[CodyReichert]

I thought about this after scrolling past a couple of times - and I think this is a good idea.

I'm thinking like a CI for tutorials. For example, I create an account on Tutorial CI (or whatever), give it the environment of the tutorial's code. It spits out a badge that I can put on my tutorial that says whether the build is passing or not. Pretty much exactly like the Travis badges you see on Github. That way, someone can verify before they even start reading that the tutorial is valid.

I actually like this idea a lot.

[yaraher]

We've been exploring this kind of scenarios at [http://codepicnic.com], where you can create your tutorial and then run some sort of test to see if it's running (perhaps returning non-zero values from some script or testing the existence of some files) but so far we think most of the attempts are a bit clumsy and would lead to false positives.

But would love to exchange ideas on the topic.