Logic-based Knowledge Different from Factual, Procedural

http://msdn.microsoft.com/en-us/library/aa480020.aspx

Facts (e.g. data in a database retrieved via CRUD) and procedures are good fit for computers and typical programming languages. But there's a "semantic gap" when it comes to knowledge which is better coded using rules engines.

So much for business logic being intrinsic to OOP domain objects?

On using reflection to decouple modules

https://www.simple-talk.com/dotnet/.net-framework/designing-c-software-with-interfaces/

Provides a good argument for the use of reflection to enforce separation within the software architecture.

Programming Language Categorizations

In "Static vs. dynamic typing of programming languages" author compares languages in three spaces:

Statically typed vs Dynamically typed (e.g. Java vs Python)

Strongly types vs Weakly typed (e.g. Python vs Perl)

Manifestly typed vs Implicitely typed (Java vs Python?)

JavaWorld on "The ultimate superclass"

http://www.javaworld.com/article/2105982/core-java/java-qanda-the-ultimate-superclass-part-1.html#tk.rss_all
talks about shallow vs deep cloning, covariant return types, etc.