Setting a Bad Example
In my line of work I read a lot of technical articles. Many of them are published in official web sites of big companies. Every now and then I come across an article containing code examples that make me realize how well-rooted bad practices are in our industry.
Take for example this article. The two code examples it presents are cluttered with bad practices such as meaningless variable names and inline conditional statement in a method call. A developer reading this might consider such writing to be acceptable. After reading many similar examples in different articles, a developer might unconsciously (or consciously) adopt these practices.
Anyone writing an article should take responsibility for the education of her readers. This is especially true for big companies publishing numerous articles a year and reaching millions of developers. This is an important (although implicit) way to change code writing patterns (or anti-patterns) in our industry.
