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

  • 0 posts edited
  • 0 helpful flags
  • 143 votes cast
Aug
30
comment Dealing with inflexible programmers
@Wayne: I think we are just arguing terminology. Those reasons, to me, aren't ignorance. Under the best possible light, they reflect issues with prioritization of short term/long term costs/gains and corporate(external to team) culture. However, it is usually a motivational issue. Those issues are much harder to solve than a lack of education.
Aug
30
comment Dealing with inflexible programmers
@Wayne: if it were just technical ignorance, simply pointing out the gaps in knowledge would be sufficient. Given that isn't the case, it is far more than ignorance. Many people, by their nature and situation, are resistant to change. As for the reasons, lots. A simple search of "why are people resistant to change" will yield large numbers of useful results.
Jul
8
comment Worst coding standard you've ever had to follow?
@Bernard-In most organizations creating a long term revenue stream is grounds for rapid promotion. Hopefully, somebody else saw the insanity in this and accidentally ran him/her over in the parking lot.
May
24
comment Who does the UX on a scrum project?
Defining the UX role and responsibilities would be a useful starting point in this question. In the broadest sense, UX is everything the user experiences and goes well beyond what the code does and is often the responsibility of multiple people.
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.
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.
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.