Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
Christ Almighty, don't be such a douche if you want people to appreciate your point. You just mocked the OP, who posted a valid - and I suspect common - point of view, while providing nothing but a laundry list of vague, unverifiable comparisons. I don't doubt you know what you're talking about, but dispose of the mocking tone and add some meat to your argument
In that case, your only chance is the brake overriding the gas (a process which should have been true from the beginning anyway).
Or you can put the car into neutral... or cut the power entirely (yes, both these things work, even with push button ignition. I tested both on a country road shortly after the initial floor mat recall). In emergency situations, it's critical to keep your head together and recognize your options.
That said, when is the last time a spoofed e-mail actually made it to your inbox?
About 10 minutes ago, and multiple times every day.
Find a guy with a little programming knowledge who can sit in the office next door and write docs for Jim.
Perfect answer. I've worked with several folks like Jim over the years, and consider myself to be in the same vein. Yes, we can and will write documentation if we have management that requires it. But we'd much rather be having fun solving problems, and wise management will make sure that is what we are doing most of the time. Right now I work for a very small research company - the entire tech staff is two engineers (not "software engineers" - computer vision & robotics) plus two programmers. Our code is messy and poorly commented with no documentation - we get away with this because it is research grade code, and because our team is so small. We (the engineers) understand it just fine. The poor programmers who must port it to other languages simply have to put the blinders on and copy the functionality. We could document the code to death, but that wouldn't be any substitute for the fundamental knowledge in physics, statistics and algorithms required to *really* understand the code. When and if we grow into a production environment where many people will have to support (and understand) the code, I trust our management will be wise enough to hire other folks to do the bulk of the documentation, with help as necessary from the engineers. Because there will always be more profitable things for us to be doing, which we actually enjoy.