Comments for The Rain and The Shade

Comment on The Broken Window (Maintaining coding best practices in organizations) by windows server

windows server — Wed, 09 Jan 2013 05:32:44 +0000

With havin so much content do you ever run into any issues of
plagorism or copyright infringement? My blog has a
lot of unique content I’ve either authored myself or outsourced but it looks like a lot of it is popping it up all over the internet without my authorization. Do you know any solutions to help prevent content from being ripped off? I’d certainly appreciate it.

Comment on Unit Testing Database driven functionality with ADO.Net Entity Framework Code First by ovaisakhter

ovaisakhter — Tue, 08 Jan 2013 13:20:11 +0000

What you have mentioned may be taken as the crux of my post, we can exactly test the where and joins with this approach. I am not sure if I have mentioned that where and joins are not business logic. If I have then it is a mistake.

Comment on Unit Testing Database driven functionality with ADO.Net Entity Framework Code First by Bob

Bob — Tue, 08 Jan 2013 13:03:24 +0000

How can you not consider ‘joins and wheres’ as business logic? The ‘joins’ defines the relationships between you tables which is business logic. And ‘where’ is used to filter data, and that filter is defined by some business rule (i.e., show me all customers with past due accounts). If you don’t test that the ‘where’ is returning the correct rows, then the rest of your testing stack doesn’t matter.

Comment on Azure Access Control Service Usage Scenario by magic Mesh

magic Mesh — Sat, 22 Dec 2012 04:23:01 +0000

Everything is very open with a precise clarification of the challenges.
It was definitely informative. Your website is very helpful.
Thanks for sharing!

Comment on Visual Studio Add-in for code review by ovaisakhter

ovaisakhter — Fri, 06 Apr 2012 05:51:55 +0000

Thanks for liking the post and your ideas.

I dint wanted to couple this implementation with a particular source control that is why I avoided any interaction with the source control. I am thinking of a good way so that the source control functionality can be injected into this type of tools. Will do a post if I end up doing it.

Comment on Visual Studio Add-in for code review by lalitkale

lalitkale — Fri, 06 Apr 2012 05:04:45 +0000

If we could add date time and source control file version of it that will be awesome. btw, Thanks for sharing the tool. I liked the simplicity of it.

Comment on Visual Studio Add-in for code review by lalitkale

lalitkale — Fri, 06 Apr 2012 05:03:10 +0000

I think along with the same,if we can add ,datetime stamp of review and may be version of file that is reviewed (pull it from vss/tfs/perforce etc..) that will be awesome..by the way thanks a ton for sharing this simple tool..I love the simplicity of it.

Comment on Visual Studio Add-in for code review by Aakif Hassan

Aakif Hassan — Tue, 03 Apr 2012 07:46:31 +0000

i remember myself preparing templates for code analysis and integrating them with TFS with the checkins, that includes standards plus some serious deviations.. but this is all precautions, i agree may be code analysis is not the right candidate for static code review and preparing bug reports, but i think i will give it a try as putting code analysis restrictions on checkins and applying custom rules helped a lot to avoid bad code and people learn as well so it may help us for the reviews as well.

and the biggest task is to identify if people followed the right architecture, right domain , right patterns at times… and that for sure has to be manual regardless

Comment on Visual Studio Add-in for code review by ovaisakhter

ovaisakhter — Thu, 22 Mar 2012 13:33:45 +0000

“We do use static code analysis on our code and use Resharper as well which I am not sure where to place category wise but surely it is the best tool next to visual studio a developer can have. Although these tools have made the life of the Architects lot easier, manual code reviews (if I may say it so) are still very relevant.”

We do need manual code reviews, and actually passing all the levels of static code analysis the manual code reviews become more beneficial.

things like

How good you have modelled your domain according to the application requirements
Your method/class does what its name suggests
and so on and so forth.

next time I review your code I will tell you what I am talking about here

Comment on Visual Studio Add-in for code review by devbridge

devbridge — Thu, 22 Mar 2012 12:50:26 +0000

Nice but manual.. and manual is by human, and to error is human.. so if a=b and b=c so a=c. hence proven that doing manual is prone to errors.