How Small Businesses and Organizations can Manage Open Source Components


Why You Should Read This Article

Wainstein explains how to implement each step, and provides caveats and hazards to consider at each step. The article is similar to something on WikiHow or in the Dummies book series; Wainstein takes a complex issue, and simplifies it to make the issue solvable for lay people.

Additionally, Wainstein leaves the steps open-ended, but provides enough information to make the caveats and hazards easily searchable. This way, readers can apply her solutions to their specific needs, and find the resources they need to succeed. Lastly, Wainstein’s article is concise and organized. Wainstein has a fabulous, cookie-cutter essay outline, which makes it easy for the reader to follow. Wainstein introduces the topic, supports her thesis, and concludes the article. Although essay formatting is taught in most schools, it is rarely perfected; Wainstein’s article is close to perfection.


The article’s link contains “5-best-practices-for-managing-open-source-components,” but the article lists seven reasons; this is a bit sloppy, but Altexsoft may not update URLs after the initial article has been published. Another issue with the article is the conclusion. Wainstein’s introduction and body are thorough, and provide the reader with lots of details. The conclusion, however, is very short and does a poor job summarizing the information provided in the introduction (mainly, her hypothesis) and body of the article.


  1. Is it normal for websites to keep the same URL if the article is updated?
  2. How often are guest writers featured on company blogs?
  3. Why does Altexsoft choose an independent writer when they could use their own writers to implement Altexsoft’s products and solutions into the article?