294 reputation
26
bio website bronumski.blogspot.com
location United Kingdom
age 36
visits member for 3 years, 8 months
seen Mar 11 at 12:11

.Net agile developer


Feb
25
awarded  Constituent
Feb
25
awarded  Caucus
Sep
19
awarded  Analytical
Nov
1
awarded  Yearling
Jul
1
comment Babysitting your Continuous Integration System
@Thorbjørn Perfectly entitled to disagree and disagreement to certain extent is good as it allows us to discuss different ideas. Looking forward to disagreeing with you again, now I must get back to belittling junior developers :)
Jun
30
comment Babysitting your Continuous Integration System
@Thorbjørn This is a CI server not your local development box. The point is the team should do everything in their power to prevent checking in code that breaks the build. Hopefully people work in a fun friendly environment and the embarrassment I am talking about is not mean spirited but it makes people think next time before they commit. But we do have a funny sound that plays when the build server breaks.
Jun
15
comment TDD: What happens before the first unit test?
I love BDD and use StoryQ. Don't forget to mention that the story can be expanded into senarios with Given/When/Then. Given some stuff has happened When I do this And this Then I expect this and this. Check out David Starr's talk on this at TechEd channel9.msdn.com/Events/TechEd/NorthAmerica/2010/DPR302 and also have a look at StoryQ if you are using .net storyq.codeplex.com
Jun
15
awarded  Editor
Jun
15
revised Coding standards and coding style, is it that much important?
added 2 characters in body
Jun
15
answered Coding standards and coding style, is it that much important?
Jun
15
answered What design and planning techniques are the most suitable for individual projects?
Jun
15
answered looking for a User Guide to write a JIRA Issue
Jun
14
comment Dealing with a developer continuously ignoring edge cases in his work
@Barry Brown I agree there are always edge cases but there are a difference between important edge cases that the Stakeholders deem to be important which we can call Scenarios and edge cases that a developer deems important. If a Stakeholder thinks something is important then it should be discussed at the planning session and included as a Scenario on a User Story and not left up to the developer to think of, it should be a proper requirement against the task. It is very time consuming and not necessary to but null checks against parameters on every single non public method.
Jun
14
answered Dealing with a developer continuously ignoring edge cases in his work
Jun
9
answered Babysitting your Continuous Integration System
Jun
8
answered Best practices for replacing licensed software with an in-house solution
May
24
awarded  Teacher
May
24
answered Style and recommendations of commenting code
May
24
awarded  Supporter
Nov
1
awarded  Autobiographer