At first Nag introduces himself to Rikki-Tikki in a way designed to strike fear into the mongoose's heart and to make Rikki feel like a young thing. But Rikki's mongoose nature won't allow him to remain frightened for long, and Nag knows what Rikki knows: that mongooses in the garden mean death for snakes. But in this scene, Nag knows something that Rikki does not at first, and that is that Nagaina, Nag's wife, is slithering up in the grass behind Rikki. Therefore Nag tries to get Rikki into a philosophical discussion about whether it's right for Rikki to eat eggs if it's wrong for Nag to eat birds. He is hoping to distract Rikki long enough to allow Nagaina to strike him from behind. But Darzee sings out with a warning, and Rikki jumps high in the air as Nagaina's strike misses. The next time Nag and Rikki meet, there is no discussion. It's a fight to the death--Nag's death.
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