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).


Jul
25
comment I know JavaScript really well, but i bomb coding interviews
Try Project Euler for some samples.
Apr
23
comment Term for accidental features
Any feedback on the downvote? Just wondering.
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! ;-)
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.
May
25
comment How to design a good receipt number
Does it matter if someone can guess a receipt number?
May
15
comment Moving to Python (SciPy and NumPy) for Scientific Computing
@BЈовић: The price of Octave and SciLab? Free!
May
7
comment Decimal to 17-bit 2's Complement Signed Number
@Mark Deleted copy on DSP.SE. As World Engineer says, you're better off flagging for migration than multiple-posting.
May
1
comment Pairwise testing, not possible to say which combinations is faulty?
I've used this technique to find a particularly hard-to-resolve embedded device bug. We had several different possibilities, and enumerated a very similar set of possible scenarios. We ran 9 of the devices overnight with the suggested setup parameters, and BAM! we had isolated our problem very quickly.
Apr
25
comment Testing multi-threaded race conditions
My only question is: How big an anthill should I use? (+1 BTW).
Apr
24
comment Can I demand code quality on a project I've gotten
+1 for taking it back to the company. They (or the management) may be unaware of the poor quality. If they are unaware and do something about it, good! If they are aware or don't' do anything about it, fire them! (Don't use them again... and tell your friends :-).
Apr
23
comment Approach to simplifying an algorithm
@WorldEngineer Ha ha!
Apr
22
comment What is the best way to prove that in-code documentation is greater than extensive external documentation?
I generally agree, but Donald E. Knuth might not. :-)
Apr
20
comment What skills are essential for professional programming that are not commonly taught in schools?
@CharlesE.Grant: I've taught graduate-level courses in programming and related topics for several years. Even graduate students have a hard time understanding why they should use a revision control system of any sort. And when they grudgingly start to use it, they seem to get very confused by it very quickly. +1 to Mason for raising it as an important unlearned topic.
Apr
15
comment Improve Bad testing
+1: United Technologies has what they call "Relentless Root Cause Analysis". It is very useful for getting to the bottom of things.