Reputation
1,197
Top tag
Next privilege 2,000 Rep.
Edit questions and answers
Badges
6 11
Newest
 Yearling
Impact
~22k people reached

  • 0 posts edited
  • 1 helpful flag
  • 22 votes cast
Jun
8
comment C# Dependency Injection with Adapter Pattern
I think still doesn't change that much what I said. Rather than exposing the reader/writers, use the controller as a pass through. So you would have: public interface IController { void Write(string value); string Read(); ...} And then do transformations inside the controller to use the right reader/writer. That way, your client doesn't know about the type of reader/writer that you are using, and therefore you keep a clean separation
Jun
6
answered C# Dependency Injection with Adapter Pattern
Mar
25
comment Understanding Bob Martin's Closed For Modification Explanation
Well, yes they are. But from the point of view of a user of the extension method, it does indeed look like there is new functionality for the class.
Mar
25
revised Understanding Bob Martin's Closed For Modification Explanation
added 595 characters in body
Mar
25
answered Understanding Bob Martin's Closed For Modification Explanation
Feb
16
answered Is circular Dependency Injection a good practice?
Feb
16
answered Does react.js make sense for a static content-driven site?
Jan
5
awarded  Yearling
Aug
25
awarded  Guru
Apr
11
awarded  Informed
Apr
11
answered Refactoring sought for replacing shared data types in .NET component
Apr
11
answered How to avoid errors and not miss anything
Apr
9
comment Should refactoring be the exception or the rule?
"Think, Act, Evaluate" will be more what I follow. I don't know of anyone, personally, that can get a design 100% before starting to write code. But I agree that you only refactor as much as it is really needed, not changing something just to make it "beautiful".
Apr
9
awarded  Commentator
Apr
9
comment Should refactoring be the exception or the rule?
I do agree with isolating code. I do apply SOLID and layers on my code. Doesn't really change what I said.
Apr
9
comment Should refactoring be the exception or the rule?
@gbjbaanb As long as the code has not been transferred to the test environment, there are no bugs, just unfinished code. Once you transfer to test (or uat, or live) then you have the bugs and you make the distinction.
Apr
9
comment Should refactoring be the exception or the rule?
YAGNI. I have suspected in the past many times that things were going to be needed, because they made sense logically. But for one reason or another (change on requirements, scope or even the project being cancelled) they never happened. So it was wasted time.
Apr
9
revised Should refactoring be the exception or the rule?
tiny bit of formatting
Apr
9
answered Should refactoring be the exception or the rule?
Apr
9
comment Does craftsmanship pay off?
I waited until I was the senior developer and had the buy in from the Development Manager before changing our process. When I had the power to change it, I did (well, we are still evolving into better processes). I wouldn't force it on entrenched people with more seniority/power.