1,084 reputation
511
bio website None
location London, United Kingdom
age 36
visits member for 2 years, 10 months
seen 2 days ago

System Analyst at Innovative Output Solutions. Officially.

Unofficially, man with many hats. Working as ScrumMaster, Senior Developer, Architecture Lead, researcher of tools and the creator of all the new procedures being implemented in the department.

On my spare time I'm dabbling with Python. Some results can be seen at: https://github.com/MiyamotoAkira


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.
Apr
8
answered What is the main goal of MVVM pattern?
Apr
8
awarded  Editor
Apr
8
revised Ensure that each class has only one responsibility, why?
added 230 characters in body
Apr
7
comment Ensure that each class has only one responsibility, why?
You do the same to all classes. You end with more classes, all complying with SRP. It makes the structure more complex from the point of view of connections. But the simplicity on each class justify it. I like @Doval's answer, though.
Apr
7
awarded  Nice Answer
Apr
7
answered Ensure that each class has only one responsibility, why?
Apr
3
comment Why have private static methods?
I must say I have never done that or seen that behaviour. The few times I have done it was for helper methods to public static classes.
Apr
2
awarded  Good Answer