5,319 reputation
11129
bio website
location Düsseldorf, Germany
age 40
visits member for 3 years, 11 months
seen 7 hours ago
Software developer, mathematician

2d
answered Where should I store test data?
Dec
15
comment Ignoring unit tests - good and bad reasons when and why?
"Removing tests that seem redundant is a waste of time. Extra testing never hurt anybody." Disagree - redundant code is often a problem, even with tests. You may need to refactor them, or change them when requirements (or your test setup) change. Then the duplication will cause extra effort.
Dec
3
comment Code First vs. Database First
@JamesAnderson: Actually, I'm a huge fan of agile development principles, where you usually only design for what you need now, unless you know you cannot change the design later (rarely the case). But I'm beginning to go off-topic...
Dec
3
comment Code First vs. Database First
Requirements first, though you should not wait until requirements are complete (they never are). Get going once you have enough to have an idea of what the goals of the application are, then get more when you need them.
Dec
3
comment Code First vs. Database First
And just to put a name on it: These practices are all (arguably the) important practices in Agile development (incremental development, the simplest thing that could work, test-driven, user needs first...).
Nov
24
awarded  Nice Answer
Nov
4
comment How much detail about a user story can a developer expect?
@Wolfgang: About "decisions the customer will revert": This will happen, not matter what methodology you use. Only in Agile, it happens sooner, so less effort is wasted.
Nov
3
answered Alternative to printing debug information to stdout\stderr
Nov
3
comment Should a getter throw an exception if its object has invalid state?
There may be situations where this is the best solution, but I cannot imagine any. For most cases, this seems overly complicated: One method throws with incomplete data, another returns null. I'm afraid this is likely to be used incorrectly by callers.
Oct
24
comment Would forcing developers to fix at 3 AM the build they broke undermine motivation?
Frankly, this sounds like a crazy idea. I don't think I'd like to work anywhere that even considers this.
Oct
22
comment Why use services (REST/SOAP) instead of a library?
Yes, the call overhead should indeed be lower. I took the liberty of editing your answer, to replace the mention of "native code" with "lower call overhead". Feel free to re-edit if you disagree :-).
Oct
22
revised Why use services (REST/SOAP) instead of a library?
replace "native code" with "low call overhead"
Oct
21
comment Why use services (REST/SOAP) instead of a library?
"native code" does not really make sense here: a) a service can use "native code" too, and b) just-in-time compilation often provides the same performance as native code.
Oct
20
comment Is staying implementation agnostic really worth it?
+1 for mentioning applications where support for multiple DBMS is a feature. If you offer your application for "self-hosting" (something many enterprise customers find desirable), you may need this. However, you can probably still stick to one ORM.
Oct
13
comment Can one determine the creation date of an email account?
I'm rather suprised this gets so many downvotes. While the question does show some lack of basic knowledge, it is a valid question IMHO.
Oct
8
comment TDD: how to test file outputs?
I don't want to get dogmatic - I just find the distinction between unit and integration tests helpful, because both have different strenghts and weaknesses. And yes, some things are not pratical to unit-test - that's why we have integration tests :-).
Oct
8
comment TDD: how to test file outputs?
Good points. However, I would class all these tests as "integration tests", because they involve multiple components, and even external tools/libraries.
Oct
8
comment TDD: how to test file outputs?
Essentially, you split your code into your business logic, and the interface logic to drive the PDF generator. The business logic is then unit-tested. The interface logic should be so simple you don't need unit tests - of course it will still need integration tests. Manually checking the files would be one kind of integration test.
Sep
24
awarded  Autobiographer
Sep
24
answered Do Agile projects use abbreviated defect reporting?