"We've thumbed our nose at the rules of good programming, typed out code that is totally bad -- and we've lived. There were no lightning bolts from the programming gods. Our desktops didn’t explode. In fact, our code compiled and shipped, and the customers seemed happy enough."
No, but breaking programming rules doesn't cause a problem today. It causes one tomorrow. It's akin to gluing a loose electric plug to the outlet. It solves the problem (very well!), but when you later need to unplug the TV, it's going to be needlessly difficult.
Tim Cook (white, male) is concerned that there are too many whites and males at Apple. I have a good idea how he can help both of those numbers immediately.
There is a terrific incentive. Take a look at the ads in your ISP's bill and in the junk mail they send you every other week. Remember the last time you talked to customer service? What did they try to sell you during the call? An up-sell to a faster connection. Most people can't tell the difference between their local connection being saturated and the data getting clogged further down the line. When their 15/5 service no longer cuts the mustard, the more savvy users will bring up speedtest.net and see that they're getting the speed they paid for. So they think, "Gee, if my Netflix and YouTube are too slow, I must need more bandwidth!" The rest probably think the Internet is like a computer and you need to upgrade every few years to keep the same relative speed.
Looking at the picture in the Businessweek article, there appears to be one small button on either side of the screen (the left one is for hazard lights, I can't tell what the right one is) and nothing else.
"...Franz von Holzhausen, can barely contain himself as he talks about the design of the Model S. “It’s like the leap of faith Apple (AAPL) took with the iPhone,” he says, explaining why the car has a touchscreen instead of the usual physical buttons."
This is monumentally wrong. Touch screens succeed on a phone because a phone is a portable device and the touch screen is lighter and smaller. Physical controls are preferable for humans because they model the physical world to which we've adapted. In a car, you need to use the controls without taking your eyes off the road. This means location by feel is important. A touch screen can't provide that.
It seems the entire design world has this backwards, include appliance manufacturers. I hate the buttons on my oven.
The problem is that there's no suitable output from a code review. Other tasks are definable, e.g., delivering code that meets the requirements. A code review doesn't work like that. It's a nice thing to do for your peers to sufficiently examine their code in a review. But nobody gets kicked for doing a half-assed review. They do get kicked for missing a delivery. So when rubber meets the road, a thorough code review tends not to happen.
The Epson QX-10, QX-16 and Equity computers were standard issue for Drew University (drew.edu) undergrads starting in 1984. They've got to have a box of old disks in a dark corner of the computer center.
Close... The spammers who are getting spammed are now spamming the spammer spammers. What we need to know is if anyone has anything that hasn't got any spam in it.
I have a blog that covers DVD authoring on Linux. Primarily it is concerned with creating a subtitled DVD from video shot on a digital camcorder. (Hearing loss runs in my family.) It also touches on transcoding, automated menu creation and other peripheral topics. What's different about it is that rather than try to be an authoritative source (which I'm not), I've chronicled my efforts, error messages and all.
Also consider universal remotes have the problem of insufficient knowledge about the devices they control. For instance, the power button is a toggle. It doesn't know if the TV is on or off, so if your macro turns the TV on when you choose "Play DVD" and your TV is already on, it will turn it off.
These remotes won't be truly useful until there is both command and query capability.
Slashdot Mirror
> its Connected Watch, which is its fist watch
So it must be waterproof, but I'd imagine it might go missing in some inconvenient places.
"We've thumbed our nose at the rules of good programming, typed out code that is totally bad -- and we've lived. There were no lightning bolts from the programming gods. Our desktops didn’t explode. In fact, our code compiled and shipped, and the customers seemed happy enough."
No, but breaking programming rules doesn't cause a problem today. It causes one tomorrow. It's akin to gluing a loose electric plug to the outlet. It solves the problem (very well!), but when you later need to unplug the TV, it's going to be needlessly difficult.
A defikopter does what, now?
Is this article for real? I can't tell.
Tim Cook (white, male) is concerned that there are too many whites and males at Apple. I have a good idea how he can help both of those numbers immediately.
There is a terrific incentive. Take a look at the ads in your ISP's bill and in the junk mail they send you every other week. Remember the last time you talked to customer service? What did they try to sell you during the call? An up-sell to a faster connection. Most people can't tell the difference between their local connection being saturated and the data getting clogged further down the line. When their 15/5 service no longer cuts the mustard, the more savvy users will bring up speedtest.net and see that they're getting the speed they paid for. So they think, "Gee, if my Netflix and YouTube are too slow, I must need more bandwidth!" The rest probably think the Internet is like a computer and you need to upgrade every few years to keep the same relative speed.
Looking at the picture in the Businessweek article, there appears to be one small button on either side of the screen (the left one is for hazard lights, I can't tell what the right one is) and nothing else.
"...Franz von Holzhausen, can barely contain himself as he talks about the design of the Model S. “It’s like the leap of faith Apple (AAPL) took with the iPhone,” he says, explaining why the car has a touchscreen instead of the usual physical buttons."
This is monumentally wrong. Touch screens succeed on a phone because a phone is a portable device and the touch screen is lighter and smaller. Physical controls are preferable for humans because they model the physical world to which we've adapted. In a car, you need to use the controls without taking your eyes off the road. This means location by feel is important. A touch screen can't provide that.
It seems the entire design world has this backwards, include appliance manufacturers. I hate the buttons on my oven.
I'm assuming you're assuming they're assuming.
The problem is that there's no suitable output from a code review. Other tasks are definable, e.g., delivering code that meets the requirements. A code review doesn't work like that. It's a nice thing to do for your peers to sufficiently examine their code in a review. But nobody gets kicked for doing a half-assed review. They do get kicked for missing a delivery. So when rubber meets the road, a thorough code review tends not to happen.
> Despite urging by the Yemen-based al Qaida leader Anwar Al Anlaki, Karim rejected the use of a sophisticated code program[...]
I don't think a guy with a job description of "blow yourself up" cares what HQ thinks.
Hedley: "You said Alan Turing twice."
Applicant: "I like Alan Turing."
The Epson QX-10, QX-16 and Equity computers were standard issue for Drew University (drew.edu) undergrads starting in 1984. They've got to have a box of old disks in a dark corner of the computer center.
There's verifiable proof that there's no Microsoft-owned code in Linux: It doesn't crash!
Close... The spammers who are getting spammed are now spamming the spammer spammers. What we need to know is if anyone has anything that hasn't got any spam in it.
"[...]would dwarf the challenges and expenses spawned by the Y2K computer dilemma."
So, in this engineer's opinion, we've got more systems using VINs than dates?
You picked a bad day to post this question!
I use growisofs for DVD+RW discs. There are command line examples in my blog. The blog is mostly about video, but also covers data.
I have a blog that covers DVD authoring on Linux. Primarily it is concerned with creating a subtitled DVD from video shot on a digital camcorder. (Hearing loss runs in my family.) It also touches on transcoding, automated menu creation and other peripheral topics. What's different about it is that rather than try to be an authoritative source (which I'm not), I've chronicled my efforts, error messages and all.
Excellent points!
Also consider universal remotes have the problem of insufficient knowledge about the devices they control. For instance, the power button is a toggle. It doesn't know if the TV is on or off, so if your macro turns the TV on when you choose "Play DVD" and your TV is already on, it will turn it off.
These remotes won't be truly useful until there is both command and query capability.