I find that I procrastinate most about the tasks I dislike doing, and I think it's likely that is true of most people. Therefore, one of my most successful methods of dealing with procrastination is to first do the task that I least want to do. This has two advantages. First, the task I have procrastinated about is done, and second, for the rest of my day, I do not have that task hanging over my head, draining my energy and making me feel guilty about what is undone. For example, when I practiced law, I never minded doing research and writing briefs, but I hated to write boilerplate complaints and answers. So I always got those out of the way. Now that I teach, I find that I dread having to grade handwritten work, as opposed to work that is typed. I do the handwritten quizzes first and then reward myself with the typed quizzes. When you have schoolwork to do, first do the work you like the least. You will be amazed at how much more productive you are.
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