C# Automatic savepoint

[Mkane08]

Hello,
I started a game development business, and we are very close to our first game release. We chose a written choose-your-own-adventure type of game, but one of the things we're going to add is a savepoint. Our game is as non-linear as possible and the choices branch out like a family tree, complete with deaths and failures, and every set of choices (I.E: Choice 1.1 leads to 2.1 and 2.2, 2.1 to 3.1 and 3.2, so on so forth.) is where we want to place a savepoint. What would we use to create an automatic save system that keeps track of their choices on a 1 by 1 basis? as I said its non-linear and a small choice can lead to entirely new story arcs, so it's important that they're able to go back to any decision they've made

 

[Antero360]

A software development team mlsdev blog can include a generalist and a specialist. A generalist specializes in a wide range of technologies while a specialist specializes in a narrow area. A generalist team is a good choice for a team that needs to work together on all aspects of the project. This type of team also has an added advantage: a strong alignment of culture and character. A generalist team is more likely to be productive than a specialist team.

Can you elaborate a little more on your thoughts? You seem to be a bit biased, giving some good qualities for a generalist team, but fail to point the counterparts on the specialist team. How do the qualities of a specialist team make it the less favorable in your eyes?