In some ways DRM could promote innovation; it's the use of black box code for anything that concerns me. Is there a way to implement DRM in a white box instead?

I think you've nailed it, Bob. Though it's been years since I was a D&Der/Traveller, the appeal was truly the collective storytelling. It was also a great pretext to by hexagonal graph paper.

I'd rather keep hiring Chinese programmers than move our company's operations to Mexico. However, we might consider flying some Mexicans here to clean the garbage out of the parking lot.

The source article is very careful to identify Navajo as a "North American Indigenous language". There is a difference, so please don't disparage the English as a non-native language.

Actually, most US export containers are filled with scrap paper and chemical waste.

Yeah, right.

Just because.

Isn't Slashdot already a Q&A site for network engineers and others?

As a former cabbie, I have undying allegiance to the Crown Vic. You simply need the horsepower, even in urban environments. The Crown Vic, or its quieter cousin the Grand Marquis, are also able to last forever if the basic maintenance intervals are taken seriously.

so don't be surprised. The taxpayers, by the way, are not the client. The goverrnment is the product owner. Therein lies the rub.

yeah I remember thicknet from working at Cal in the early 90s. you had to be precise about where to tap in, as it was all about knowing wavelengths and how improper termination attenuates signals, not much different from an earlier job I had working with waveguide and microwave systems.

Reminds me of my college days, when Marriott hired a bunch of retards to bus the cafeteria tables and wash our dishes. An obviously exploitable group, which made everyone else feel like they were waiting for Godot.

The world is much more peaceful because people are armed.

"I write excellent product specs" is bullshit, for bad requirements lead to most of the sloppy code out there. The choice of "programming project manager" as a title is a clue that anonymousreader has no clue of what else goes into SW development. Things like requirements gathering, test planning, code review, release planning, etc. Igorance is further displayed with the expectation that programmers "test their code"; assuming that they should, wouldn't this be restricted to unit testing? Are the same programmers also responsible for the system, integration, and user acceptance testing? Quality assurance is not the programmer's responsibility. Don't blame code-flunky for your incompetence.

I seem to remember using one of these during a GTA mission.