Error Driven Development Tutorials

Draft Notes 1

This is what I'm calling an "Error Driven Tutorial". Lots of steps will produce an intentional error so you can see what they look like, and then the next thing will be to fix it in an incremental way. This is done to help show how the parts fit together and to get used to seeing error messages that you'll be seeing during dev in general.

This is also done to address the thing that often happens to me in tutorials where there are instructions to do several things before seeing anything change and when you finally get to the part that's supposed to work it throws a weird error that's hard to troubleshoot because you don't know what step produced it.

Draft Notes 2

Error Driven Development

Getting a new app set up for content takes several steps. Lots of tutorials do all the steps before looking at any pages. The idea being that you'll make it to the finished version with no issues. That's rarely been the case in my experience. So, we'll be taking a different approach. We're going to look at each step one at a time. This will result in seeing a bunch of different error messages as we make progress.

There are two big benefits to this approach: