Reputation
3,277
Top tag
Next privilege 5,000 Rep.
Approve tag wiki edits
Badges
8 25
Newest
 refactoring
Impact
~272k people reached

15h
revised Could changing the return type from void to string introduce breaking changes?
edited title
15h
answered Could changing the return type from void to string introduce breaking changes?
15h
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"?
15h
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
Jul
19
awarded  Nice Answer
Jul
14
answered Continue building off an ugly code base or start refactoring?
Jul
14
comment Continue building off an ugly code base or start refactoring?
c2.com/cgi/wiki?PlanToThrowOneAway
Jul
1
revised What are the design principles that promote testable code? (designing testable code vs driving design through tests)
typos
Jul
1
answered Is testable code better code?
Jul
1
revised Is testable code better code?
typos
May
14
answered What factors should influence how I determine when to abandon a small project with a friend?
May
13
comment How would a new language look if it was designed from scratch to be easy to TDD?
It's purely a prototype. If it were to get real, then we would have to consider things like performance and size, but it's much to early to worry about that, and if we ever got to that point, it wouldn't be hard to choose what to leave out or, if desired, to leave the assertions out of compiled code. Thanks for your interest.
Apr
15
revised TDD Red-Green-Refactor and if/how to test methods that become private
its --> it's and introduced semicolons between independent clauses