The Zen of Python, by Tim Peters has been adopted by many as a model summary manual of python's philosophy.  Though these statements should be considered more as guideline and not mandatory rules, developers worldwide find the poem to be on a solid guiding ground.

Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!

There has been and continues to be a plethora of observational studies by different researchers in the publishing industry focused on how e-books have affected hard-copy book sales. Evidence from these studies has indicated that there is a significant and monumental shift away from hard-copy books to e-books.[1]These findings precipitate fears that hard-copy books might become more expensive in the near future as they begin to be less available.  This scenario could escalate to the point where only collectors of hard-copy books are willing to pay the high price for ownership.

The founder of Amazon, Jeff Bezos, made a statement in July 2010 that sales of digital books had significantly outstripped U.S. sales of hard-copy. He claimed that Amazon had sold 143 digital books for its e-reader, the Kindle, for every 100 hard-back books over the past three months. The pace of this change was unprecedented;  Amazon said that in the four weeks of June 2010, the rate of sales had reached 180 e-books for every 100 hard-backs sold. Bezos said sales of the Kindle and e-books had reached a "tipping point", with five authors including Steig Larsson, the writer of Girl with a Dragon Tattoo, and Stephenie Meyer, who penned the Twilight series, each selling more than 500,000 digital books.[2] Earlier in July 2010, Hachette said that James Patterson had sold 1.1m e-books to date.

According to a report made by Publishers Weekly, for the first quarter of 2011, e-book sales were up 159.8%; netting sales of $233.1 million. Although adult hard-cover and mass market paperback hard-copies had continued to sell, posting gains in March, all the print segments had declined for the first quarter with the nine mass market houses that report sales. Their findings revealed a 23.4% sales decline, and that children’s paper-back publishers had also declined by 24.1%.[3] E-book sales easily out-distanced mass market paperback sales in the first quarter of 2011 with mass market sales of hard-copy books falling to $123.3 million compared to e-books’ $233.1 million in sales.

According to .net sales report by the March Association of American Publishers (AAP) which collected data and statistics from 1,189 publishers, the adult e-Book sales were $282.3 million in comparison to adult hard-cover book sales which counted $229.6 million during the first quarter of 2012. During the same period in 2011, eBooks revenues were $220.4 million.[4] These reports indicate a disconcerting diminishing demand for hard-copy books.

In programming, memory leaks are a common issue, and it occurs when a computer uses memory but does not give it back to the operating system. Experienced programmers have the ability to diagnose a leak based on the symptoms. Some believe every undesired increase in memory usage is a memory leak, but this is not an accurate representation of a leak. Certain leaks only run for a short time and are virtually undetectable.

Memory Leak Consequences

Applications that suffer severe memory leaks will eventually exceed the memory resulting in a severe slowdown or a termination of the application.

How to Protect Code from Memory Leaks?

Preventing memory leaks in the first place is more convenient than trying to locate the leak later. To do this, you can use defensive programming techniques such as smart pointers for C++.  A smart pointer is safer than a raw pointer because it provides augmented behavior that raw pointers do not have. This includes garbage collection and checking for nulls.

If you are going to use a raw pointer, avoid operations that are dangerous for specific contexts. This means pointer arithmetic and pointer copying. Smart pointers use a reference count for the object being referred to. Once the reference count reaches zero, the excess goes into garbage collection. The most commonly used smart pointer is shared_ptr from the TR1 extensions of the C++ standard library.

Static Analysis

The second approach to memory leaks is referred to as static analysis and attempts to detect errors in your source-code. CodeSonar is one of the effective tools for detection. It provides checkers for the Power of Ten coding rules, and it is especially competent at procedural analysis. However, some might find it lagging for bigger code bases.

How to Handle a Memory Leak

For some memory leaks, the only solution is to read through the code to find and correct the error. Another one of the common approaches to C++ is to use RAII, which an acronym for Resource Acquisition Is Initialization. This approach means associating scoped objects using the acquired resources, which automatically releases the resources when the objects are no longer within scope. RAII has the advantage of knowing when objects exist and when they do not. This gives it a distinct advantage over garbage collection. Regardless, RAII is not always recommended because some situations require ordinary pointers to manage raw memory and increase performance. Use it with caution.

The Most Serious Leaks

Urgency of a leak depends on the situation, and where the leak has occurred in the operating system. Additionally, it becomes more urgent if the leak occurs where the memory is limited such as in embedded systems and portable devices.

To protect code from memory leaks, people have to stay vigilant and avoid codes that could result in a leak. Memory leaks continue until someone turns the system off, which makes the memory available again, but the slow process of a leak can eventually prejudice a machine that normally runs correctly.

Related:

The Five Principles of Performance

In Demand IT Skills

Structure Rule Language

To aid in the ease of rule authoring, Blaze Software, now Fair Isaac, created the proprietary Structure Rule Language (SRL), an object-oriented programming language designed to enable those with little or no background in software development to pen rules. Although the capabilities of this language are far too extensive to detail in this article, we can examine the basic rule syntax.

Rules in the SRL take the following form:

rule RuleName [at | priority M] is