The point, though, is that teaching young students to use computers often replaces teaching them more important and difficult subjects. While it may have been useful for you to learn three languages when you were 11, it is apparent that your education did not focus on proper spelling or grammar. We are converging on a time where everyone is developing their computer skills and it is the ability to communicate well that separates the wheat from the chaff.
I agree that basic computer skills should be taught to the young, but as a language would be taught, and not as a substitute for the conventional methods that enforce human interaction and real learning.
We are all well aware of Welchia and the fact that it caused nearly as much nuisance as Blaster. Let us learn from this and never again release a worm for good purposes.
Kazaa recently withdrew their suit after they realized they were suing a 60 year old woman with an iMac. This follows the current trend of trying to give a random old lady a heart attack.
I took a class where we used something called a Wiki. The concept is simple. You have a community of people who all contribute to the content of the site and even have the power to create their own pages. In our case, we submitted our homework on it, and we could have other people review and edit it (and keep track of the changes). We had a glossary that we kept building, and we had our own journals, and it worked really well for us, until the end, when we had so much content that we actually slowed the server down.
The best part is that it's pretty easy to set up, really easy to use (once you get the hang of it), and really cool for everyone involved.
I remember reading that the Eisenhower Highway System was designed so that 1 mile in 5 was straight with the idea that it could be used as a landing strip in case of emergency. I'm sure many of these abandoned airstrips in the middle of the forest in the middle of nowhere serve the same purpose.
No discussion about the simpsons is complete without mention of www.snpp.com (for springfield nuclear power plant), which is the largest database on the simpsons. It has descriptions of each episode, lists of errors, lists of references, essays, everything the simpsons related that anyone could ever want.
But what is this doing on the front page? This is something you ask a smaller specialized forum, not the slashdot community. I can hardly see how this will generate meaningful or intellectual discussion, and I can definitely not see how this is news for nerds or stuff that matters.
well, it seems a matter of course that it would not be publicly available. As I recall, many geologic surveys and records, blueprints and articles were pulled from public access in the interest of national security. Imagine the damage one could wreak with a blueprint of the city, its weaknesses, its strengths, its tunnels. This is obvious sensitive information that could be used for evil purposes.
On the other hand, if stripped of some of the more sensitive information, it could be an extremely valuable tool, not only in terms of advertisements or community building, but also for game development and online community building, designing, city planning, and other things.
As a student at Oregon State University (go Beavs) I had the opportunity to listen to Schwartz explain the situation in which he was currently a victim. There is no doubt in my mind that his behavior was professional and responsible. He was doing a favor, volunteering his time and clock cycles, to improving a gaping security hole. It is the responsibility I would hope for from any professional.
To be condemned for his behavior sends a message to all that security problems should be ignored to be exploited later by the truly dangerous, rather than exposed by the people whose job it is to improve the security of his and his peer's domains.
I was glad to have heard him speak to us, and I think this man is certainly not the criminal he is accused. Rather than condemn him, we, as a community that believes in improving security and protecting systems, should support him in his endeavor to beat a law that was inappropriately inaugurated on him.
The full text of flatland is available at
http://www.geom.umn.edu/~banchoff/Flatland/
or
http://www.information-resources.com/Library/libra ry73.html
or
http://www.jollyroger.com/xlibrary/Flatland:ARoman ceAE/Flatland:ARomanceAE1.html
or if you use a TI-89, check this out
http://www.ticalc.org/archives/files/fileinfo/151/ 15174.html
The composite can only fix the crack once, and the forces that caused the crack are still there, so the composite WILL break again. The only solution is a better design that won't put so much stress on that composite or replacing the composite with a new one. Further, the glue is only a quick fix, a hack, that should only last until an engineer is available to fix the material with a new one. Someone mentioned earlier that the glue should be colored so that it indicates cracks (though it would be very disconcerting to go over an older bridge and see bright green spots on all the girders).
While the technology is cool, it's a wrong step in terms of safety and in terms of proper design in engineering applications.
I found the article a little repetitive, but he had good ideas. The point is, do we want a better program or a better programmer? Right now, the programmer costs more than the program, so it would be in the best interest of the company to take shortcuts. If using an object oriented language makes the development process shorter, at the expense of clock cycles, then management will certainly go with oop. They lose money when the programmer takes time, but not when the program does at home. Besides, you've got the cycles to spare.
However, what do you use to develop the language? obviously you can't use that language. For example, the java platform can't be written in java. (I'm not sure, but I think it's written in C). The point is, OOP is great for getting a product out fast, but it's a little dirty and doesn't do the job as thoroughly as a higher level language.
Either you pay the programmer extra so they can make a more efficient program, or you pay the programmer to produce. In terms of management, which makes more sense?
Shouldn't we, as an act of kindness to the country of Australia, mirror the site to which we are referred in the article? After all, we don't want Australia/.ed.
Slashdot Mirror
The point, though, is that teaching young students to use computers often replaces teaching them more important and difficult subjects. While it may have been useful for you to learn three languages when you were 11, it is apparent that your education did not focus on proper spelling or grammar. We are converging on a time where everyone is developing their computer skills and it is the ability to communicate well that separates the wheat from the chaff.
I agree that basic computer skills should be taught to the young, but as a language would be taught, and not as a substitute for the conventional methods that enforce human interaction and real learning.
We are all well aware of Welchia and the fact that it caused nearly as much nuisance as Blaster. Let us learn from this and never again release a worm for good purposes.
Kazaa recently withdrew their suit after they realized they were suing a 60 year old woman with an iMac. This follows the current trend of trying to give a random old lady a heart attack.
I took a class where we used something called a Wiki. The concept is simple. You have a community of people who all contribute to the content of the site and even have the power to create their own pages. In our case, we submitted our homework on it, and we could have other people review and edit it (and keep track of the changes). We had a glossary that we kept building, and we had our own journals, and it worked really well for us, until the end, when we had so much content that we actually slowed the server down.
The best part is that it's pretty easy to set up, really easy to use (once you get the hang of it), and really cool for everyone involved.
This is the site for it http://c2.com/cgi/wiki
I remember reading that the Eisenhower Highway System was designed so that 1 mile in 5 was straight with the idea that it could be used as a landing strip in case of emergency. I'm sure many of these abandoned airstrips in the middle of the forest in the middle of nowhere serve the same purpose.
No discussion about the simpsons is complete without mention of www.snpp.com (for springfield nuclear power plant), which is the largest database on the simpsons. It has descriptions of each episode, lists of errors, lists of references, essays, everything the simpsons related that anyone could ever want.
But what is this doing on the front page? This is something you ask a smaller specialized forum, not the slashdot community. I can hardly see how this will generate meaningful or intellectual discussion, and I can definitely not see how this is news for nerds or stuff that matters.
We've put all our power in a winded man.
it would be New New York. and it would be built over the ruins of the old one.
well, it seems a matter of course that it would not be publicly available. As I recall, many geologic surveys and records, blueprints and articles were pulled from public access in the interest of national security. Imagine the damage one could wreak with a blueprint of the city, its weaknesses, its strengths, its tunnels. This is obvious sensitive information that could be used for evil purposes.
On the other hand, if stripped of some of the more sensitive information, it could be an extremely valuable tool, not only in terms of advertisements or community building, but also for game development and online community building, designing, city planning, and other things.
read a book!
As a student at Oregon State University (go Beavs) I had the opportunity to listen to Schwartz explain the situation in which he was currently a victim. There is no doubt in my mind that his behavior was professional and responsible. He was doing a favor, volunteering his time and clock cycles, to improving a gaping security hole. It is the responsibility I would hope for from any professional.
To be condemned for his behavior sends a message to all that security problems should be ignored to be exploited later by the truly dangerous, rather than exposed by the people whose job it is to improve the security of his and his peer's domains.
I was glad to have heard him speak to us, and I think this man is certainly not the criminal he is accused. Rather than condemn him, we, as a community that believes in improving security and protecting systems, should support him in his endeavor to beat a law that was inappropriately inaugurated on him.
The full text of flatland is available at
http://www.geom.umn.edu/~banchoff/Flatland/
or
http://www.information-resources.com/Library/libra ry73.html
or
http://www.jollyroger.com/xlibrary/Flatland:ARoman ceAE/Flatland:ARomanceAE1.html
or if you use a TI-89, check this out
http://www.ticalc.org/archives/files/fileinfo/151/ 15174.html
The full text of flatland is available at http://www.geom.umn.edu/~banchoff/Flatland/ or http://www.information-resources.com/Library/libra ry73.html
or
http://www.jollyroger.com/xlibrary/Flatland:ARoman ceAE/Flatland:ARomanceAE1.html
or if you use a TI-89, check this out
http://www.ticalc.org/archives/files/fileinfo/151/ 15174.html
The composite can only fix the crack once, and the forces that caused the crack are still there, so the composite WILL break again. The only solution is a better design that won't put so much stress on that composite or replacing the composite with a new one. Further, the glue is only a quick fix, a hack, that should only last until an engineer is available to fix the material with a new one. Someone mentioned earlier that the glue should be colored so that it indicates cracks (though it would be very disconcerting to go over an older bridge and see bright green spots on all the girders). While the technology is cool, it's a wrong step in terms of safety and in terms of proper design in engineering applications.
It's a geocities site. They can handle boatloads of traffic.
I found the article a little repetitive, but he had good ideas. The point is, do we want a better program or a better programmer? Right now, the programmer costs more than the program, so it would be in the best interest of the company to take shortcuts. If using an object oriented language makes the development process shorter, at the expense of clock cycles, then management will certainly go with oop. They lose money when the programmer takes time, but not when the program does at home. Besides, you've got the cycles to spare. However, what do you use to develop the language? obviously you can't use that language. For example, the java platform can't be written in java. (I'm not sure, but I think it's written in C). The point is, OOP is great for getting a product out fast, but it's a little dirty and doesn't do the job as thoroughly as a higher level language. Either you pay the programmer extra so they can make a more efficient program, or you pay the programmer to produce. In terms of management, which makes more sense?
Shouldn't we, as an act of kindness to the country of Australia, mirror the site to which we are referred in the article? After all, we don't want Australia /.ed.