« May 2005 | Main | July 2005 »

Notable Links

Posted by: David Carroll

Top Ten Reasons Why It's Cool to be a Calvinist

Posted by: David Carroll

First let me say this is a joke. I'm reprinting this from Jolly Blogger

  1. Calvinists tend to wear wool and cotton. Dispensationalists tend to wear lime-green polyester leisure suits.
  2. John Calvin was French...being French is very chic.
  3. Calvin sounds like Calvin Klein...and his clothes are very chic.
  4. Calvinists can drink.
  5. Calvinists can smoke.
  6. Dispensationalists are into prophecy conferences where they talk about Star-Trek eschatology and the mark of the Beast. Calvinists have conferences on "life and culture", art, social justice, and other high- brow things like that. Afterwards, we go to the local pub and talk about philosophy over a pint of Bass ale.
  7. Calvinists have close ties with Scotland and Scotland is very cool: you know --Sean Connery, the movie Highlander, Bagpipes, the Loch Ness Monster, Glenlivet 18 year old Scotch, the movie Train Spotting, Brave Heart, etc.
  8.  Calvinists think we are smarter than anybody else.
  9. It is more socially acceptable to say, "I go to Grace Presbyterian Church" than to say, "I go to Washed In The Blood Worship Center", "I go to Sonlife Charismatic Believers Assembly", or to say "I go to Boston Berean Bible Believing Baptist Bethel", or to say "I go to the Latter-Day- Rain Deliverance Tabernacle Prophecy Center, Inc.", or to say "I go to the Philadelphia Church of the Majority Text", or to say "I go to the Lithuanian Apostolic Orthodox Autocephalic Church of the Baltic union of 1838".
  10. Ultimately, I am a Calvinist because I had no choice in the matter.

Disturbing observations about Purpose Driven Life

Posted by: David Carroll

Did you know that Purpose Driven Life was the second best selling book of all time? Here are some thoughts from someone whom I respect theologically:

  • This book is theologically naive, revealing little understanding of the law, divine grace, human depravity, redemption from sin, justification, sanctification (holiness), the nature of saving faith, or the lordship of Christ.
  • The Bible talks about how God fulfills His purpose through believers; it's not about Him helping us fulfill our purpose. (Romans 8:28, for example, describes Christians as those who are "called according to His purpose.")
  • In fact, Jesus called people to self-denial, not self-fulfillment. The notion of "self-fulfillment" caters to human pride and self-will, which Scripture says is sin.
  • But Rick Warren seems to think whatever you want to be is what God wants you to be ("God wants you to be yourself"—p. 103).
  • Scripture does not teach that God accepts people unconditionally in the sense Rick Warren seems to think.
  • True worship, service, sharing, and most of the other things described in The Purpose-Driven® Life are not possible at all apart from salvation. So why not give the gospel more clearly?
  • The true gospel is a message about redemption from sin, not "purpose in life." The most essential features of the gospel message are the cross of Christ and the truth of the resurrection. (Neither is given much emphasis—I don't recall that the resurrection is mentioned at all—in The Purpose-Driven® Life.) The cross is where sin was atoned for, and the resurrection is the proof Christ's atonement was accepted as payment in full for the sins of Christ's people. You haven't preached the gospel at all if you neglect those truths.
  • In short, this is basically feel-good stuff, carefully packaged to make a message that is appealing to unspiritual people. Other than that, the audience is ambiguous, and the gospel message is tamed, toned down, and obscured. The hard issues that were the most outstanding features of Jesus' message—sin, repentance, self-denial; not to mention the vital themes of righteousness, judgment, atonement, and the world to come—are all completely missing from Rick Warren's presentation.
  • The Purpose-Driven® Life epitomizes what is most wrong with the shallow, anti-theological, a-biblical message being proclaimed from most "evangelical" pulpits today.

From Phillip Johnson's blog

Visual Studio Tools for Office

Posted by: David Carroll

The basic architecture is simple. Excel 2003 and Word 2003, upon loading a document, check for two custom properties in the document: _AssemblyLocation0 and _AssemblyName0. If these properties are found, the host application loads the Visual Studio Tools for the Microsoft Office System Assembly Loader (Otkloadr.dll). This unmanaged DLL is responsible for loading the assembly that you created using Visual Studio Tools for the Microsoft Office System. The loader uses the document's custom properties to find the document's assembly, loads the assembly into memory, examines some metadata, sets up references between the host and the assembly, and then steps out of the way.

If you change the Assembly Link Location property or the name of the assembly and then rebuild your project, the _AssemblyLocation0 and _AssemblyName0 document properties will be updated during the build process. However, the build process will not update the security policy to reflect your change; security policies are updated only during the initial project creation. So, if you change either the Assembly Link Location or the assembly name, you will need to update your Microsoft .NET security settings to reflect the new file name or location.

You should also make note of the project's Copy Assembly property. If Copy Assembly is disabled or set to False, the build process will not copy the assembly to the link location. When you change the project's Assembly Link Location to a network path, the Copy Assembly property is automatically set to False. Likewise, when you change the Assembly Link Location to an HTTP path, the Copy Assembly property is disabled.

from: Smart Client Developer Center Home and Visual Studio Tools for Office

Design Smells

Posted by: David Carroll

From Agile Software Development, Principles, Patterns, and Practices by Robert C. Martin

Design Smells, the odors associated with rotting software.

  1. Rigidity - System is hard to change in even the most simple ways.

  2. Fragility - Changes cause system to break easily and require other changes.

  3. Immobility - Difficult to entangle components that can be reused in other systems.

  4. Viscosity - Doing things right is harder than doing things wrong.

  5. Needless Complexity - System contains infrastructure that has no direct benefit.

  6. Needless Repetition - Repeated structures that should have a single abstraction.

  7. Opacity - Code is hard to understand.

via David Hayden