This saying means that if, as we go through life, our eyes are firmly fixed only on where we are going, we are going to miss our entire lives! Essentially, life consists of all the moments on the way to our various destinations, and when our focus is on the destination, we are not living in these moments. There are many small and large examples of this, literally and figuratively. As I leave my house, I have a destination, the school where I teach. If that is all that I think about on the way, I am missing out on a great deal. I will miss the cherry tree that just blossomed, the eagle that was perched on a rail on the road, some small children playing while waiting for their school bus to pick them up, and so much more. When I get to school, if I am not in the moment, but focused on my next stops, the bank and the library, I will not be in the here and now for my students. When you start college, if all you are focused on is your destination, which is to get a degree, you will be missing out on the entire college experience, which is a wonderful one. Keeping your focus on the moment allows you to be open to the learning, the new experiences, and the friends you will make along the way. When I do set out on an actual journey, I detest using my GPS and usually use a map. Having a voice tell me where to turn all the time keeps me focused too much on where I am going and not on the drive itself. Keeping your eye on where you are going eliminates being open to serendipity, which often brings us our very best experiences. Having a destination is important, to be sure, but if all we do is think about where we are going, we are missing all the riches and joy of our lives.
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