327 reputation
311
bio website
location United States
age
visits member for 2 years, 10 months
seen May 5 at 18:51

I've been developing web applications since 2001, specializing primarily in Microsoft based technologies (ASP.NET, MVC, C#, SharePoint, WCF and Silverlight). While I still leverage these technologies heavily in my day-to-day, I'm quickly becoming addicted to mobile & open-source development using HTML5, jQuery, underscore, knockout & REST.

I've also developed a strong affinity for Agile clean-code practices and extensible design patterns and I'm currently researching mobile cross-device development techniques on Windows Phone, iOS & Android.


Jan
16
awarded  Notable Question
Oct
14
comment Should comments say WHY the program is doing what it is doing? (opinion on a dictum by the inventor of Forth)
Not ALL comments are bad, you just need to make sure that a) they aren't used as a crutch to excuse poorly designed implementation and b) they are properly maintained. But again, code commenting and documentation are two very different things, and this question addresses commenting code specifically.
Oct
14
comment Should comments say WHY the program is doing what it is doing? (opinion on a dictum by the inventor of Forth)
@ACase Commenting your code and documenting your program's implementation are two separate things. IMO comments within code are a smell that the implementation is suboptimal and requires a "human" explanation to the reader. Separate documentation of a program's implementation or architecture is another matter entirely and has nothing to do with literal commenting of code. In any case, if you feel the need to comment your codebase line-by-line, then it's nothing short of irresponsible to not place the same maintenance weight on the comments themselves as it is on the actual code.
Aug
3
awarded  Popular Question
May
3
accepted Task Planning on an Agile Team
May
2
comment Task Planning on an Agile Team
I actually mean hours for the tasks, we assign story points for the user stories
May
2
asked Task Planning on an Agile Team
Mar
15
accepted Test planning for an Agile sprint
Mar
15
comment Test planning for an Agile sprint
Thanks for your excellent answer, this indeed helps! Does your entire development team create this sprint test plan, or does that responsibility go to more QA-focused team members? Also, how do you keep track of the status of all of your bullet-point items (whose working on what, what is done, what still needs to get done). Thanks again for your answer!
Mar
15
comment Test planning for an Agile sprint
@dzieciou Honestly all that you described in your answer below is what our ideal purpose would be. Doing everything we need to do in order to test the sprint's features and do so in a transparent manner.
Mar
15
revised Are RIA plugins a thing of the past?
deleted 314 characters in body
Mar
15
revised Are RIA plugins a thing of the past?
edited title
Mar
14
asked Test planning for an Agile sprint
Mar
9
comment Maintain a web application once the only developer is gone
Very sorry to hear this. Honestly, given your situation this web application would be the last thing I'd concern myself with.
Mar
9
comment Shared QA responsibilities on an Agile team
Thanks for the response, it closely aligns with how we're currently handling our approach. Our failings are mainly in the depth of thought being put into test planning for a sprint and providing transparency to all team members as features are being tested. Our test tasks right now are very high-level and generic, as a feature is being tested it's very difficult to know what the testing status of a feature is. I'd love to easily see not only what features are being tested but also by what means those features are being tested, empowering developers to engage fully in test tasks.
Mar
9
awarded  Commentator
Mar
9
comment Shared QA responsibilities on an Agile team
@mattnz A little of both I suppose, but with an emphasis on how quality assurance and control can be owned by both developers & testers. Ultimately the goal is to get to the point where we don't specifically need to rely on a "tester" per-se to test a sprint feature, instead hoping that testing can be accomplished by any team member.
Mar
9
asked Shared QA responsibilities on an Agile team
Feb
27
awarded  Yearling
Feb
25
awarded  Caucus