Though we often focus on the firestorm it ignited against slavery in the United States, Uncle Tom's Cabin had a huge influence outside of its country of origin. According to David Reynolds' book covering the impact of Uncle Tom's Cabin, called Mightier than the Sword, Stowe's novel helped inspire revolutionary movements in Russia, Brazil, China and Cuba. Because of uncomfortable parallels between Southern U.S. slavery and serfdom in Russia, the book was initially banned in Russia, though people were able to get copies in French and German--and after the czar freed the serfs, it was available in Russia. It influenced Russian revolutionaries such as Lenin and radical reformers such as the writer Leo Tolstoy. It was, according to Reynolds, the number one bestseller across Europe in the nineteenth century. Charles Dickens, whose novels often focused on the plight of the poor in industrialized England, wished he had written the novel and Queen Victoria wanted to meet Stowe, although she was advised against it, due to Stowe's "radicalism." Overall, the book is the poster child for how a work of literature, through arousing emotions, can have a outsize influence on political life and hence history, particularly, in this case, movements that fought for the liberation or increased rights of oppressed peoples.
As a software engineer, I need to sometimes describe a piece of code as something that lacks performance or was not written with performance in mind. Example: This kind of coding style leads to unmaintainable and unperformant code. Based on my Google searches, this isn't a real word. What is the correct way to describe this? EDIT My usage of "performance" here is in regard to speed and efficiency. For example, the better the performance of code the faster the application runs. My question and example target the negative definition, which is in reference to preventing inefficient coding practices. Answer This kind of coding style leads to unmaintainable and unperformant code. In my opinion, reads more easily as: This coding style leads to unmaintainable and poorly performing code. The key to well-written documentation and reports lies in ease of understanding. Adding poorly understood words such as performant decreases that ease. In addressing the use of such a poorly ...
Comments
Post a Comment