The Story of a Unicorn
We are often asked to tell about how we prepare the articles for publication, how we work on them, come up with the ideas and who is the one that draws this cute unicorn. Today we decided to tell you one of these stories.
Our colleague, Sergey Vasiliev, has recently published a new article on the source code check of .Net Core (CoreFX) libraries performed by the PVS-Studio static analyzer. In the article, he examines the code parts that were detected by the tool: errors, suspicious code pieces and those fragments that he got interested in for some reason. And like a true programmer, he did not just search and analyze them, but also reproduced the bugs in practice. As you can see, a lot of work has been done and I am sure that you will find a lot of useful information in the article and see yourself that Sergey did a good job. Now we would like to speak more about the part that was done by Galina, our designer. We do not usually talk that much about the inner workings of our marketing department that she works at but this case is a special one.
When programmers write articles, they ask the designer to draw some pictures to the topic. Most often, they already have specific ideas of what they want or describe the picture as they imagine it (or just send memes). Once the picture is drawn, it needs to be approved by the manager and then inserted into the article. It was supposed to be the same way this time but something went wrong. At some point, Sergey asked Galina to draw a unicorn that would express the following emotion: ¯\_(ツ)_/¯.
“No problem”, — thought Galina and drew it.
And then the fun begins. Colleagues who saw the picture said that it was nice but something was wrong or missing. Suddenly Galina’s inner artist switched to a protective mechanism, which is well known as five stages of grief (or five stages of acceptance of the inevitable). What’s the big deal, you’d think? Just change the picture and that’s it! And she did …
Stage 1. Denial
“Well, if the picture is nice I shouldn’t change anything. I’ll just make the neck look a bit shorter”.
Stage 2. Anger
“What do you mean shoulders should be higher? How much higher? IS IT HIGH ENOUGH?”
Stage 3 and 4. Bargaining and Depression
“Shoulders are not good enough and neither is the neck but everyone liked the original version. Ok, if I draw the neck like this can I make the shoulders lower then? I’d rather draw 150 sketches, just don’t make me change those shouldeeeeeeeeeeeeeers…”
2 minutes later:
“What is this all about? It will lead to nothing good anyway”.
Stage 5. Acceptance
“This is not bad. I kind of like it. What about you?”
As a result, everyone was satisfied with the last picture and after four shots, Sergey had this cute unicorn in the article and the marketing specialists left with fewer nerve cells J
By the way, in addition to useful information for true programmers, you can find some new unicorn pictures in Sergey’s article. Let us know if you want to read more articles like this and we will prepare something interesting for you.