An AntiPattern is a common practice in solving problems with a bad solutions. (In comparison to a Amelioration Pattern, which turns a bad solution into a good one.)
In programming the Liferro framework, identifying bad practices with an objective eye can be quite difficult, but having a library of bad practices to draw from aids in solidifying a stable framework which is valuable in the next generation of software subscription services.
Typical AntiPatterns can manifest why a bad solution looked attractive at the time, and why the implementation didn't quite live up to expectation. They can also indicate appropriate patterns that can used in its place.
So why should you care about an AntiPattern? Well, AntiPatterns are common software mistakes which help to identify an alternate solution easily. The collective experience from years of software project experiences as well as numerous cited works of these bad practices, help developers eventually produce quality code. In the end, users and developers benefit from this collection of known common bad practices called AnitPatterns.
The Liferro framework is built on best-practice development, and is always wary of AntiPatterns. The consistent vigilance and correction of these AntiPatterns helps keep the Liferro framework flexible and extensible.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment