349 reputation
15
bio website spamsense.blogspot.com
location Indianapolis, IN
age 41
visits member for 2 years, 11 months
seen 59 mins ago

Professional: 16+ years C++/C#/HTML/ASP.NET/SQL

Personal: 1 wife, 3 kids


Oct
9
comment Is it reasonable to insist on reproducing every defect before diagnosing and fixing it?
I think what he's saying is, you don't necessarily have to reproduce the issue in order to investigate a fix for it. And assuming you track it down and find a fix, you'll then know the conditions to set up on the test server to reproduce. At that point you'd even know how to set up the previous code - set it up, verify that it's reproducible, deploy the fix, verify that it's fixed.
Jul
2
comment C# Minimal SQL Database
I don't remember if SQL CE has a separate runtime or not. SQLite doesn't, but it can be a little tricky to set up with a .NET project.
Apr
26
comment Hardware running gpl code
How did you determine that it is running Linux?
Apr
4
comment where to use web services
Q: "Should I use web services?" A: "Only if you want to use your data somewhere besides the system where it's produced."
Mar
29
comment Is it OK to have multiple asserts in a single unit test?
I've seen cases where multiple asserts were used instead of RowTest (MbUnit) / TestCase (NUnit) to test a variety of edge-case behaviors. Use the proper tools for the job! (Unfortunately, MSTest doesn't seem to have a row-test capability yet.)
Mar
27
comment Should Repositories return IQueryable?
If you're just going to use an IQueryable, then why would you even use a repository? Repositories are intended to hide implementation details. (Also, WCF Data Services is quite a bit newer than most of the solutions I've worked on in the past 4 years that used a repository like this... So it's not likely that they'll be updated anytime soon just to make use of a shiny new toy.)
Mar
27
revised Should Repositories return IQueryable?
added 199 characters in body
Mar
27
comment Should Repositories return IQueryable?
@MikeBrown The point of this question - and my answer - is that you want to expose the behavior or the advantages of IQueryable without exposing the IQueryable itself. How are you going to do that, with the built-in API?
Mar
26
revised Should Repositories return IQueryable?
added 852 characters in body
Mar
26
comment Should Repositories return IQueryable?
If I didn't want to expose the built-in query API, yes.
Mar
26
answered Should Repositories return IQueryable?
Mar
26
comment Is the average number of bugs per loc the same for different programming languages?
I think your edit (Update:) is the core of the problem. Or, as Mark Twain said, there's three kinds of lies: Lies, Damn Lies, and Statistics.
Mar
20
comment What should a test method test?
Also, keep in mind that putting multiple, dissimilar tests in one method (first approach) will not fully exercise your classes - as soon as one of them fails, the rest of the assertions in that test method do not even run.
Mar
13
comment How do I handle having so many SQL queries?
@LieRyan As long as you're operating on the IQueryable, this is possible in LINQ as well.
Mar
12
awarded  Yearling
Mar
12
awarded  Editor
Mar
12
revised Why is (position < size) such a prevalent pattern in conditionals?
added 47 characters in body
Mar
12
comment Why is (position < size) such a prevalent pattern in conditionals?
Depending on your development tools, many will also warn (or error) on the variable = constant construct.
Mar
12
answered Are these good reasons for moving to Microsoft web development platform?
Mar
12
answered Why is (position < size) such a prevalent pattern in conditionals?