291 reputation
25
bio website
location Vancouver BC
age
visits member for 3 years, 4 months
seen Dec 15 at 18:04

Nov
21
answered Designing a better performing total permissions setup for multiple permission levels
Nov
21
answered Reducing dependency cycles and reducing coupling
Nov
16
comment How to do Test Driven Development
I would disagree with your first statement. Unit-tests should guide your code design, that results in good testability. If they are written after code, they usually act as taxes developer has to pay, after his code works. Also, if you write code first, you may often find that to test it you need to change it that is avoided by TDD. I would not recommend doing test-after at all even for simple cases. If it's a bug fix simple as one character change - write a failing test (which was obviously missed before) and then fix it and make the test pass.
Nov
16
comment How to do Test Driven Development
Code coverage might not be very reliable measure. Enforcing % of coverage usually results in a lot of non-necessary tests (like tests for all parameters null checks, etc. - which are tests for the sake of tests that add almost no value) and wasted development time, while hard to test code paths might not be tested at all.
Nov
16
revised How to do Test Driven Development
deleted 99 characters in body
Nov
16
awarded  Editor
Nov
16
revised How to do Test Driven Development
added 217 characters in body
Nov
16
answered How to do Test Driven Development
Feb
26
awarded  Caucus
Feb
26
awarded  Constituent
Feb
19
comment How can I deal with a team member who dislikes making comments in code?
@G3D I will disagree here, commenting on "where it will be used" is one of the wrong thing to do. One should never comment the intended usage - it does not guarantee it will not change and when it changes - people will 95% forget to update/remove the comment (hey, why would I need to touch this class if I just used it or its property in some other way =)) which will lead to issues later.
Feb
18
comment How can I deal with a team member who dislikes making comments in code?
@mehaase I don't find it to be helpful to hold anyone accountable for the issues that could have been avoided in the first place. I do agree that there are complex algorithms etc that need explanation, but those are very rear. If method size is 5-3 lines of code and it's "SRP-complaint" - I can hardly find a reason to add a comment to it, since its name will state what is the only thing this method is meant for.
Feb
18
comment How can I deal with a team member who dislikes making comments in code?
@jmk I was not saying "never" use comments, I suggested to get rid of all those, which one can. If comment can be removed via renaming/refactoring - that's the right way to go - those comments must not remain.
Feb
17
awarded  Announcer
Feb
6
answered How can I deal with a team member who dislikes making comments in code?
Aug
25
awarded  Yearling
Apr
12
answered Testing loses its effectiveness if all programmers don't use them
Jan
19
answered Parent and child permission schemes
Jan
19
comment Meaningful concise method naming guidelines
"Clean Code" was the greatest book that helped me understand the impact of code readability and listed the best practices I follow on regular basis
Jan
18
answered How do I choose what code to review?