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.
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.
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.
"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.
Companies that provide snacks and drinks expect an ROI. And they all know how to offshore your overpaid code-monkey ass so shut up and get back to work.
I've aimed microwave STLs before and that was a royal pain in the ass. In the hundreds of gigahertz range aiming the antennas has got to be a bitch. And damn well better make sure the mast and mountings will never shift under wind pressure.
RTFA. ..especially this paragraph:
"The water enters the first facility at 42.8 degrees Fahrenheit (6 degrees Celsius) and exits at 53.6 F (12 C). It's pumped to a second site, which it leaves at 64.4 F (18 C), and a third, which it leaves at 75.2 F (24 C). It's then sent to a heat pump and used to heat local homes and offices."
Lynx and Pine are certainly not for everyone, but I'm glad to hear that some young people are still using this stuff.
Pine rocks. I remember getting reprimanded for chatting at work while at Apple in the late 90's. I dragged my ignorant boss into my lab and showed him that what he assumed to be chat was actually an e-mail program, and he changed his tune when he realized that I was not only not-chatting, but using a highly-efficient e-mail program to get my work done.
In the early 90's I developed a website for a public science center. My boss thought I was wasting time optimizing web pages for Lynx as well as Mosaic but changed his tune when he started receiving thank-you e-mails from public library administrators throughout the U.S. At the time, web browsers were not ubiquitous so it was important to implement solutions with old-school tools as well as new-school tools.
In these two cases, using old-school technology raised skepticism from key stakeholders: management. But note that in order to please all stakeholders I also had to reduce my own skepticism of emerging technologies.
Great CIOs, demonstrate a balance between understanding the business and understanding the technology in their communications. Fortunately I've worked for a couple of these in my career. Few and far between.
Slashdot Mirror
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.
The private sector pays for all the research anyway, so bully for them.
I'll protect my family with a de-personalized gun, thanks.
Companies that provide snacks and drinks expect an ROI. And they all know how to offshore your overpaid code-monkey ass so shut up and get back to work.
Actually, this scheme to appease the dumb masses by reducing H1B visas will simply encourage U.S. companies to set up offshore development centers.
French? Multiculturalism is hella whack.
Apple Computer should be commended for following the Law. Congress itself should be offshored.
I've aimed microwave STLs before and that was a royal pain in the ass. In the hundreds of gigahertz range aiming the antennas has got to be a bitch. And damn well better make sure the mast and mountings will never shift under wind pressure.
RTFA. . .especially this paragraph:
"The water enters the first facility at 42.8 degrees Fahrenheit (6 degrees Celsius) and exits at 53.6 F (12 C). It's pumped to a second site, which it leaves at 64.4 F (18 C), and a third, which it leaves at 75.2 F (24 C). It's then sent to a heat pump and used to heat local homes and offices."
Lynx and Pine are certainly not for everyone, but I'm glad to hear that some young people are still using this stuff. Pine rocks. I remember getting reprimanded for chatting at work while at Apple in the late 90's. I dragged my ignorant boss into my lab and showed him that what he assumed to be chat was actually an e-mail program, and he changed his tune when he realized that I was not only not-chatting, but using a highly-efficient e-mail program to get my work done. In the early 90's I developed a website for a public science center. My boss thought I was wasting time optimizing web pages for Lynx as well as Mosaic but changed his tune when he started receiving thank-you e-mails from public library administrators throughout the U.S. At the time, web browsers were not ubiquitous so it was important to implement solutions with old-school tools as well as new-school tools. In these two cases, using old-school technology raised skepticism from key stakeholders: management. But note that in order to please all stakeholders I also had to reduce my own skepticism of emerging technologies.
Great CIOs, demonstrate a balance between understanding the business and understanding the technology in their communications. Fortunately I've worked for a couple of these in my career. Few and far between.