welcome to: http://www.wowowbiz.com/
The website wholesale for many kinds of fashion shoes, like the nike,jorda-n,prada,ad-idas, also
including the jeans,shir-ts,bags,ha-t and the decorations. All the products are free shipping, and the the
price is competitive, and also can accept the paypal payment.,after the payment, can ship within short
time. http://www.wowowbiz.com/
Greybeard Stories: The Jamming Gyro
21–30 of 47 posts
Re: Greybeard Stories: The Jamming Gyro
#22Earlier quoted context omitted.
No amount of testing the former will lead you to realize the latter. Sure, you might happen to come to the realization while writing the test, but you might do so over breakfast too. You're a bit more likely to do it during a time you've set aside to fully consider potential failure scenarios.
I guess I can't argue with that, as it's essentially unfalsifiable. But it's worth pointing out that writing a unit test, which is the subject that started this discussion, is definitely not a time when you're "fully considering potential failure scenarios". Unit tests are narrow and focused, and aimed at verifying features. What you're talking about is something I'd call white box QA. Which is valuable, though it's…
Unit tests are narrow and focused, and aimed at verifying features. What you're talking about is something I'd call white box QA. Which is valuable, though it's essentially just an extension of design, and has the same limits.
It seems like most negative arguments regarding "unit tests" start by defining them as a small subset of what can be usefully tested, and then arguing against the value of testing such an incomplete subset.
I don't see the point of drawing such an arbitrary line. I leverage "unit" tests to automatically test units of code as completely as possible (not just 'verify features'), and I expect the same of tests that others write.
Re: Greybeard Stories: The Jamming Gyro
#23You need to round up a voting posse to help push your stories up onto the front page. Doesn't take much, just 1-2 HN users who like your stuff and will toss you a few votes when something goes up.
Edit: Of course they need to be people who really like your stuff. Not suggesting he game HN, just that he let fans know when there's a post they can check out.
Re: Greybeard Stories: The Jamming Gyro
#24Seems implausible to me. Rather than a self-destruct, it would be more plausible to just disable the explosive trigger altogether. If a torpedo fails to hit target for whatever reason (including, but not limited to the original problem) you don't necessarily want it to explode in some random place. Nor is it clear how, if this failure did occur with loss of all hands, we would ever have known about it. Despite this,…
Possibly because you don't want your adversary to get one of your unexploded torpedos and copy / reverse-engineer / exploit a design flaw. Tactically that'd be far more devastating than losing a ship or two.
Re: Greybeard Stories: The Jamming Gyro
#25You need to round up a voting posse to help push your stories up onto the front page. Doesn't take much, just 1-2 HN users who like your stuff and will toss you a few votes when something goes up. Edit: Of course they need to be people who really like your stuff. Not suggesting he game HN, just that he let fans know when there's a post they can check out.
It would be a very sad thing if that's what it took to get stories to the front page. Unfortunately it seems that quite a few people have adopted your 'tactic', I always find it a little suspicious when links have been posted literally minutes ago and already have 3-5 upvotes without any comments, especially if they then scroll off the new page without receiving further upvotes.
My guess is that those are simply sockpuppets used for the initial votes. The sad thing is that plenty of times the strategy seems to work.
Re: Greybeard Stories: The Jamming Gyro
#26Earlier quoted context omitted.
For what its worth I just read all three and really dug them! It might help to use a more regular blog format so people can post comments?
When I get back from my meeting I'll put links on them back to here - thanks for the idea. I should've thought of that.
I think that you can quickly add a commenting system to static sites with disqus.com. I would also consider adding Google Analytics or piwik.org to better understand the hits you are getting.
Re: Greybeard Stories: The Jamming Gyro
#27They should've written unit tests obviously ;-)
Written as a joke, but in my line of work (embedded systems) this is a big problem. Because most of a product's operation may depend on external inputs, it can be impossible to write a suite of unit tests that are useful without also building and automating hardware to generate the external stimuli.
We've come up with some creative responses to this, but nothing remotely like what's possible when you're just moving data around and not, e.g., testing the hardware's ability to start a 300hp diesel engine at it's low-temperature limit.
Re: Greybeard Stories: The Jamming Gyro
#28This will be the last of these stories for a while. The previous two stories pretty much sank without trace, so I thought I'd finish and submit this one, then stop writing them up and re-think the effort. In case you're interested: http://news.ycombinator.com/item?id=996250 http://news.ycombinator.com/item?id=994358
I hadn't seen the other two, but I've now read (and enjoyed) all three. Thanks!
Same here...
Re: Greybeard Stories: The Jamming Gyro
#29Earlier quoted context omitted.
Testing can verify that your software works within the space of behavior that you already know about. It can't make up for your failure to understand the problem fully. Thinking about correctly testing software is generally one of the best ways to improve your understanding of the problem. I quite often find bugs during unit testing simply because I'm forced to think about how the software will break, rather than thi…
Sure, writing tests can find design bugs. But that's not really the question at hand here. The specifics are that we have a clear and obvious requirement ("torpedo should self-destruct if it turns a full 360 degrees") that turns about to be missing an important point ("EXCEPT IF IT IS ON THE BOAT"). No amount of testing the former will lead you to realize the latter. Sure, you might happen to come to the realization…
I think his point is that the test itself isn't the useful bit. The useful part is that thinking about what to test can uncover bugs.
This is what FMEA (Failure Modes Effects Analysis) does: you assume failures of every part of the system, rank their likelihood and the end effect and see how your design handles it. A good FMEA assumes everything will fail and analyzes the impact. Unfortunately, comprehensive FMEA is expensive and time consuming so it's usually only done for critical subsystems.
Re: Greybeard Stories: The Jamming Gyro
#30Earlier quoted context omitted.
When I get back from my meeting I'll put links on them back to here - thanks for the idea. I should've thought of that.
I think that you can quickly add a commenting system to static sites with disqus.com. I would also consider adding Google Analytics or piwik.org to better understand the hits you are getting.
I'll look at those over the weekend - thanks.