1,793 reputation
11022
bio website linkedin.com/pub/…
location Minneapolis, MN
age 47
visits member for 3 years, 10 months
seen Jul 11 at 20:07

Senior Software Developer with extensive experience in Microsoft and other technologies


Apr
2
comment How do you feel about being asked to code during an interview?
I disagree on several details. First, you don't know how I think, and I don't know how you think. Second, most of the examples of "tests" i've seen involve being VERY creative at the drop of a hat. Third, there is a difference between programming with your peers, and programming while trying to impress a future employer. Your peers aren't evaluating your performance and making a decision about whether you will be hired or not. These are fundamentally different environments. There is a difference between "communicating" and "interviewing".
Apr
2
asked How do you feel about being asked to code during an interview?
Apr
1
answered Do Programmers sometimes intentionally over complicate code?
Mar
31
answered Why does every installer on Windows have to be run with elevated privileges?
Mar
31
answered What reasons might a programmer have for wanting hyperthreading turned off?
Mar
7
answered Can you change a license once you pick one?
Feb
28
awarded  Nice Question
Feb
27
answered What is Object Oriented Programming ill-suited for?
Feb
25
answered Small projects using the cathedral model: does open-source lower security?
Feb
25
revised .NET Reflector is no longer free - how does everyone feel about this?
added 185 characters in body
Feb
17
answered HTML/CSS plagiarism
Feb
16
comment Are DDD Aggregates really a good idea in a Web Application?
@qstarin- I disagree with the class per query approach for a lot of reasons. First, it creates a large amount of boilerplate code that you have to rewrite or copy (or generate). Second, it leads to an explosion of classes and I don't see how having 50 classes that do variations of the same thing are any better than 1 class with 50 methods. Even taking SRP into account, it seems to add complexity to the system as a whole. I think there's some middle ground, possibly with specifications that might be better. Also, one class per query makes it more difficult to substitute other persistence later.
Feb
16
awarded  Editor
Feb
16
revised Are DDD Aggregates really a good idea in a Web Application?
added 986 characters in body
Feb
14
comment Are DDD Aggregates really a good idea in a Web Application?
I guess your familiarity with the subject allows you to infer meaning that my unfamiliarity does not. I don't see the the text you quoted as meaning the same thing you believe it does. "all the needed data" is not the same thing as "only the needed data". The way I see repositories working, they return all the data from the aggregate, not just the data you need.
Feb
14
answered Do you count a Masters in CS as a negative?
Feb
14
comment Are DDD Aggregates really a good idea in a Web Application?
Can you provide any references that discuss that? The one you provided says nothing of the sort, and none of the other references i've found mention it either.
Feb
14
answered What did Linus Torvalds mean by his quotation about portability?
Feb
14
comment Can programmer experience be expressed in hours of coded like hours of flight for a pilot?
I didn't say they weren't regulated. I'm simply saying, flight hours really aren't a measure of how experienced a pilot is at all the things necessary to make them a good pilot (staying awake for 5 hours while the plane needs minimal course changes is not necessarily one of them).
Feb
14
comment Are DDD Aggregates really a good idea in a Web Application?
So, after googling a bit on this, it doesn't seem that CQRS is intended to solve the problem i'm referring to. CQRS is about seperating command and query operations, and removing state. It seems more like CQRS is designed to solve various consistency problems, not providing the minimal data needed for an operation (which is basically what i'm discussing)