This comes across to me as more of a rant, than a constructive exit description from a company. When hiring new candidates, and doing background checks alarm bells would go off if I saw people whining about their previous jobs in a blog post. Be professional, accept that some jobs are shit, and find a new one. This post will do you no favours in the future.
There has to be some sort of balance between criticism and "maintaining a professional attitude" (whatever that phrase means -- I have never understood it). A lot of times "be professional" is used to silence criticism of truly horrendous software development practices.
Being forced to use a stack of horrible software including IE strikes me as a perfectly valid professional criticism. Possibly, this might be because I worked at another company (also in the mobile space) that had exactly this sort of atmosphere of bureaucracy and using a contrived, corporate software stack for their development teams.
I don't have a company of my own right now, but if I did, I would have no problem hiring someone who ranted about an environment that is toxic to good software development. (I guess I would prefer it if he also gave an instance where he tried to improve that environment and failed, but from experience I know that it often tends to be a futile endeavour.)
So what? It does a good service to future prospective employees by spreading information about what it's like to work there. It's like saying that citizens under oppressive governments should never speak up because doing so can only land them in jail.
This is exactly what I was going to say. Writing a blog post riddled with grammatical errors (and emoticons!) slagging off your former employer is not a good look as far as future employers are concerned.
The grammatical errors could be due to English as a second language. I'm not sure that part of the requirements of working for Samsung in Poland is a flawless grasp of the English language.
Are we honestly that concerned with formality in this industry? I'd be more concerned with the contents and less with how formal they are. And what is wrong with using emoteicons in personal blog posts?
I don't necessarily agree with slagging off your former employer but his criticisms are still valid. The only thing that I didn't like was: "First of all I did this because this job was terrible boring for me (fixing code of other people is not especially exciting)." - That's not perhaps the best thing to write since he was a junior and this will make some people think he is lazy and does not want to take on the less fun jobs that we all have to do from time to time.
And like someone pointed out, English is not his first language. I'm sure you just didn't notice that though. :)
