3,087 reputation
1126
bio website sites.google.com/site/…
location CT, USA
age 49
visits member for 4 years, 3 months
seen Dec 16 at 13:40

What do I look for in a post? Clarity and Contribution.

NO vote: If the post is clear, but makes no contribution OR if the post is unclear, but makes a contribution (though I will try to improve the clarity either by comments or direct edit).

UP vote: If the post is clear and makes a contribution.

DOWN vote: If the post is unclear and makes no contribution (though I will try to see if I've missed something by commenting).


Nov
5
awarded  Revival
Sep
19
awarded  Yearling
Jul
25
comment I know JavaScript really well, but i bomb coding interviews
Try Project Euler for some samples.
May
23
reviewed Approve How do I prove or disprove “god” objects are wrong?
Apr
23
comment Term for accidental features
Any feedback on the downvote? Just wondering.
Apr
15
awarded  Nice Answer
Feb
2
awarded  Custodian
Feb
2
reviewed Approve Should I use automatic properties?
Oct
21
comment When should I increment version number?
Do you do QA before issuing the hotfix? It's a release. If not of the full product, then of the hotfix.
Oct
17
comment Long term planning and agile?
Get another customer! ;-)
Sep
19
awarded  Yearling
Aug
20
comment Disillusioned with agile; how do you prepare for life after release 1.1?
There is no silver bullet!
Aug
16
comment Is SQLite a sensible option for data logging?
The other nice thing about using a simple text file is, if you split it by day, you can use the same technique to zip up old files using a cron job, saving disk space. Like this
Aug
12
comment Organising staggered user story in Scrum
@BryanOakley: Ya... "final product" and "software" doesn't necessarily compute to me. The OP used "release_s_". To me, that means each user story will be in a "final" product (i.e. not necessarily all stories in all releases).
Aug
12
comment Organising staggered user story in Scrum
@MetaFight: Understood. "Pedantic"? Possibly, I've been beaten up here for less. :-)
Aug
12
comment Organising staggered user story in Scrum
"Could be" and "aren't" are two different things.
Aug
12
comment Organising staggered user story in Scrum
Tempted to -1 for your first sentence. Of course user stories are descriptions of the final product! They serve zero purpose if they are not. I think you mean something different from what you've said.
Jul
26
revised How to deal with requirements and use cases in this kind of situation?
Expanding compound nouns. Some spelling corrections.
Jun
10
awarded  Nice Answer
May
25
comment How to design a good receipt number
Does it matter if someone can guess a receipt number?