Quick Update. Upcoming Post.

I haven’t posted much for a bit due to some heavy commitments with a fantastic client, however I’ve pulled an old post out of the drafts — essentially the long-delayed part III of the high performance SQL series from eight years ago — and will finish it up imminently.

It is tentatively titled “The Absolute Minimum Every Developer Should Know About Indexes“, and includes a demonstration database that you can run in PostgreSQL.

On other matters, occasionally I look at the sorts of traffic that bring people here, and I’m always amazed at some of the Google search results. Not only that Google sends so many people here, but in how incredibly obsolete technologies hang on.

A frequent search hit, for instance, is regarding the internet provider for Visual SourceSafe. I’d authored a piece almost a decade ago, it being mangled in the moves between various blog engines, but somehow it still yields some search juice.

To which I would say: People still use SourceSafe? With all of the incredibly powerful options freely and easily available, they’re still working with that derelict, obsolete, broken source control provider?

Though of course this isn’t entirely surprising. Many teams and shops have an inability to decouple from past decisions, and those things just hang around for perpetuity. How those things usually happen is that a team or company or product gets loaded with more and more baggage, zero effort or expense paid to continuously refine and remove accumulating technical debt, until eventually the solution is so overwrought and broken that the the entire thing is wholesale abandoned. Not as some voluntary choice, but rather the detritus slows it down the point that eventually it hits a breaking point and involuntary actions are taken: The internal team and product replaced with a greenfield product of an outside consultancy, for instance. It is the ballistic arc of so many projects, where necessary choices and actions aren’t taken through the lifecycle, until the problem is so great that abandonment is the only recourse.

Always be re-evaluating the stack that you use. This isn’t a call to blindly follow what is new, but honestly if you’re still using products like Visual Sourcesafe for anything, there is probably an issue.