%3Fxml version="1.0" encoding="UTF-8"%3F>
I recently had a massive problem on one of my client installations. The system was live, and one of the pages that they had previously not been using started to get used. This page, as it turned out, had a huge number of memory leaks. SQL Server started choking, and before I knew what was going on, my customers had been completely locked out of their database. The real issue was that I hadn’t done an upload to the live system in over a month. This meant that the development version of the application had over a month’s worth of changes in it that had not yet been fully tested and could lipitor online be pushed to Live. If it wasn’t for subversion, I would have been completely screwed.
Here’s how I fixed the problem. I checked out the latest copy of the codebase to a folder on my computer. Then I updated to the revision of the codebase that was committed *just* before my last upload to Live. Then I worked on that codebase, fixed the problems, recompiled and replaced the Live system with the fixed version.
I had the problem fixed in a couple of hours thanks to this awesome tool that never gets in my way and is always there, working, when I need it. So, yeah. Subversion? I’m a fan.
]]>Clarke was and a visionary writer. If you haven’t read it yet, I suggest you check out my favourite science fiction book of all time: .
He will be sorely missed…
]]>