391 reputation
15
bio website blog.excastle.com
location Omaha, NE
age
visits member for 4 years, 1 month
seen Sep 7 at 13:59

Feb
28
awarded  Caucus
Sep
30
comment Reasons for Pair Programming
@jfrankcarr, nobody even suggested permanent pairs; I'm not sure where you came up with that idea. (Notice that this answer specifically mentioned "when to rotate pairs".) Our team found that it's a really bad idea to keep the same two people pairing with each other for more than a day or two; you start to get in a rut. Some teams rotate every hour and a half (PDF link).
Nov
15
awarded  Yearling
Nov
8
awarded  Nice Answer
Aug
22
awarded  Commentator
Aug
22
comment WPF vs. WinForms - a Delphi programmer's perspective?
Actually, some of the biggest hurdles are about learning to work with a framework that separates responsibilities properly, rather than just having everything blindly derive from TKitchenSink.
Jul
5
comment Low impact refactoring and code cleaning of sloppy code while waiting for requirements
If the code wasn't designed for tests, that's all the more reason to get tests around it -- but safely. Read Michael Feathers' book "Working Effectively with Legacy Code"; it has recipes for making untestable code testable.
May
18
comment How does one network at software conferences?
I recently ran across a good article that speaks to your "Don't talk yourself up" point: "The Art of Conversation: How to Avoid Conversational Narcissism" artofmanliness.com/2011/05/01/…
May
18
comment Dominant team members in a Scrum team
That's an awesome way of re-framing the problem. Asking for his help completely changes the situation (and makes it a whole lot less scary).
May
18
answered How can I make refactoring a priority for my team?
Apr
20
comment When to go Fluent in C#?
@ach, I don't see anything in this reply about "more calls than setters". Are you confused by his statement about "code [that] is read a lot more than it's written"? That's not about property getters/setters, it's about humans reading the code vs. humans writing the code -- about making the code easy for humans to read, because we typically read a given line of code much more often than we modify it.
Mar
5
comment WPF vs. WinForms - a Delphi programmer's perspective?
Don't know about the job market. As for the debugger, expect frustration if your window's constructor throws an exception, because the debugger will be reluctant to give you a stack trace -- but all you have to do is dig into two levels of InnerException in the debugger's exception-details dialog. And if your bindings don't work, run under the debugger and look in the Output window to see the binding errors. Other than that, I'm not sure what concerns you have. WPF debugs OK in my experience, and MVVM lets you unit test more of your UI logic than you can in WinForms.
Mar
2
awarded  Supporter
Mar
1
awarded  Teacher
Mar
1
answered WPF vs. WinForms - a Delphi programmer's perspective?
Aug
15
comment What optimizations are premature?
@Simon, the answer stands. If you're making the code less readable, or less maintainable, and you don't have profile results to prove that you need to, then the optimization is premature. You haven't proven that the code isn't good enough; you haven't proven that you need to hurt your productivity today by making the code worse in the face of a possible problem tomorrow. See YAGNI: en.wikipedia.org/wiki/YAGNI