In this episode you'll learn a bit about the current state of art with AI and playing computer games.

I try to find the most difficult academical paper on the topic and start from there.

Sometimes it happens - what to do now?

It can actually be both! But usually feature toggles are a better option

Event sourcing helps with providing the historical context.

The blogpost I'm talking about: http://blog.arkency.com/2017/02/how-to-unit-test-classes-which-depend-on-rails-models/

Link to my book about blogging: http://blog.arkency.com/blogging/

Sometimes it's hard to decide which way to go in the project.
2 techniques which help here:

1. Timeboxed experiments
2. Reversible decisions

You can hard-delete an object, you can also use a boolean flag "deleted", you can use a datetime field called "deleted_at". You can also have a record per each deletion. Finally, you can just use events.

What's best?

Collective Ownership + Small Stories + Single Backlog + Take the first task from the top

Those techniques help you achieve the milestone in the project, where you're able to work on any part of any system.