If a manager asks about documentation, say: “I use mental architecture.” Nobody dares to…

If a manager asks about documentation, say: “I use mental architecture.” Nobody dares to ask again

(c) Georgy Kryukov ( @Shark_0909 ), author of the book “Fuck Safety”

Last night after the meetup, I sat down in a cafe, took dry white wine and... completely read the book “F*ck Security” 📖

In fact, the book is only 91 pages long, making it an extremely quick read. And since this is the case, I thought that I haven’t done a book review on this channel for a long time ( last was already in February ) 🫡

The book uses the approaches of reverse psychology, as well as those known to everyone "Bad advice" Gregory Oster. We are, as it were, immersed in an insecure development team and given recommendations on how and what exactly to remove the **** from application security ( These are the puns today ). It all starts with theses like “there is no point in maintaining documentation and testing the product before release” and ends with what excuses to use if everything goes wrong ( at the end there is even a checklist on how to quit gracefully in this case ) 😎

In some places the book is quite fun to read due to the increasing absurdity of the recommendations, but sometimes you can’t help but feel existential horror when you realize that the author literally described the current situation on the market. This especially applies to the seventh chapter about the endless beta test. This is where you begin to understand the author’s main argument that “The main thing is to get it out quickly, and don’t care about everything else” . A huge number of large companies strive to roll out the product as quickly as possible, neglecting everything else. There’s Apple Intelligence, and a bunch of Microsoft products that have always been chasing speed rather than quality at the start. 😵‍💫

At the same time, the author himself mentions at the beginning of the book that there is no need to take this too seriously, because the work is primarily about something else. There is a more humorous and humorous approach here, rather than a dystopia. And here, perhaps, is the main nuance that can ruin the entire impression of a book: it is very important in what mood you start reading it 🤔

If you are extremely serious about all things security, don't understand post-irony, and are crazy about memes, this book is not for you. Here you need to read -> laugh -> learn a lesson about what you definitely shouldn’t do. Don't take everything too personally 😭

Stylistically, the book is written approximately like posts in the tg channel ( Well, I write in a similar way, on Sunday in any case ). Some people will like it, others obviously won't. For me personally, this is not a minus, but I can’t call it a big plus either. I prefer the clear separation between the book and online posts 📖

There are typos in the book ( I have already written to the author about several ). This is just a fact, there is nothing to comment on here ✏️

Subjectively, I rate the book 7/10

The book came out very well. If we add to it, and in some places revise the presentation of the material a little, I’m sure something even cooler could come out. Decent for a debut book 🆒

I wish George not to rest on his laurels and continue to develop in a creative direction)

#book_review
#information_security
@ever_secure