Web Forms Model Binding Part 1: Selecting Data (ASP.NET vNext Series 3)

http://weblogs.asp.net/scottgu/archive/2011/09/05/web-forms-model-binding-part-1-selecting-data-asp-net-vnext-series.aspx

Frameworks making developers dumb

http://sivalabs.blogspot.com/2011/08/frameworks-making-developers-dumb.html

"I strongly believe frameworks will increase developer productivity. But the developers should try to understand how the framework is doing the stuff. You need not learn all the internal working mechanisms of frameworks. If you are really good at Servlets and JSP then it is very easy to understand any Java Web framework like Struts, SpringMVC etc.If you aren't good at the basics then obviously for every other question reply would be.. "framework's annotation/xml will execute this" 

Code Refurbishment

Code refurbishment is the better word than refactoring for business side. 




A code refurbishment is worthwhile to correct the core domain if it's about to undergo significant further development, or if a module is business critical and needs to be occasionally corrected under production pressure to preserve revenue generation.



http://mechanical-sympathy.blogspot.com/2011/08/code-refurbishment.html

How Facebook Ships Code

http://framethink.wordpress.com/2011/01/17/how-facebook-ships-code/

Where OO has succeeded most

http://www.johndcook.com/blog/2011/04/29/where-oo-has-succeeded-most/

I believe he overstates his case when he says it has been difficult to show benefits of OO outside graphics and simulation. But I agree that it’s harder to create good object oriented software when there isn’t a clear physical model to guide the organization of the code. A programmer may partition functionality into classes according to a mental model that other programmers do not share.

When you’re developing graphics or simulation software, it’s more likely that multiple people will share the same mental model. But even in simulation the boundaries are not so clear. I’ve seen a lot of software to simulate clinical trials. There the objects are fairly obvious: patients, treatments, etc. But there are many ways to decide, for example, what functionality should be part of a software object representing a patient. What seems natural to one developer may seem completely arbitrary to another