I'm David, a UK based senior software developer. I work for a UK insurance group where I do analysis and development primarily on the .NET technology stack. Here you will find information about me, my blog, skills matrix and portfolio.
When I'm releasing updates to a database I will release to a pre-release schema before dropping the live objects. Afterwards I will then change them over to the new schema. This is a sample script of how to change the owning schema across.
When trying to configure web deploy you may experience a crash when trying to configure a user for webdeploy.
I've carried out a minor release of Smart Approve to improve the backward compatability between Windows Server 2012, and previous operating systems.
There is a new beta release of Smart Approve which is to deal with an issue introduced by Microsoft when releasing Windows Server 2012. Normally I wouldn't be openly critical of other developers, but this highlights a key issue in compatability through unnecessary change.
I've produced an update, which includes a contribution that never got released last year, and attempts to deal with some UAC issues when running on Windows Server 2008 R2. This release is marked as a beta, as it's had a lack of testing around the issues I'm trying to resolve.
In an age where we encourage users to have secure passwords that are unique to each site they are using. It irritates me when major companies or sites insist on rules for passwords that don't allow for complexity in passwords. A major UK telecommunication's provider has a requirement that passwords must be no longer than 15 characters. One domain registrar went through a period of insisting passwords were exactly 8 characters in length!
I've touched in the past about the weakness of advert quality control in the likes of Google AdSense. If you look at the likes of download sites like sourceforge, cnet or gamefront you will see image based adverts looking like download links. These "generic" adverts link to downloads containing spyware or malware.
While watching the coverage of the formula 1 Chinese Grand Prix a couple of weeks ago, Sky Sports ran a segment where they aired tweets on screen displaying the username. The username caught my attention because of the work I do in developing processes to cleanse and match customer details. The username in question contained the person's date of birth.
Recently I've been reading a lot of "experts" on sites like Stack Exchange saying that De-normalised data structures are better than Normalised data structures for performance. The simple fact is you should know the business problem and the data before making any recommendations; and someone should test the impact of their design on large chunks of test data. A system with a few hundred rows will act very different from a system with a few hundred million rows in. End of the day you need a system that can work in a business as usual environment with no maintenance just to stop it falling over.
I've released a new version of WSUS Smart Approve after an issue was reported with the way the config file is processed. As I stated to the person who reported both the problems this week, I would rather have the tool working properly than have people not using the tool because of problems with it.