96,001 reputation
24213372
bio website linkedin.com/in/…
location Lancaster, CA
age
visits member for 4 years, 7 months
seen 12 hours ago

Pythagorean Theorem

http://www.davis-inc.com/pythagor

Copyright © 1998 by Davis Associates, Inc. All Rights Reserved


May
8
revised If this isn't a user story, what is it?
added 1 character in body
May
8
revised If this isn't a user story, what is it?
added 47 characters in body
May
8
answered If this isn't a user story, what is it?
May
8
comment If this isn't a user story, what is it?
How would you get from the first version to the second, if all you had at the beginning of the sprint was the first? What do you call the second version? Requirements? On it's face, the second version feels like a more complete, less ambiguous description, so if all this is about is what the definition of "user story" is ...
May
8
comment How to deal with team members writing bad code
@MichaelDurrant: I made a small tweak to my answer. I trust that suffices.
May
8
revised How to deal with team members writing bad code
added 32 characters in body
May
8
awarded  Enlightened
May
8
comment How to deal with team members writing bad code
@JohnBarça: Nobody is arguing that. I certainly didn't make that assertion in my answer. But there has to be a point where you say "it's good enough," without engaging in endless, ongoing tweaking. That's the place that you're at when your superiors say "don't touch this; it already works, and there's no point in putting further effort into it."
May
8
comment How to deal with team members writing bad code
@MichaelDurrant: Then you must be taking the position that there is a place that you can arrive at where the code is essentially done, and needs no further work, barring new features. This is the state I am describing when I say "declared successful."
May
8
comment How to deal with team members writing bad code
@MichaelDurrant: I don't know of any software project where people regularly go in and massage code that already works, unless they're adding a feature, fixing a bug, or deliberately setting aside time to work on technical debt. If your premise is that we throw the thing together and fix all the problems later, I submit to you that is not the best possible approach. If it's worth doing, it's worth attempting to get it right the first time.
May
8
comment How to deal with team members writing bad code
@MichaelDurrant: You must have missed the part where I said "declared successful."
May
8
awarded  Nice Answer
May
8
answered Reason to treat internal class variables and functions inside a class as “separate” entities
May
8
awarded  Guru
May
8
answered How to deal with team members writing bad code
May
8
awarded  Good Answer
May
8
awarded  Enlightened
May
8
awarded  Nice Answer
May
8
awarded  Enlightened
May
8
awarded  Nice Answer