Jamie Taylor

That's probably not even a version of Ruby, but let's say we are, right?

We're using Ruby version 2.6, and then it will go, cool, I will do a web search for Ruby 2.6 ORM best practices and Ruby 2.6 Stripe compatibility and Stripe documentation for this particular version of Stripe, right?

So then it grabs all of that information, does all of that research ahead of time, the same stuff that you or I would do if we were doing it, right?

We get to the point where we're about to implement the Stripe API, and we go and read the API and go, all right, yeah, that's how we do it.

We need to have a client ID and maybe an OAuth token or whatever, right?

And then what will happen is it does that all ahead of time.

It stores that in the plan.

And then when you come around to breaking that plan into tasks by running the task command, it looks at the plan and goes, cool, I think there's about 70 tasks there.

And it breaks it down into individual things.

So like create this Ruby file that represents the controller.

Excellent.

Now install the package.

Excellent.

So then it's like piecemeal steps.

Like you would a junior developer, right?

You would ask a junior developer to do this one step at a time.

Create the controller.

Now create, add the package to our, I think it's a Ruby gem lock file or something like that, right?

And then we write a test to make sure that if we're doing test-driven development, write a test to make sure that it works, but it's going to fail because, and then it actually says in the test step, this step will fail because we haven't written the code yet.

So then it gets to that point.