Reputation
944
Next privilege 1,000 Rep.
See votes, expandable usercard
Badges
4 8
Newest
 Critic
Impact
~13k people reached

  • 0 posts edited
  • 0 helpful flags
  • 140 votes cast
Mar
12
answered Scriptable user-interfaces/frameworks for automated UI testing
Mar
11
answered What do you do when one thinks the code isn't complicated enough?
Mar
11
answered Does professionalism in job postings matter?
Mar
4
awarded  Commentator
Mar
4
comment UI Testing with Visual Studio 2010 Feature Pack 2
@Seth-not sure how much it matters. This is such an immature area that each significant release is likely to change the game. Given that MS finally has the automated testing bug(pun intended), their offering should continue to improve. Telerik will probably be focused on taking the MS solution to the next level.
Mar
3
answered UI Testing with Visual Studio 2010 Feature Pack 2
Mar
1
awarded  Nice Answer
Feb
16
revised Dealing with inflexible programmers
Added highlighting
Feb
16
comment Software bug/defect classification
What problem are you trying to solve ?
Feb
16
comment Dealing with inflexible programmers
@Marci-I've always believed the field of software development has allowed a percentage of the population from avoiding mental health hospitals. Not that they shouldn't be institutionalized, but that they can hide within some development teams.
Feb
15
answered Dealing with inflexible programmers
Feb
13
answered How should I manage a team with different skill levels?
Feb
10
answered Assembly as a First Programming Language?
Feb
7
awarded  Editor
Feb
7
revised What is the motivation that makes you to stick with current job?
poor choice of their for there
Feb
6
answered What is the motivation that makes you to stick with current job?
Feb
4
answered Can you be a manager and a programmer at the same time?
Jan
30
comment How much Code Coverage is “enough”?
I like the number (70%). As my teams get higher, I tend to start finding tests for coverage than for value. On the WPF comment, we are just in the beginning days. Meaning, we aren't building/structuring WPF code to be easily testable. Mock models help. When designing code, design it to be testable. And, yes, at this point there are limited examples so you'll have think about it. No different than where most developers were as TDD was introduced to them for the first time just less industry experience.
Jan
30
comment TDD with limited resources
One addition: Initially, look for highest value tests. Tests that let you know, early, you've broken your code base. These tend to be high, sweeping tests that don't tell you what you broke, but that you broke it. You'll very quickly see the value of a CI, with testing, environment. Use tests to debug breakage. With a system in place, the costs of adding new tests starts getting easier/cheaper and you can focus on more tests that do a better job of proving that it works and showing where it doesn't.
Jan
30
comment How to convince an employer to move to VB.Net for new development?
ROI is the right approach, but the human factor (boss comfort/preference) tends to win out. A bad manager will put their technical skills or lack thereof ahead of the best choice. It is also worth noting that waiting until the risk is realized, especially if there will be some time to react, isn't bad. With a confirmed risk(e.g. doesn't work with Win8), getting significant resources for an important code base is much easier and likely to be larger than without which could mean faster, but done properly.