In order to answer this question, we must first examine the term "social justice" and establish its meaning. "Social Justice," although a concrete definition is never really given when its used in conversation, can be described as complete economic equality for all individuals who are members of that society. Through Communism, this is essentially achieved when money is collected and evenly distributed to everyone by the government. Marx believed that the right to own private property did not exist, because property and money was generated by work that everyone did; Thus, the rich few should not be able to profit off of the work of others, while still paying them the minimum wage acceptable for them to exist. Under communism, individuals would be free from long working hours due to increased automation. Then, they would be free to pursue their creative passions. In addition, it would eliminate the division between workers and owners, and make the means of production common, rather than privately owned. This would get rid of scarcity and would allow people to focus on the social aspects of their lives, and not fight for survival. The capitalist state would be rendered useless, and everything would be decided not by public institutions but by a true democratic process.
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