6,541 reputation
32129
bio website softwareonastring.com
location Netherlands
age 52
visits member for 4 years, 3 months
seen Nov 22 at 18:59

Software developer since 1985. Started in Cobol, moved via Clipper/VB to Delphi. Delphi developer since 1998. Sniffing at C# and playing around with javascript and some php for websites. Coaching new employees and less experienced developers. Focused on software architecture and SOLID design. Keenly interested in user experience and usability.

Questions

When you ask a question, show your effort, provide all the details that will help someone to help you and be precise.

Answers

When you answer a question, don't just paste your code. Your answers will be much better when you explain why your code is doing what it does and how it achieves the asker's goal. It makes it a whole lot easier to follow along. As it is I am much more inclined to up-vote answers that have explanatory text about what the code is doing and why it is written as it is.

Answers that just contain links aren't likely to get an up-vote from me either

Other

Obligatory link whenever someone thinks they are improving security by imposing all sorts of rules on password composition: Password strength


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)
Sep
27
comment Are any top software products outsourced? (offshore or otherwise)
@RossPatterson: Where does it say that they our outsourcing development of their virtualization solution? I may be reading it wrong (just scanned it really), but I see MS outsourcing the operation of their virtualization platform, not the development of it?
Sep
27
revised Are any top software products outsourced? (offshore or otherwise)
added 411 characters in body
Sep
19
revised Why is aggregation function bad idea for RESTful?
Added a section on algorithmic uri's
Sep
11
awarded  Yearling
Jul
19
revised Unit testing statically loaded data
added 11 characters in body
Jul
19
answered Unit testing statically loaded data
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.
Jul
2
awarded  Guru
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
27
answered Design Patterns for creating tasks
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
revised Is method overriding always a violation of Liskov Substitution Principle?
added 383 characters in body