Reputation
265
Top tag
Next privilege 300 Rep.
Create new tags
Badges
2 12
Newest
 Excavator
Impact
~12k people reached

Apr
11
comment What is “Soft Coding”, really?
This is exactly what I was thinking!!! When logic is buried deep in code, how can a domain/subject matter expert or business user see the values and logic that are in use in order to ensure they are right, and diagnose the system's behavior? One thing a config file does is make the settings visible. There has to be some means for promoting the visibility of business rules--even if that makes the coding "harder". I can accept a thin class or set of classes that do the job, without mixing in other concerns--as long as the business user has the means to access and understand them.
Mar
19
comment Within an interface specified by a core component, should it request IReadOnlyCollection or IEnumerable?
@CodingGorilla I disagree with you. Developers don't read documentation, and helping them to "fall into the pit of success" rather than failure is only accomplished through the code. If you think the selected data types have no meaning to people, then you and I have fundamentally different philosophies of coding.
Mar
19
comment Within an interface specified by a core component, should it request IReadOnlyCollection or IEnumerable?
@CodingGorilla its about what the data types communicate to the developer, and the extra work required to turn an IEnumerable into an IReadOnlyCollection.
Mar
19
comment Within an interface specified by a core component, should it request IReadOnlyCollection or IEnumerable?
@CodingGorilla I think you're just way under-thinking this!
Mar
19
comment Within an interface specified by a core component, should it request IReadOnlyCollection or IEnumerable?
@JohnPeters Perhaps someone else can understand. That you thought I was talking about speed when I didn't write one word in there about performance (show me?) gives me some doubts, perhaps someone else might see things differently.
Mar
18
revised Within an interface specified by a core component, should it request IReadOnlyCollection or IEnumerable?
added 167 characters in body
Mar
18
comment Within an interface specified by a core component, should it request IReadOnlyCollection or IEnumerable?
@JohnPeters This isn't about speed at all. Don't go in that direction. This is about quality software. I care nothing about speed here.
Mar
18
revised Within an interface specified by a core component, should it request IReadOnlyCollection or IEnumerable?
added 1 character in body
Mar
17
asked Within an interface specified by a core component, should it request IReadOnlyCollection or IEnumerable?
Feb
11
comment Why should I use List<T> over IEnumerable<T>?
Any method returning an IEnumerable that can throw is probably making a mistake. Deferred IEnumerable methods should be split into two: one non-deferred method checks parameters and sets up, throwing if necessary (say, because of a null argument). Then it returns a call to the private implementation which is deferred. I don't think my comments are completely at odds with your answer, but do think that you've left out an important aspect in your answer, which is the semantic meaning of using IEnumerable vs. a List (mutation) vs. IReadOnlyCollection (no benefit to deferral).
Feb
11
comment Why should I use List<T> over IEnumerable<T>?
You shouldn't even use List--passing around a List implies that the contents of the list are going to be modified. If you want to return a collection, use IReadOnlyCollection. List is for use within methods, and for exchange between methods that modify the list. That's it!
Jan
15
awarded  Excavator
Jan
15
revised How do you organize your projects?
Spelling corrections
Jan
15
revised Structuring projects in a solution for interfaces
added 11 characters in body
Jan
15
comment Structuring projects in a solution for interfaces
@LightnessRacesinOrbit I have added a section at the bottom of my question, "For Reference". Does that help answer the question? I'm afraid to say that I used "new" as a verb: I should have said, "create instances of the IDataSource-implementing classes that were found." I'll update the post with this clarification, too.
Jan
15
revised Structuring projects in a solution for interfaces
added 1783 characters in body
Jan
14
revised Structuring projects in a solution for interfaces
added 421 characters in body
Jan
14
revised Structuring projects in a solution for interfaces
added 308 characters in body
Jan
14
suggested approved edit on How do you organize your projects?
Jan
14
revised Structuring projects in a solution for interfaces
added 699 characters in body