Why do some developers feel the need to capitalize everything in the database? It just looks ugly…

Not to mention the inconsistency here with some database tables being named using singular representations and others named using plurals.
Why do some developers feel the need to capitalize everything in the database? It just looks ugly…

Not to mention the inconsistency here with some database tables being named using singular representations and others named using plurals.
Taking on new maintenance projects is always a bit scary, especially with those asp.net projects where the code is compiled and can’t be completely seen beforehand (though it’s sometimes possible to get an idea using Reflector).
It’s a little more worrying when the existing developer says to the client:
[The code] is completely as-is, with no warranty whatsoever and no suggestion that it is fit or otherwise for any particular purpose, and a hold-blameless clause in all eventualities.
Nice. This seems like one of those cases where the developer has lost interest in the project, doesn’t particularly need the work anymore, and wants to get rid of it without accepting any liability for the work done.
On the upside, at least the project is relatively small…
Just saw this when loading up Winamp:

The bloat in new versions of Winamp is getting ridiculous. Mp3 blog and remote access?! No thanks.
Maybe it’s time to try this Winamp alternative, as recommended by a commenter in this post, though it does look a little too basic.
The best software change I’ve made has to be moving from Adobe Reader to FoxIt PDF Reader which is much, much better than Adobe’s bloatware.
I’ve been using VisualSVN for a few weeks now, and found it to be an excellent Visual Studio plugin which does exactly what it says on the tin. The VS integration makes it a lot easier to use SVN for source control (rather than having to alt+tab back to Explorer and use TortoiseSVN).
Since Jeff’s post about supporting small software vendors makes a lot of sense, when my free trial expired a couple of days ago, I decided to grab a copy, and started what is probably one of the crappiest experiences I’ve had buying stuff online (second to WorldPay, who have the top spot).
For reasons unknown, VisualSVN are using ShareIt.com (a division of Digital River) for selling their software. This is what I’ve had to go through so far to try and buy a license:
So, I’ve used two paypal accounts with two different payment methods, as well as trying to use my credit card directly, and still haven’t managed to buy a license successfully.
If VisualSVN/ShareIt.com could make the process any more painful, I don’t know how. In the Internet-age where it’s easy enough to do real-time credit card processing and with systems like Paypal in place, buying a $49 software licence could (and should) be as simple as entering Name & Email, signing into Paypal to make payment and receiving a license key by email within a couple of minutes.
If anyone from VisualSVN is reading this, please change your payment process. I really expect a better buying experience from a company selling software (especially when it’s good software!).
Update – 05 November 2007: Emailed sales yesterday, explained what I was going through and then tried to buy a license again. Unsurprisingly, got an email this morning from ShareIt.com yet again declining my order. Also heard back from someone in sales asking me to share my best experience of buying software on the web (though no mention of any discount for all this trouble I’ve gone through, or even offering another way to pay). WTF. All I’m asking for is a system that *works*. I’m really starting to believe these folks don’t want to sell their software!
Update – 06 November 2007: After trying for a fourth time to buy a license, and having heard nothing back from the sales team for 2 days, I’ve given up. It’s simply not worth the hassle dealing with them. If the sales team can’t be bothered to reply to someone who has tried to buy their software four times, then there’s something very wrong.
Just wrote a new article on CodeProject with information on how to manage sessions ending when using a StateServer other than InProc, which don’t fire the Session_End event.
Check it out:
ASP.NET HttpModule for handling session end with StateServer