Reputation
6,913
Top tag
Next privilege 10,000 Rep.
Access moderator tools
Badges
3 22 30
Newest
 Yearling
Impact
~201k people reached

Feb
20
comment Cheap implementations in fundamental TDD
@Alfe "... or write the correct solution anyway" How would you know it is correct and more importantly that it remains correct? Quite often ensuring proper test cases before hand may seem "over the top" for the initial implementation, but they start shining when someone inadvertently makes a change that introduce a bug and that bug goes unnoticed because the test cases where done after the fact and may well suffer from myopia by the developer who thought (s)he was already done.
Jan
26
comment Two contradicting definitions of Interface Segregation Principle – which one is correct?
Cool @user61852 :) (and thanks for the credit)
Nov
7
comment In an Agile Environment, who is responsible for software architecture
Because of the questions like @DaveHillier poses, I tend to use "s/he"... (Thanks for this great answer by the way, puts reality back into the "the team is/does/has/owns ..." cliches)
Jul
19
comment Organizing solution / project structure and classes for Line of Business Application (LOB)
In this case I don't agree with the YAren'tGNI approach. Separation of concerns is far easier to achieve and keep up when unrelated code is in separate assemblies. And of course separation of concerns helps achieving better design with high cohesion and low coupling. Having to add an assembly in your references makes dependencies visible and makes it harder for dependencies "to creep up on you". Use it to think about whether you actually need that code and/or whether is is where it belongs. It's a LOT simpler to code this way than having to loosen badly intertwined dependencies when YAreGNI.
Jul
19
comment Desktop client server application, limiting text area field compromise with customers
Forget about size restrictions and think about lazy loading. Don't load the notes unless they are actually needed to display or edit. So don't include the notes in any queries used for list displays, always filter server side if a note is in the filter expression, etc.
Jun
28
comment Design Patterns for creating tasks
Oh and using observer would make your observer of the Entity certainly non-anemic... Your Entity class still may or may not be anemic, but the observer certainly won't. The desire not to have anemic classes is very good, but you should still not put code in a class just to make it non-anemic. The code to instantiate the Task indeed does not belong in Entity as it would introduce unwanted (and unwarranted) coupling. Any code added to Entity should be related to Entity.
Jun
28
comment Design Patterns for creating tasks
Perhaps your confusion stems from treating design patterns as code examples. A design pattern may have a code example to explain it, but it is never limited to that example. Design patterns are much more than just code examples. Design patterns are ways of talking about code and talking about general solutions to common problems. It is up to the developer to apply a design pattern to his/her specific problem by amending the explanatory example to his/her specific case.
Jun
28
comment Design Patterns for creating tasks
Whether your classes are anemic has nothing to do with using or not using Observer. Furthermore the Observer pattern is not restricted to passing along just "simple" parameters. The observed can pass along anything you need to the observer. So you could simply pass along the Entity instance that was changed and the observer can pick whatever it needs.
Jun
20
comment Mental Models or Real-World-Metaphors for Functional Programming
@Doval: Thanks for taking the time to explain. Learned something :-)
Jun
18
comment Mental Models or Real-World-Metaphors for Functional Programming
Curious: can I infer from your example that in Haskell "things flow left"? Meaning that execution starts at the right end of the statement and results of the right most function are input for the one to its left? That would present an interesting challenge for someone used to OO fluid coding where each method of a class returns the instance it worked on as its result (including its now changed state), which means that "things flow right". Meaning that in fluid coding your examples would become smallest = SomeInstance.Sort.Head and smallestEven = SomeInstance.FilterEven.Sort.Head.
Jun
15
comment Is method overriding always a violation of Liskov Substitution Principle?
@Phoshi: Ah that's what you were getting at. Yes, indeed, I just responded to the "is overriding always a violation of LSP". And for me overriding is linked to classes... I trust you upvoted DocBrown's answer then :)
Jun
13
comment Simplifying data search using .NET
Use SOLR?
Jun
12
comment Is it customary for software companies to forbid code authors from taking credit for their work? do code authors have a say?
Would you like to be called/mailed by your company's customers to provide support even after you have left that company? And don't think they wouldn't be able to contact you if the source doesn't contain an (e-mail) address or other contact information. I wouldn't like it. And therefore I'd be more than happy to remove my name if and when my employer decided to provide the source with their software.
Jun
12
comment Is method overriding always a violation of Liskov Substitution Principle?
@Phoshi: Yes, so? That doesn't preclude cases where you do have base behavior and descendants can add to it as necessary. After all a class is a type. Calculations in payment and salary programs for example. The ancestor will do the basic calculations, descendants may add extra's, effect different values for parts of the calculation depending on whatever. Of course in any salary program the calculations may well be an amalgamation of Strategy patterns and each may in effect have its own inheritance hierarchy to deal with all variables and variations.
Jun
12
comment Is method overriding always a violation of Liskov Substitution Principle?
@jk. How? Augmented behavior in payment programs could be a getting a value from somewhere for the calculation of rebates, an additional rebate, ... whatever ... all variations on calculating (base) rebates from the ancestor, all still within SRP.
Jun
9
comment Access Token Verification
@DecafCoder: no re-login after a restart, regardless of the reason, sounds like a security risk? And if that is what you are after then the token becomes more of an API key than an access token. Access tokens by their nature need to have a limited life time? You may also want to check out Information Security.
Jun
9
comment Access Token Verification
@miraculixx: I am no hashing expert, but wouldn't hashing the (referring URL, source IP and day of the year) limit the validity of the token to a single session on a single day?
Jun
8
comment Access Token Verification
Why would it need to store the token in a database? Wouldn't it be perfectly acceptable to store it in memory and accepts that if the server crashes or is restarted all tokens become invalid. As sessions don't usually survive a restart why should tokens?
Jun
8
comment Why Beta versions have so many bugs?
@Eugene: wouldn't it be a waste of time to develop a feature, ensure it is 100% bug-free, put it up for beta only to learn that nobody really cares about the feature?
Jun
6
comment is it valid that a state machine can have more than one possible state for some transition?
Perhaps only one type of output, but an item can have one of several states following the current one? Just think of have an issue "in progress". You may decide not to work on it anymore and its state returns to "open". And when you do finish working on it, it's state may become "fixed", or "working as designed", or "cannot reproduce" or... How about the output of working on an issue, given that it can transition to all these states? It may be documentation, a working feature [+ doc], or nothing at all? How would you deal with a "working on an issue" activity to satisfy the one output rule?