620 reputation
513
bio website
location
age
visits member for 3 years, 2 months
seen 2 days ago

Jul
2
awarded  Curious
Jun
11
awarded  Good Question
Apr
19
awarded  Yearling
Apr
15
accepted How to do an effective code review of library changes?
Apr
11
revised How to do an effective code review of library changes?
added what i have already done
Apr
11
asked How to do an effective code review of library changes?
Mar
17
accepted How to address, “Is anyone even using this feature?” questions
Mar
15
awarded  Good Question
Mar
14
awarded  Popular Question
Mar
14
awarded  Nice Question
Mar
14
comment How to address, “Is anyone even using this feature?” questions
1 and 2 are not practical. 75-95% of what the app does is backend work, not a user facing interface and its a healthcare application. Can you elaborate on how 3 might work from a developer perspective? eg "I spot a feature that seems old and obscure. I file a ticket with our product owner. Then magic happens. I either get a "wont fix" response or a new development ticket to remove the feature"
Mar
14
asked How to address, “Is anyone even using this feature?” questions
Feb
11
comment How do I effectively address code-review feedback about class and method names without a suggestion for a better or alternate name?
@DocBrown - In this case I work from home 3 time zones away from the rest of my team at headquarters. We use instant messaging. We use Crucible for code reviews. We get on the phone. Part of this challenge is a lack of face-to-face communication.
Feb
11
accepted How do I effectively address code-review feedback about class and method names without a suggestion for a better or alternate name?
Feb
10
awarded  Yearling
Feb
10
awarded  Editor
Feb
10
revised How do I effectively address code-review feedback about class and method names without a suggestion for a better or alternate name?
edited title
Feb
10
asked How do I effectively address code-review feedback about class and method names without a suggestion for a better or alternate name?
Aug
21
comment Does an Open Source license exist that allows me to retain rights to revoke usage of software/source at any time, for any reason, and without warning?
Also if the software is open source, I would at one point have had the source. Most definitions of open source allow for forks and clones in some way or another. Reality means I can copy your code and do as I please because there is limited enforcement of the requirement to keep the original license on derived works.
Aug
21
comment Does an Open Source license exist that allows me to retain rights to revoke usage of software/source at any time, for any reason, and without warning?
How would you implement this in practical terms? You can revoke my license but how would you learn of "unacceptable" use? How would you enforce the revocation?