Slashdot Mirror

You do not understand. But you will: http://www.ece.cmu.edu/~ganger/712.fall02/papers/p 761-thompson.pdf

When will interface designers learn that it's faster if you don't have to take your hands off the keyboard every three seconds?

Actually, there are a large number of studies that say the opposite is generally true, even for expert users who know the keystroke commands from memory (indeed, one could argue that the letter and symbol keys on a keyboard are all examples of this). The time 'saved' by keeping your hands on the home row is more than wasted by the time that it takes to recall a key-combination. It doesn't seem that way because you are actively thinking about the command, so your time sense is focused on the activity, whereas the time spent mousing around is more or less 'blank time', since the hand-eye coordination needed to match the pointer to the pointed item is more or less 'handled in hardware' once the decision of which command to use is made.

Naturally, there are several cases where keyboard commands are faster than menus, however. One is when there is a very common operation which has a permanently assigned action key, with no key-combos. Another is in the case of an expert user entering a complex, multi-operation command line, versus having to gesture the same actions; however, a case such as that is generally complex enough that the real optimal solution is to create a script of the command, even for a single use instance (some systems, such as Oberon, facilitate this by allowing you to invoke any arbitrary selected text as a script - indeed, in Oberon a menu item is nothing more than a section of text that is pinned to a given location and 'pre-selected' so that it activates on a single click). Third, multi-level menus require the user to select and target successive items, which is the same cause of slow-down in keystroke commands. Fourth, there are many cases of poorly considered 'graphical' tools that require multiple passes to home in on the target (Raskin's example of a 'visual thermometer' that requires you to adjust the height of the 'mercury' column versus simply entering the degrees into a textbox, comes to mind). Finally, 'adaptive' menus are invariably worse than keystrokes, because the changes disrupt the pattern of actions. In each of these last three cases, the reason the mouse is slower is because the layout of the UI stymies the ability of the user to habituate to them, making it a matter of design rather than a flaw with pointing devices themselves.

Ironically enough, given all the 'quick bars' around in certain systems, the worst response time in most cases is for using icons. The problem is that you have to associate the icon with not only the image it represents, but also the action it causes, and the connection between them is not always as obvious to a user as it was to the developers. The difficulty increases rapidly with the number if icons on the screen, especially if there are two or more similar icon images that need to be differentiated. Many design theorists today argue that icons should only be used sparingly, and only to represent specific physical devices (i.e., a disk drive).

What we really need are more designers who understand usability analysis, and actually use it to determine how much effort a given design takes to use.


Usability in Website and Software Design
AskTog Interaction Design Section
The Raskin Center for User Interface Design
Human-Computer Interface Institute at CMU
Human-Computer Interaction Resources on the Net
Bibliography of Human-Computer Interface Studies
Usability Tips and Tricks
Overiview of GOMS Analysis
Us

Snow White is an old tale (re)told by the Brothers Grimm. http://www.cs.cmu.edu/~spok/grimmtmp/042.txt

I know that our courts and copyright system are a big mess, but I can't concieve how Disney could claim ownership of Snow White without being laughed out of court. Indeed too many movies to mention have been made under that title by studios other than Disney -- just do a title search on the IMDB.

We might be closer than we think to complex hands at least. Here is a project at CMU that is building an anatomically correct hand. As we move towards making anatomically correct body parts, we will also learn more about making anatomically correct brain parts. From there, it might not be too far to get to a human-like "brain".

Try out this book. Very nice. Head to #lisp on freenode to get help on how to install a Lisp environment.

Lisp is a very nice language with very little notation to get confused about (you need an editor to help you with the notation, though). It was my first language, and I still love it.

Think of it as having some hidden Easter Eggs or a game.
Perhaps It'll come back with something interesting if you listen to things like Joe Wecker - DeCSS Song or Wierd Al Yakovic - Windows 95 Sucks

Could anyone else care about what you listen to?

If your collection is really Da BOMB, it'll include
JJ Walker - DYNOMITE!
Simon and Garfunkle BRIDGE Over Troubled Water
Moody Blues - TUESDAY AFTERNOON
The Vogues - FIVE O'CLOCK World

http://gamedev.cs.cmu.edu/spring2004/

It is initially tough to convice some of the older, conservative faculty that learning how to write games is something that CMU should be teaching its students. But on second-look, one realizes that what students really learn is fundamental to all of computer science: efficient data structures, effective resource management and memory usage, good user interfaces, handling images and multimedia content, process threading and multi-user networking, etc. However, with a game programming class, you get to teach all of this stuff in a fun way, where students are extremely self-motivated to learn it all.

The class has been quite popular, and many of my students have gone off to work in the game development industry. The best feedback I have received has been from students who enjoyed the fact that their final game projects have been the the only pieces of software they have written during their university days that had a lifetime beyond the course itself. I think game programming is an excellent way to teach coding skills and working as part of a development team, which is a very practical part of any CS curriculum.

There are downloadable movies of some of the recent lab projects here (all written in portable OpenGL code:

http://gamedev.cs.cmu.edu/spring2004/labs/lab1/
http://gamedev.cs.cmu.edu/spring2004/labs/lab2/

http://gamedev.cs.cmu.edu/spring2004/

It is initially tough to convice some of the older, conservative faculty that learning how to write games is something that CMU should be teaching its students. But on second-look, one realizes that what students really learn is fundamental to all of computer science: efficient data structures, effective resource management and memory usage, good user interfaces, handling images and multimedia content, process threading and multi-user networking, etc. However, with a game programming class, you get to teach all of this stuff in a fun way, where students are extremely self-motivated to learn it all.

The class has been quite popular, and many of my students have gone off to work in the game development industry. The best feedback I have received has been from students who enjoyed the fact that their final game projects have been the the only pieces of software they have written during their university days that had a lifetime beyond the course itself. I think game programming is an excellent way to teach coding skills and working as part of a development team, which is a very practical part of any CS curriculum.

There are downloadable movies of some of the recent lab projects here (all written in portable OpenGL code:

http://gamedev.cs.cmu.edu/spring2004/labs/lab1/
http://gamedev.cs.cmu.edu/spring2004/labs/lab2/

http://gamedev.cs.cmu.edu/spring2004/

It is initially tough to convice some of the older, conservative faculty that learning how to write games is something that CMU should be teaching its students. But on second-look, one realizes that what students really learn is fundamental to all of computer science: efficient data structures, effective resource management and memory usage, good user interfaces, handling images and multimedia content, process threading and multi-user networking, etc. However, with a game programming class, you get to teach all of this stuff in a fun way, where students are extremely self-motivated to learn it all.

The class has been quite popular, and many of my students have gone off to work in the game development industry. The best feedback I have received has been from students who enjoyed the fact that their final game projects have been the the only pieces of software they have written during their university days that had a lifetime beyond the course itself. I think game programming is an excellent way to teach coding skills and working as part of a development team, which is a very practical part of any CS curriculum.

There are downloadable movies of some of the recent lab projects here (all written in portable OpenGL code:

http://gamedev.cs.cmu.edu/spring2004/labs/lab1/
http://gamedev.cs.cmu.edu/spring2004/labs/lab2/

http://gamedev.cs.cmu.edu/spring2004/

It is initially tough to convice some of the older, conservative faculty that learning how to write games is something that CMU should be teaching its students. But on second-look, one realizes that what students really learn is fundamental to all of computer science: efficient data structures, effective resource management and memory usage, good user interfaces, handling images and multimedia content, process threading and multi-user networking, etc. However, with a game programming class, you get to teach all of this stuff in a fun way, where students are extremely self-motivated to learn it all.

The class has been quite popular, and many of my students have gone off to work in the game development industry. The best feedback I have received has been from students who enjoyed the fact that their final game projects have been the the only pieces of software they have written during their university days that had a lifetime beyond the course itself. I think game programming is an excellent way to teach coding skills and working as part of a development team, which is a very practical part of any CS curriculum.

There are downloadable movies of some of the recent lab projects here (all written in portable OpenGL code:

http://gamedev.cs.cmu.edu/spring2004/labs/lab1/
http://gamedev.cs.cmu.edu/spring2004/labs/lab2/

CMU's masters programs, overall, aren't really that interesting. (The exceptions I can think of offhand are the robotics and entertainment technology programs, and even those are direct career path -- the former into big-time university or defense industry R&D, the latter into being an EA slave). The information and networking program (which is NOT run out of the CS department!) is positively disgusting and run by total idiots -- about three clicks in any direction from that front page will find you some technocrat mumbo-jumbo about cybercrime and cyberthis and cyberthat. These are the people who testify before congress every now and then saying how Internet users need to be protected from themselves.

You can use the chips for optical navigation too. I played around with one for an introductory robotics class, here.

Journal of the trip: NHAA journal and information on the software, RALPH

NHAA showed that it's possible to do at highway speeds (60+ mph), using 1995 technology. The construction issues are a challenge. From the journal, it sounds like RALPH handled construction reasonably well, but there certainly are construction sites that even many humans can't successfully navigate...

Journal of the trip: NHAA journal and information on the software, RALPH

NHAA showed that it's possible to do at highway speeds (60+ mph), using 1995 technology. The construction issues are a challenge. From the journal, it sounds like RALPH handled construction reasonably well, but there certainly are construction sites that even many humans can't successfully navigate...

Sounds familiar

The link between TFA and Asimov's novel is faint, if not null.

I think a closer analogy is the HeartLander. Not exactly a submarine, but still a small mobile "vehicle" to deliver treatment.

Here's some info, relevant material pulled:

"There are many different types of radiation effects, many of which cause both mechanical and electrical degradation. Mechanical defects consist of ones that cause properties of materials to be altered. For instance, such defects could alter the mechanical, optical, thermal and electrical properties of metals. Electrical degradation would physically occur during operation. Due to the accumulation of alpha particles, bits can be flipped during operation and cause system failure"

There's more in-depth info out there, but most of the detailed stuff I was trying to access requires memberships in consortiums etc. I was a little surprised by the bitflipping.

Thats a pretty vague question, and you didn't provide enough information to really answer it right, but here's some recommendations.

Assuming you have managed switches, collecting per-port data with SNMP is a great first start. I think Cricket (http://cricket.sourceforge.net/ is a great system for collecting this data, but I prefer Drraw (http://web.taranis.org/drraw) for graphing the data. For an example of the power available by combining these two tools, see http://stats.net.cmu.edu/

Once you've got that, install Net-SNMP's snmpd on your host and collect & graph interface stats for your unix servers as well. If you don't have managed switches this may be good enough on its own. You can also graph load average, memory usage, etc.

For actually analyzing your network traffic I suggest Argus, http://www.qosient.com/argus. It's a network traffic auditing tool, think of it as tcpdump for flows instead of packets, or as netflow on crack. You can easily record complete flow statistics for your entire network for later perusal. All you need is a network topology that allows you to sniff most/all of the traffic. A span port on a switch is usually sufficient. If you've already got a snort server and it has enough processing capacity you can just run argus on the same host.

Speaking of which, if you don't have a snort server you probably want one. Nessus as well.

For monitoring/alerting I recommend Mon (http://www.kernel.org/software/mon), but then I'm biased.

And once you've tracked down what machine(s) are causing the problem, do you have records of which machines belong to which users? (Insert plug here for CMU's NetReg system for management of DNS and DHCP, which provides that. (http://www.net.cmu.edu/netreg) I'm biased on this one as well...)

Oh, and my money would be on poorly timed overlapping network backups, saturating a switch uplink. Just a guess...

Thats a pretty vague question, and you didn't provide enough information to really answer it right, but here's some recommendations.

Assuming you have managed switches, collecting per-port data with SNMP is a great first start. I think Cricket (http://cricket.sourceforge.net/ is a great system for collecting this data, but I prefer Drraw (http://web.taranis.org/drraw) for graphing the data. For an example of the power available by combining these two tools, see http://stats.net.cmu.edu/

Once you've got that, install Net-SNMP's snmpd on your host and collect & graph interface stats for your unix servers as well. If you don't have managed switches this may be good enough on its own. You can also graph load average, memory usage, etc.

For actually analyzing your network traffic I suggest Argus, http://www.qosient.com/argus. It's a network traffic auditing tool, think of it as tcpdump for flows instead of packets, or as netflow on crack. You can easily record complete flow statistics for your entire network for later perusal. All you need is a network topology that allows you to sniff most/all of the traffic. A span port on a switch is usually sufficient. If you've already got a snort server and it has enough processing capacity you can just run argus on the same host.

Speaking of which, if you don't have a snort server you probably want one. Nessus as well.

For monitoring/alerting I recommend Mon (http://www.kernel.org/software/mon), but then I'm biased.

And once you've tracked down what machine(s) are causing the problem, do you have records of which machines belong to which users? (Insert plug here for CMU's NetReg system for management of DNS and DHCP, which provides that. (http://www.net.cmu.edu/netreg) I'm biased on this one as well...)

Oh, and my money would be on poorly timed overlapping network backups, saturating a switch uplink. Just a guess...

Hey, Microsoft just sponsored a puzzle-solving competition here at CMU. And they're (or at least Bill is) sponsoring a large portion of a new CS building for our school. I guess that their contributions in the US just aren't that visible.

As a past participant in the AUVSI/IARC, I've noticed that only a few teams have tried using a fixed-wing approach. This is likely because the "building entry" requirement is difficult to accomplish without navigating in close proximity to the buildings. Yet since Mars has such a thin atmosphere, one would think that a rotary-wing aircraft would be much less practical for NASA's purposes.

However, if the NASA competition allows for helicopters, there are several IARC teams that have developed vision-based (no GPS) navigation capability for their rotary-wing platforms. In particular, Carnegie Mellon University, Georgia Tech, and USC all appear to have successfully developed this capability.

The only other requirement listed is "extending and retracting a probe to precisely hit multiple targets on the ground." This statement is pretty vague, and doesn't sound very trivial, but there is precedent.

So far anyway, there doesn't appear to be much any new technology needed to win this NASA competition. Contending institutions that have developed visual navigation techniques can probably just integrate an extra computer/camera to a cheap commercial UAV, optimize their algorithm for the competition terrain type, and interface their controller with the UAV's mission planner. Hopefully NASA will soon add some requirements that will level the playing field a bit and provide them with some usable R&D.

Some history about the Linux flap:
http://www.cs.cmu.edu/~dst/DeCSS/Gallery/archive/g arfinkel.txt

Some other page I found by accident about file sharing:
http://www.eff.org/IP/P2P/howto-notgetsued.php

...when you can code that way?

"How to decrypt a DVD: in haiku form". It's quite elegant, really.

No, this isn't for every situation. Common hardware is a must (or at least a real help). But, it does neatly solve other common issues, like system builds.

A freind of mine does just this on his home system about once a month (well, and at work...as he says, we're not in the business of installing an OS by hand anymore). I'm going to take the same plunge. Pick an automated system rebuild method, test it, build new systems with it and rebuild your systems on some sort of regular basis. There are lots of caveats to the Microsoft methods (ADS/RIS... single partition systems, you need BOOTP, blah blah blah). And, the image-based methods can be tricky (Ghost? Oh come now). Other options like nLite might help, too.

It may not be what the doctor ordered, but it will simplify your life when you need to build a new workstation. And, if one gets pokey beyond the reach of the other tools mentioned, blow on a new image. Plus, if you're using XP, you can use folder redirection to keep the user files someplace else, so you don't neccesarily have to rely on draconian policies regarding where they should save files (well, you can't let them save files just anyplace, so a few policies may be in order).

Is this the ultimate insult that the best way to manage Windows workstations is to automate reinstalling them? Well, maybe, depending on your viewpoint. But, it is what it is, so we build automated methods to learn to live with the limitations.

Humbly submitted, here are some of my bookmarks on the subject:
http://www.cmu.edu/computing/andrew-windows/andrew -ris-server.html
http://ani.sourceforge.net/
http://www.autoitscript.com/autoit3/
http://support.microsoft.com/default.aspx?scid=kb; en-us;299441
http://www.livejournal.com/users/lotso/1863.html
http://isg.ee.ethz.ch/tools/realmen/
http://www.microsoft.com/windows2000/techinfo/howi tworks/management/remoteover.asp
http://www.microsoft.com/whdc/archive/risover.mspx
http://www.microsoft.com/technet/prodtechnol/windo wsserver2003/library/TechRef/3983c4a4-e6ff-4664-84 25-28ec740474b1.mspx
http://unattended.sourceforge.net/
http://www.windowsitpro.com/Articles/Index.cfm?Art icleID=7109
http://www.microsoft.com/technet/prodtechnol/windo ws2000serv/evaluate/featfunc/intmiror.mspx

You seem to be asking more about the basics of Project Management than specific tools. For a fair overview of the subject try this in Wikipedia. The grand-daddy of Project Management for software development is SEI-CMM.

These communist bastards must be stopped. We'll start with this guy.

There are a lot of web sites that are taken down routinely, a few of them have been politically-motivated (ie. raisethefist.com was taken down for a while and Sherman Austin arrested and detained.

However, on the issue of the French riots, I agree that raping and destroying your own community's property is bad, I agree with them.

And as for rights, of course the US/Europe/France is going to view them as illegal - no government wants something that takes away some of their power. Personally though, I could care less what the government and a company tells me I can or cannot do, rights aren't given out because of a piece of paper. Where there is authority, there is no freedom.

Actually, it uses the Mach kernel with FreeBSD userland tools. It has its own abstraction layer called IOKit for device drivers and its own window server called Quartz. So no, it doesn't have a BSD kernel, it doesn't use BSD drivers, and it doesn't use X11 for its "pretty interface." It's not "BSD" any more than Windows is "BSD" due it including a BSD-licensed network stack. Ask your grandma to buy you one of the new I-MAXES for your birthday, d00d. Maybe you'll learn something.

My theory: - Making developers work over-hours is how bad managers (try to) compensate for their poor management skills (bad planning, skipping of requirements analysis, not saying NO when they should, no prioritizing, ignoring how client dependencies affect deadlines, etc, etc, etc) and keep projects within the budge.
Yes, YES, YES!!!
this is well documented and studied by the software enginerring institute :http://www.sei.cmu.edu/
End of project heroics and long hours are clear indicators of bad managemnt, budgeting, and planning.

Here.

Ah, Sweepstakes...the search for the smallest, lightest girls ad the biggest, strongest guys...the scrambles for rubber bits to be analyzed in the lab...

From the CMU Phd in computer science application page.

"Submit three letters of recommendation. Recommenders should know you relatively well and be able to evaluate the quality of your previous work. At least two should be from faculty or recent employers. With the online application, letters will be requested and submitted electronically. Letters of recommendation are due by January 3. All deadlines are final. Letters received after this date may not be considered in the review of your application."

As I've said, most require two or three. I've never heard of a program which reqires more than that.

http://www.cs.cmu.edu/afs/cs.cmu.edu/academic/clas s/15740-f97/public/platform/21164.pdf

When the Alpha first came out, people were aghast at the unbelievable deep pipeline. DEC had opted to sacrifice IPC at the altar of clock speed. Some choice quotes (that article is from 1994):

The new chip achieves its performance by continuing to emphasize clock speed over complexity. Digital clocks its processors two to three times faster than competitive high-performance products while accepting a lower number of instructions per cycle (IPC). Although other processors deliver much better IPC, none comes close to reaching a high enough IPC to counteract Digital's advantage in clock speed. The Speed Demons continue to outpace the Brainiacs. ...
System designers must cope with the very high power dissipation of the 21164 chip.

Intel's bet was the same as DEC's. Pay the price of long pipelines to get high clock rate.

What nailed Intel was that leakage current blew up as they scaled the process down, so power use rose far faster than expected. Had they not hit a wall in terms of process scaling, Intel would have P4 for sale at over 10Ghz, and they'd still have the performance crown.

Bad bet. But not as stupid as people make it sound.

Here's a paper that describes a system at CMU they built for such purposes.

I hope you equally as appalled by attempts to circumvent other laws ... http://www.cs.cmu.edu/~dst/DeCSS/Gallery/ ... http://www.grandtimes.com/rosa.html

If you're interested in reading the actual research paper involved (as opposed to a journalist's interpretation), it's readable here - pdf file, but lots of graphs, tables and pictures, so I'll forgive them.

Pretty un-sage. And pretty un-Forbes-like. Sounds a lot like a certain UFO cult, actually.

> BASH BACK. If you get attacked, dig up dirt on your assailant and feed it to sympathetic bloggers. Discredit him.

1. Spot who is attacking us.

2. Start investigating them promptly for FELONIES or worse using our own professionals, not outside agencies.

3. Double curve our reply by saying we welcome an investigation of them.

4. Start feeding lurid, blood sex crime actual evidence on the attackers to the press. (LRH)

- Dead Agenting

> ATTACK THE HOST. Find some copyrighted text that a blogger has lifted from your Web site and threaten to sue his Internet service provider under the Digital Millennium Copyright Act. That may prompt the ISP to shut him down. Or threaten to drag the host into a defamation suit against the blogger. The host isn't liable but may skip the hassle and cut off the blogger's access anyway. Also:Subpoena the host company, demanding the blogger's name or Internet address.

"Reporters are a kiss of death unless one really is an expert PR man himself. Reporters have to be handled and well. If truly friendly, they have to be wooed. If not they have to be handled. The routine is (1) Whisper of a bad story (2) Get a lawyer (3) Threaten suit (4) Totally discredit using the technique of the Dead Agent caper which MUST be understood in full."

- Dead Agenting

> SUE THE BLOGGER. If all else fails, you can sue your attacker for defamation, at the risk of getting mocked. You will have to chase him for years to collect damages. Settle for a court order forcing him to take down his material.

ENEMY: [Suppressive Person] Order. Fair game. May be deprived of property or injured by any means by any Scientologist without any discipline of the Scientologist. May be tricked, sued or lied to or destroyed.

- Fair Game

and

"The purpose of [a lawsuit] is to harass and discourage rather than to win. The law can be used very easily to harass, and enough harassment on somebody who is simply on the thin edge anyway, well knowing that he is not authorized, will generally be sufficient to cause his professional decease. If possible, of course, ruin him utterly."

- "A Manual on the Dissemination of Material" (1955 edition)

If you're running a UFO cult, and you're doing so in the media environment of the 1950s-1970s, L. Ron Hubbard's policies will work just fine. He may have been a raging nutbag, but he knew where the defects were in the news-gathering and news-dissemination networks of his day were, and his cult developed policies to exploit them successfully.

Most organizations have adapted to the new reality, and have come up with effective ways of managing the media - whether you agree with the Swift Boat Veterans for Truth, or whether you agree with Michael Moore and moveon.org, both groups have become effective in getting their respective messages out.

The Co$, ironically, is the final proof -- part of Cult doctrine is that the words of Hubbard must be regarded as both true, and immutably so. By its own doctrines, the Co$ has been unable to adapt to the new media reality -- because (by virtue of the doctrine of the immutable truth of Hubbard's writings) to deviate from these 1950s/60s/70s-style media manipulations is heresy. The fact that the cult has gone from "that kinda-weird ultra-wealthy Hollywood religion" to "a money-grubbing UFO cult that's the laughingstock of the planet" is testam

Couldn't we just send a photographer down to the Atacama Desert in Chile and start up an insurance program for the poor with the savings?

-Eric

Coda works even when nodes disconnect, for instance with network outages or mobile computing. Plus, there is a Windows client, if that's the way your shop swings.

From the Link Grammer link you provided:
http://bobo.link.cs.cmu.edu/link/
As of December 2004, we are releasing the parser under a new license; the license allows unrestricted use in commercial applications, and is also compatible with the GNU GPL (General Public License). You can view the license here. We are also releasing version 4.1b, which is identical to version 4.1 (released in 2000) except that the licensing statements reflect the new license.

Sun's license for OpenOffice is LGPL
http://www.openoffice.org/license.html

If you're curious, Mike Montemerlo graduated with his Ph.D. from CMU's Robotics Institute right about when Sebastian Thrun defected from CMU to the better weather found in Palo Alto, in 2003. Mike's thesis work was advised by both Thrun and Red Whittaker, as shown here

So, yes, a lot of work on Stanley was based upon work done at CMU, but let's not forget the addition of vision work done at Stanford as well as the help of the VW people, as I'm sure they were both critical in Stanley's success.

Been done -- ten years ago! Highways are much easier than the desert, especially if you DO have a driver on board who can intervene. Google for "No Hands Across America", e.g.
http://www.cs.cmu.edu/afs/cs/user/tjochem/www/nhaa /nhaa_home_page.html

Maybe it has not incurred to anyone yet, but if you check out Sebastian Thurn's homepage, and download his C.V. http://robots.stanford.edu/cv.html (bottom of the page) or even check on the home page of the Carnegie Mellon University http://news.cs.cmu.edu/Releases/demo/33.html, he said correctly in German that he did obtain his VORDIPLOM. He, however translates this as having attained his B.Sc.. If you check with the German translation engine Leo (provided by the University of Munich), and enter the name VORDIPLOM into the box dict.leo.org, the following items come up: intermediate diploma das Vordiplom p intermediate examination das Vordiplom p pre-degree das Vordiplom p. Given that a Vordiplom is NOT a degree leading to a profession, but a pre-degree and that as a rule of thumb, it should be attained after TWO years of study, and a B.Sc. (Honours degree) can take up to FOUR years, Mr. Thrun has either a poor command in the English language, or for his U.S. employers, he has not told the truth, I am afraid to say. I think academic integrity should also entail the respective person's C.V.!

ISR has exactly these goals. It is essentially the concept of running a Virtual Machine that can migrate between different computers. Migration can happen via the network or via portable storage devices such as USB keychains. The ISR project was also covered in a previous Slashdot story here.

There is a webcast on campus here (Carnegie Mellon):

"A live Webcast of the Oct. 8 Grand Challenge through the Mojave Desert will be shown on campus in Breed Hall in Margaret Morrison Carnegie Hall.

"The Webcast will begin at 9 a.m. and end at 6:30 p.m. Breakfast will be served from 9 to 11 a.m. and lunch from 12:30 to 2:30 p.m."

http://www.cmu.edu/cmnews/extra/050927_redteam.htm l

This is new?
http://www.ece.cmu.edu/research/piperench/index.ht ml (the oldest working link I can find on this area) is about 6 years old. I did have links that were older(they just don't work anymore)...

Meet the author, a recent M.S. grad from CMU who interned as a testing programmer on The Sims 2 and did a little work on Ultima X Online.

http://www.andrew.cmu.edu/user/bkj/

What about AFS which stands for Andrew File System. It was developed at CMU and allows dynamic backup of data (it automagically copies you data to different physical volumes). I've never even heard about data being lost on an AFS system and it supports very high security too. Then just build your code on top of the UNIX commands or AFS file API. But then again, it might be a bit much for your requirements. I don't know of a windows client version but one might exist. And the wayback part you might have to write yourself but it might be supported as well. Check it out if you are interested.

PS: A quick look at some fast Java code. (It is a bit dated but gives you some idea what I am talking about.)

Hmm ... that's a little archaic. The page complains about Java performance in JDK 1.1, and appears to be based on a site (http://www.cs.cmu.edu/~jch/java/optimization.html ) that hasn't been updated since 1998.

Maybe just include a link to this.

Back in 2000, CMU switched to IMAP and started reccommending Mulberry as the standard mail client. I was pretty surprised by this. CMU had previously used open-source or locally developed software. Some of the locally-developed software was pretty quirky and hard to support, but they had generally been trying to make it open source or switch to open source. (For example they switched from AMS to IMAP, and were working on switching from AFS to CODA.) So I was pretty surprised when they started reccommending a closed source mail client. I remember thinking, "A closed-source, third party app? I wonder how long that's going to last..." Today I got the answer - It lasted about 5 years.

Shortly after they started using Mulberry, they started using some other closed-source third-party service called Blackboard. I wonder how long that's going to last...