In Redmod, they know how to prevent good programming

I'm not only working on Java... The worst thing with working with microsoft stuff is probably getting used to it, considering .Net fairly "ok", rediscovering the wonderful Java practices and tools and now going back and forth between Java and the disgusting .Net.

Today, I'm doing some Analysis Services coding. Trying to maintain a piece of web application visualizing data from the OLAP. It has once been written by a DBA, which means most logic was once in the database. Databases are like Excel, they can do to many things and are therefore used for things they weren't supposed to.

However, I tried writing a unit for a constructor implemented enourmous method that I'm trying to split up and test. However, it turns out, it's impossible. ADO MD (OLAP client) is written to be impossible to test, by sealing all its data classes. Trying to find out how the use those classes, I found this page, check the community comment!

It's clear. At microsoft, they detest modern practices so much they go to lengths to prevent them!

Why web developers shouldn't do systems

I stumbled into the google code blog the other day and there was a post about performance improvement for mobile html5.

There was a section about database performance which was just ridiculous. I won't go too deep into this, but I reacted strongly to the suggestion to "Use Triggers whenever possible". With some experience in application maintenance I can recommend this if you will do the maintenance on this application until its end of life. The reason is simple, putting application logic in the database is hard to debug and cannot be versioned in any simple way. So please, don't do this. Microsoft used to recommend similar things (stored procedures instead of OR mapping) and I think they're trying really hard to forget that now.