Reputation
3,705
Top tag
Next privilege 5,000 Rep.
Approve tag wiki edits
Badges
9 27
Newest
 Yearling
Impact
~299k people reached

Apr
11
answered In test-driven development, are there good reasons not to write multiple failing tests and only then to make them pass?
Nov
21
awarded  Yearling
Sep
10
answered TDD Duplicate Testing on Related Classes
Sep
10
revised TDD Duplicate Testing on Related Classes
it's --> its
Aug
28
revised C#6: Should I refactor my code using Resharper for the new features?
grammar
Aug
28
revised C#6: Should I refactor my code using Resharper for the new features?
typo
Aug
18
awarded  Nice Answer
Aug
18
awarded  tdd
Aug
17
answered Is there a need to keep tests for simple (self-contained) functions?
Jul
29
revised Could changing the return type from void to string introduce breaking changes?
edited title
Jul
29
answered Could changing the return type from void to string introduce breaking changes?
Jul
29
comment Could changing the return type from void to string introduce breaking changes?
What do you mean by "The question scope is beyond the case who somebody has implemented this interface too outside the SDK"?
Jul
29
revised Could changing the return type from void to string introduce breaking changes?
grammar
Jul
22
comment Who should write Unit Tests?
@KonradMorawski perhaps we should do something about the gender disparity in our profession and our community.
Jul
22
comment Who should write Unit Tests?
The unit tests should be written by the developer who writes the code, before she writes the code.
Jul
21
awarded  refactoring
Jul
20
awarded  Explainer
Jul
20
comment Unknown design pattern
You could have the build() method throw an exception if any mandatory fields are uninitialized. It's not very expressive, certainly not as clear as a proper constructor, but it's an option.
Jul
20
answered Unknown design pattern
Jul
20
revised Unknown design pattern
typo