Blood, sweat and pixels (Blood, sweat and pixels)

Year. 3 Last weekend, I read this book, Jason Schreier, and it was surprisingly good. Maybe it's because these ten stories remind me too much of a job. Or the thing is that stories about the heroic overcoming of numerous problems by game development teams are perceived as a happy epic. (Except for the StarWars story. 1313)Which kind of hints that your problems are just a warm-up:) Or maybe this book is perceived by me as a way to dive into the world of games, the gate of which I closed more than a decade ago. Interestingly, I haven’t played any of the games in the book:) This led to the loss of some of the impressions of the story about the content of the games. But I know the concept of crunch. For example, a 3-month crunch at an unnamed startup where I worked before Tinkoff:) And who just three years ago, after years of torment, stopped playing a bad dancer who was getting in the way. In this case, the startup got rid of the interfering, according to the founders, part, namely the development team. I think that's the solution.

Read Blood, Sweat and Pixels and enjoy it. In this book, both a workaholic and a gamer will find something for themselves. The main thing is not to succumb to the romantic description of the profession of the creator of games and not to go headlong to fork games.

#Software #SoftwareDevelopment