Originally posted by creekster
View Post
As a progammer, I am also a Deist of sorts. The gospel is an abstract class. The scriptures define certain abstract methods in that class like abstract void LoveYourNeighborAsYouself(). The Church is the instantiation of that abstract class and all abstract methods are required to be implemented, such as void LoveYourNeighborAsYouself(). Now how that method is implemented is the imperfect result of the programmers... e.g. the collection of leaders over the last 170 and some odd years. That method can call other stuff like List<MonthlyReports> DoHomeTeachingEveryMonth() at one point in its revision history, or it can call stuff like List<QuarterlyReport> GoMinisterToYourFamilies() - doesn't matter. The point is not really what is contained in the implementation of the abstract method, but the fact that the method has been implemented in some way. The person that authored the abstract class created a blueprint. The author included many abstract methods therein. The author doesn't give two shits how the method gets done (e.g. implemented), just GET IT DONE - and don't tell me about how you did it (void).
I view the Corp of the Church in that same way. It is man's best instantiation of the Gospel class. At the surface, it looks clean and utilitarian with nice sounding methods and a cool, clean interface. But feel back the layers and you find kludges and imperfections and pages and pages of if ... else if... else if... else statements (using cuddled curly braces FFS!). The implementation will never be perfect and it is perilously stupid to think so. Just log it as a bug, patch up the code to prevent it from occurring in the future, and move on.
Comment