Reputation
5,553
Top tag
Next privilege 10,000 Rep.
Access moderator tools
Badges
1 16 35
Newest
 Good Answer
Impact
~472k people reached

Feb
1
revised DDD - Aggregate Roots - Dealing with Efficiency and Concurrency
added 5 characters in body
Feb
1
comment Writing Testable Code vs Avoiding Speculative Generality
I would also add, when you are depending on the interfaces in the tests, the generality is no longer speculative
Feb
1
answered DDD - Aggregate Roots - Dealing with Efficiency and Concurrency
Jan
31
comment MVVM Clarification
I doubt I can find a link, because I believe I got it from his book, Domain-Driven Design. Anyway, I think it is an excellent example of the different between domain and application logic. More on the book here books.google.dk/books/about/…
Jan
31
answered MVVM Clarification
Jan
30
answered What defines “software developer” role
Jan
30
comment Workflow: Using binary document formats in Git without locks (moving from subversion)
There are in fact merge tools that can merge Word documents. I don't have any experience with them however, so how good they are I have no idea of?
Jan
28
revised How do we make unit tests run fast?
added 123 characters in body
Jan
27
answered How do we make unit tests run fast?
Jan
25
comment agile / scrum and functional specs
And I'm not hung up on dogma. If the individual team finds that it makes more sense to update the specs every 3 or 4 sprints, by all means do so. Scrum is not set in stone. Adapt it to your own needs. I'm just pointing out that if you want to deliver a potential shippable, it might be problematic to have updating the specs in a separate story.
Jan
25
comment agile / scrum and functional specs
"... @Pete expressed concern that if the spec were a story, how can the product be "potentially shippable" if all that is delivered after an iteration is a spec?" I have a feeling you have misunderstood my comment. What I am trying to say is, can you say that you are delivering a potential shippable after each sprint, if updating the functional specs is placed in a separate story scheduled to be implemented in a later sprint?
Jan
24
comment agile / scrum and functional specs
Very good idea to have updated ISO specifications to be part of the done criteria for a story. To place it in a separate story however, I have difficulty seeing how you can deliver a "potential shippable" product after each sprint.
Jan
21
awarded  Mortarboard
Jan
16
awarded  Necromancer
Jan
16
comment IOC and stateless services. Short-lived or single-instance?
No. What I am trying to say is that it may be difficult to predict how your code base will be modified over time. But the question is extremely general, so I'm giving an extremely general answer ;)
Jan
15
answered IOC and stateless services. Short-lived or single-instance?
Jan
11
awarded  Yearling
Jan
2
answered Use Queue<T> or stick to native f# lists
Nov
1
awarded  Nice Answer
Sep
11
comment Declaring interface in the same file as the base class, is it a good practice?
It is in fact a quite normal pattern to have one interface for one class in .NET, as it allows unit tests to substitute dependencies with mocks, stubs, spys, or other test doubles.