Entity Framework Web Application Deployment

In retrospect, this seem painfully obvious, but when you deploy your Entity Framework web application, I would recommend that you script your database from SQL Management Studio as opposed to selecting "Generate Database from Model..." in the Visual Studio .edmx context menu.

Yes, I made the mistake of using the model generated SQL to create my production database, but it was a very small project and I had not gone into SQL Management Studio once during coding...

Happy Coding

What I wish I read a decade ago

In the field of software development two types of developers seem to be working their hardest to destroy you application and push back your release date. The first is the "Copy and Paste Kid", the second is "Over-Generalizing Gerry". The Copy and Paste Kid has never heard of functions or constants and makes numerous humorous mistakes. Over-Generalizing Gerry is the evil "genius" who will destroy your code-base by over-engineering you application into oblivion. Watch out, he'll leave no stone unturned because he will either try to anticipate every future situation imaginable or make sure your application conforms (insert buzz word paradigm) religiously. If you let your local evil "genius" gain too much self-confidence he might even try to create his own language or language extension! Pshhh, what the heck did the creators of JavaScript know?

The frustrating thing about talking to even a mild Over-Generalizing Gerry is he will often confuse you with the Copy and Paste Kid! I've finally found an article that articulates perfectly why there is an "over" in "over-generalize". I myself have been guilty of over-engineering all too often; that's why I wish I had read this article a while ago: Tips for maintainable Java code.

The preceding article is probably the best I have ever read as far as good practices outlines go. It applies to any language, not just Java.