The best single document would be the classic Goldberg paper on "What Every Computer Scientist should Know about Floating Point Arithmetic" http://docs.sun.com/source/806-3568/ncg_goldberg.html (originally published as an ACM paper; kindly corrected and republished by the Sun Floating Point Group (Goldberg worked at Xerox). It should be required reading.
Beyond understanding the differences between conventional mathematical arithmetic and what computers actually do, the student really should have a formal introduction to data structures.
Lastly, and why I hung the comment on this one, Numerical Recipes is well known to not be a good numerical choice. Making it the foundation of a class would be a real crime against computing.
Having slept in a CRX, I find removing the passenger seat bizarre to say the least. Sleeping in the passenger seat was way more comfortable than sleeping in the driver's seat.
"Which of course brings us back to the original question about how the airforce plans to attract older computer scientists, if they want to actually employ computer security experts - which the general didn't even attempt to answer." I believe the General observed that civilian experts and consultants can be, and are part of the solution.
But for a more profound exploration of the technological question, why assume that the young are the best choice for the military... see John Scalzi's "Old Man's War". While we don't have OMW technology for the infantry, telepresence, robotics and cyberwarfare are all venues where experience may be more critical than youth.
Realistically, in most school settings any system that *CAN* run a software package probably will at some point. Evil agendas aside, it makes sense for a vendor to offer a steep discount and then apply it to all possible systems... it also makes sense for the school so that they aren't accidentally in violation with draconian penalties attaching.
That such a site license also has the side effect of making it more attractive to just run the site licensed software (less to manage) is part of why a software vendor is motivated to offer steep discounts.
It happens in industrial settings and not just for software from Evil Overloads from Rainy locations.
BSD and Solaris have compatible licenses. So new tecchnologies developed in either can potentially migrate to the other. That is, of course, the point of Open Source isn't it?
A filesystem isn't a kernel, so leaping from the incorporation of ZFS into Darwin to a replacement of Mach and/or the BSD bits with Solaris is a bizarre one.
If putting your email, pictures and search data "out there" isn't enough , the folks at mint will happily store your financial records and access information automatically for you.
Of course, it may just be sooo handy that it's irresistible .
As best I can tell, and it's certified http://docs.sun.com/app/docs/doc/802-1953/6i5uv2sif. I'll bet HP-UX and AIX are too. So is Daryl's claim t that his Unix isn't as marketable as other people's Unixes??
A variety of the better science fiction authors may provide some useful input for the students. If your School district will permit their teaching. Having the students then write some short science fiction would t be the obvious next step.
If that isn't permitted, or doesn't appeal, various historical figures: Newton, and Einstein as obvious starting points... but Feynman and various Crypto experts might be good choices.
Either you should be expert and enthusiastic or you should work something out with some of the Math and Science teachers to coordindate your approaches would be helpful.
Isn't it legit for the accused to hold out for a blood test? Surely those are not nearly as prone to random acts of RFI and should result in residual blood for resampling in the event the Defense should want one.
Indeed, wouldn't the simple fix for the Legal system to mandate blood sampling as a secondary test. That is, the on the spot device could only be used to determine who should have their blood sampled. Of course, anyone refusing to have the blood test would be back in the position of being potentially convicted based on an unsound device but that was a consequence of refusing to submit to testing.
Assuming that the reason Rob knows this case law is because IBM's lawyers are discussing it is... specious. If Rob is involved (or ever has been involved) in a formal Standards process (e.g. served as an ANSI officer) he probably got a briefing (I did when I was;>). Various bits of arcane anti-trust trivia are shot at the poor volunteer, in the attempt to ensure that a handful of someones in the room during deliberations have a clue as to what is, and what is not legitimate discourse. Otherwise ANSI would lose it's special standing (which permits competitors to meet "safely" in terms of Anti-Trust. This is, of course, purely US experience... but many other countries have similar systems.
This is just one o many ways that Rob could have been exposed to such things sans IBM lawyer involvement.
http://techupdate.zdnet.com/techupdate/stories/mai n/Could_Sun_hold_a_key_to_SCO.html/ as an example. For those too busy to read, Sun purchased "expansive" rights to Unix from USL shortly after it was acquired by Novel... long before the deal between Novell and SCO. So Sun's rights predate SCOs. No doubt the legal team imaginative enough to craft the last lawsuits won't let a little matter of time and priority deter them... but one imagines the Courts would.
Clearly you don't debug Operating Systems for a living;> Recall that the first VMs were on the IBM mainframes so that the OS developers wouldn't crash the machine on each other.
Similarly for debugging or otherwise doing risky things with one's OS/configuration. Having a VM makes it a lot faster and easier to recover or to examine a troublesome system.
And even if you only want to run Linux, there are many different distros and kernels to chose from. If you are developing software to be portable, being able to easily/quickly test your code on multiple configurations can go a lost faster with a virtualized set of environments.
One of my earliest computing experiences was at JPL who had massively hacked their Univac environment. The documentation was, of course, rewritten in house. I can still remember a variety of Univac commands, not beaccause they were so obvious, but because the documentation was so good. @pack rat ; @ prep school
But they kept it within reason. Turning the documentation into the equivallent of a game, with ppuzzless is just asking for even fewer people to pay attention
Why did he serve for 4 years and only afterwards whine about his treatment? The time to make a serious point was at while it was happening to pu publicly resign.
Probably too late (they have your real direct dial numbers;>) but in the future, only publish numbers with a front end (like Grand Central http://www.grandcentral.com/howitworks/spam_and_bl ocked) where you can block calls from specific numbers or do a good job of screening;>
My, how US centric can we get. The traditional Scottish Legal system had "Guilty" "Not Proven" and "Innocent". Arguably this is a more logical arrangement than the US system of Guilty|Not and double jeopardy attaching to either (logically Guilty|Innocent should have double jeopardy applying, but "Not Proven" would lend itself quite well to a retrial).
Just because the US has embraced a false binary choice doesn't mean it's a logical necessity.
That batteries can explode is no secret. Managing the charging correctly is critical... and a battery which is on the road to exploding has lots of "markers" (fast heat rise, wrong charging profile, etc.).
It seems to me that low margins are the root cause... for the battery vendor to have QA practices that allow marginal batteries, and for Dell (since they are the ones being fingered, not because I know anything about their practices) to skip additional safety logic beyond whatever minimal standards the battery vendor has specified.
Clearly, there is a market for a "redaction tool" easy to use, and "failsafe" (viz. should not just overwrite the text, it should remove it appropriately and replace the area of the text with blackout material for "the record").
How come Adobe (or others) aren't marketing such a tool?
While I agree absolutely that comments should be written first; I am not so doctrinare as to do so for every block. As others have sagely noted, the comments should not repeat what the code says; it should focus on:
What I intend (especially if it's subtle, involves global state, etc.)
What I assume (about input, the processor, or more generally, the context)
Pointers to suitable external design documents (e.g. paper which introduced the algorithm employed), especially when they are uncommon.
Some of the code I wrote 25 years ago is still in use. While I can't say that I can pick it up after all these years, people who have taken the project over claim that such signposts proved helpful over the years, and the many hands it's passed through since.
Write like your code will live forever. If you do it will, it just might;>
You could just read the source and compare. I believe you will find that (just as advertised) it's SVr4 and not BSD down deep. But why take someone else's word for it, use the Source.... http://opensolaris.org/os/
Slashdot Mirror
The best single document would be the classic Goldberg paper on "What Every Computer Scientist should Know about Floating Point Arithmetic" http://docs.sun.com/source/806-3568/ncg_goldberg.html (originally published as an ACM paper; kindly corrected and republished by the Sun Floating Point Group (Goldberg worked at Xerox). It should be required reading.
Beyond understanding the differences between conventional mathematical arithmetic and what computers actually do, the student really should have a formal introduction to data structures.
Lastly, and why I hung the comment on this one, Numerical Recipes is well known to not be a good numerical choice. Making it the foundation of a class would be a real crime against computing.
Acrobat 8 has redaction tools built in.
Having slept in a CRX, I find removing the passenger seat bizarre to say the least. Sleeping in the passenger seat was way more comfortable than sleeping in the driver's seat.
"Which of course brings us back to the original question about how the airforce plans to attract older computer scientists, if they want to actually employ computer security experts - which the general didn't even attempt to answer." I believe the General observed that civilian experts and consultants can be, and are part of the solution.
... see John Scalzi's "Old Man's War". While we don't have OMW technology for the infantry, telepresence, robotics and cyberwarfare are all venues where experience may be more critical than youth.
But for a more profound exploration of the technological question, why assume that the young are the best choice for the military
Realistically, in most school settings any system that *CAN* run a software package probably will at some point. Evil agendas aside, it makes sense for a vendor to offer a steep discount and then apply it to all possible systems ... it also makes sense for the school so that they aren't accidentally in violation with draconian penalties attaching.
That such a site license also has the side effect of making it more attractive to just run the site licensed software (less to manage) is part of why a software vendor is motivated to offer steep discounts.
It happens in industrial settings and not just for software from Evil Overloads from Rainy locations.
BSD and Solaris have compatible licenses. So new tecchnologies developed in either can potentially migrate to the other. That is, of course, the point of Open Source isn't it?
A filesystem isn't a kernel, so leaping from the incorporation of ZFS into Darwin to a replacement of Mach and/or the BSD bits with Solaris is a bizarre one.
If putting your email, pictures and search data "out there" isn't enough , the folks at mint will happily store your financial records and access information automatically for you.
Of course, it may just be sooo handy that it's irresistible .
As best I can tell, and it's certified http://docs.sun.com/app/docs/doc/802-1953/6i5uv2sif. I'll bet HP-UX and AIX are too. So is Daryl's claim t that his Unix isn't as marketable as other people's Unixes??
A variety of the better science fiction authors may provide some useful input for the students. If your School district will permit their teaching. Having the students then write some short science fiction would t be the obvious next step.
... but Feynman and various Crypto experts might be good choices.
If that isn't permitted, or doesn't appeal, various historical figures: Newton, and Einstein as obvious starting points
Either you should be expert and enthusiastic or you should work something out with some of the Math and Science teachers to coordindate your approaches would be helpful.
Isn't it legit for the accused to hold out for a blood test? Surely those are not nearly as prone to random acts of RFI and should result in residual blood for resampling in the event the Defense should want one.
Indeed, wouldn't the simple fix for the Legal system to mandate blood sampling as a secondary test. That is, the on the spot device could only be used to determine who should have their blood sampled. Of course, anyone refusing to have the blood test would be back in the position of being potentially convicted based on an unsound device but that was a consequence of refusing to submit to testing.
Assuming that the reason Rob knows this case law is because IBM's lawyers are discussing it is ... specious. If Rob is involved (or ever has been involved) in a formal Standards process (e.g. served as an ANSI officer) he probably got a briefing (I did when I was ;>). Various bits of arcane anti-trust trivia are shot at the poor volunteer, in the attempt to ensure that a handful of someones in the room during deliberations have a clue as to what is, and what is not legitimate discourse. Otherwise ANSI would lose it's special standing (which permits competitors to meet "safely" in terms of Anti-Trust. This is, of course, purely US experience ... but many other countries have similar systems.
This is just one o many ways that Rob could have been exposed to such things sans IBM lawyer involvement.
http://techupdate.zdnet.com/techupdate/stories/mai n/Could_Sun_hold_a_key_to_SCO.html/ as an example. For those too busy to read, Sun purchased "expansive" rights to Unix from USL shortly after it was acquired by Novel ... long before the deal between Novell and SCO. So Sun's rights predate SCOs. No doubt the legal team imaginative enough to craft the last lawsuits won't let a little matter of time and priority deter them ... but one imagines the Courts would.
Clearly you don't debug Operating Systems for a living ;> Recall that the first VMs were on the IBM mainframes so that the OS developers wouldn't crash the machine on each other.
Similarly for debugging or otherwise doing risky things with one's OS/configuration. Having a VM makes it a lot faster and easier to recover or to examine a troublesome system.
And even if you only want to run Linux, there are many different distros and kernels to chose from. If you are developing software to be portable, being able to easily/quickly test your code on multiple configurations can go a lost faster with a virtualized set of environments.
One of my earliest computing experiences was at JPL who had massively hacked their Univac environment. The documentation was, of course, rewritten in house. I can still remember a variety of Univac commands, not beaccause they were so obvious, but because the documentation was so good.
@pack rat ; @ prep school
But they kept it within reason. Turning the documentation into the equivallent of a game, with ppuzzless is just asking for even fewer people to pay attention
C# are their fault ... credit where credit is due. C# is from the folks at Redmond, not Sun.
Like VMware or Parallels. Snapshot before any update, if you don't like the result just restore to the snapshot image.
... you can always blow away virtual disk images.
Also handles pesky issues like the claimed inability to really wipe data
Why did he serve for 4 years and only afterwards whine about his treatment? The time to make a serious point was at while it was happening to pu publicly resign.
Probably too late (they have your real direct dial numbers ;>) but in the future, only publish numbers with a front end (like Grand Central http://www.grandcentral.com/howitworks/spam_and_bl ocked) where you can block calls from specific numbers or do a good job of screening ;>
Permutation City, among others. http://www.amazon.com/Permutation-City-Greg-Egan/d p/006105481X/sr=8-1/qid=1171811681/ref=pd_bbs_sr_1 /104-7115273-0999957?ie=UTF8&s=books
My, how US centric can we get. The traditional Scottish Legal system had "Guilty" "Not Proven" and "Innocent". Arguably this is a more logical arrangement than the US system of Guilty|Not and double jeopardy attaching to either (logically Guilty|Innocent should have double jeopardy applying, but "Not Proven" would lend itself quite well to a retrial).
Just because the US has embraced a false binary choice doesn't mean it's a logical necessity.
http://www.amazon.com/Thrice-Upon-Time-James-Hogan /dp/0671319485/sr=8-1/qid=1163699261/ref=pd_bbs_sr _1/104-7429885-2363911?ie=UTF8&s=books dealt with all these issues ... with Hogan's usual insight and wit. A good read, and apparently now an important one!
That batteries can explode is no secret. Managing the charging correctly is critical ... and a battery which is on the road to exploding has lots of "markers" (fast heat rise, wrong charging profile, etc.).
... for the battery vendor to have QA practices that allow marginal batteries, and for Dell (since they are the ones being fingered, not because I know anything about their practices) to skip additional safety logic beyond whatever minimal standards the battery vendor has specified.
It seems to me that low margins are the root cause
Clearly, there is a market for a "redaction tool" easy to use, and "failsafe" (viz. should not just overwrite the text, it should remove it appropriately and replace the area of the text with blackout material for "the record").
How come Adobe (or others) aren't marketing such a tool?
Some of the code I wrote 25 years ago is still in use. While I can't say that I can pick it up after all these years, people who have taken the project over claim that such signposts proved helpful over the years, and the many hands it's passed through since.
Write like your code will live forever. If you do it will, it just might
You could just read the source and compare. I believe you will find that (just as advertised) it's SVr4 and not BSD down deep. But why take someone else's word for it, use the Source .... http://opensolaris.org/os/