Announcer: Now for quick hits and commentary on software development topics from around the web, the EIP web-ring brings you the stigmatized spawn of a refactory, MoffDub, and Helltime!
- Ray Chen recounts the old new thing about garbage collection and has an unusual take on the definition. Garbage collection is considered to be the simulation of infinite memory. I suppose that makes sense from your program’s point of view, and I guess from the program author’s point of view: you get to write code as if you had an infinite amount of memory and never had to clean up after yourself. Ray uses this concept to draw the bottom line: don’t assume anything about the timing of garbage collection, particularly of your finalizers in .NET.
- The offering at simple-talk on database version control by Mike Mooney is epic, and very worth the read. Predictably, I am not aware of any version control of our databases at my place of work, and I certainly never did any version control on The Project’s SQL Server. While it seems silly, this post is good at breaking down the essential differences between code and data that make versioning the latter a non-trivial task. Interesting that he concludes, like I have, that developers should have their own, private, isolated copy of the database.
- Ending the Helltime show is a cautionary don’t-reinvent-the-wheel chide from the folks at ElegantCode.com, pleading that you don’t write that millionth XML parser and just use something built-in. The methods cited seem slightly involved, and maybe that is how it is for parsing. In particular, I don’t like how the classes are usually written for you, but if they are just data structures, what’s an extra layer of mapping between friends? John Sonmez never did cover building XML, but I will in a post in the near future, since the problem is currently my main focus at the old cube farm. Stay tuned.
|Announcer: You’re reading the EIP web-ring.|