One could argue that, since 14-22 year olds are ruled by hormones, the promise of naked boobies is far too much for them to resist, and is therefore marketing to children since kids like boobies.
Remember, there is no quantity of juice sufficient to stop a male from staring at the hindquarters of a female in estrus.
Tuvalu profited immensely from the sale of their ccTLD. I can't blame them for doing it because it was in the best interest of their country, and will generate a revenue stream for this otherwise poor island nation.
Or are countries no longer allowed to sell their resources anymore?
Apple already solved your problem with Expose. (Pronounced Ex-po-zay). Move the mouse to a corner of the screen or push a function button and all the windows slide into view, which is run by the GPU. click on one and that window moves to the front. And you can do it with windows inside applications by moving to another corner or pushing a different key. Or you could move all windows off of the screen to get at the desktop.
It's revolutionized how I use my Mac. I don't think this will help very much because you have to look closely at the tilted windows instead of just seeing smaller versions of the windows you've seen before.
One more thing about Windows:
He is constantly saying how the Linux guy is overpaid because you gave him $50,000 up front and you're only paying the Windows guy $10,000 a month.
/me is looking forward to going home to my smart, sexy geek woman. And my fiance, too...
Maneuvering: RCS system on a cylinder is easy to design.
Attachment: Put a handle on the container for the station's robotic arm. Open the outer airlock door and put the suits inside using the arm, then close the door and repressurize the airlock.
I read the article, but maybe I misunderstood it. I've worked on some pretty crappy dev teams before. 8-10 hours a week in 'team meetings' with marketing and management, listening to their inane and impossible ideas, making sure we had a 'vision statement' and that it was updated. Then I go back and have to deal with people interrupting me for stupid things, coworkers talking loudly (the same ones who complain they can hear my music through my headphones), and other devs who can't work without someone holding their hand. At the end of that job I was begging to be locked in a room to get away from them. (This, however, wasn't at a professional software company.)
But if you say 2 hour meetings weekly to cover deliverables and glorious silence locked in a dark room with my music blaring, and supervisors who email me to communicate, then I'm up for that.
I get that too. Turns out my number is the same as the fax number for an out-of-business hotel in my area. I've already faxed back the companies whose numbers were on caller ID, but several others are not available.
Then again, it might be old wardials from the Dead Phone Call office...
Solution: 1. Comment your code 2. Make programs do only one thing, and then make them talk together. Make components, not programs 3. Wikipedia for development. Functionality and business logic are therefore documented by the creator and supplemented by testers, creating a very large database of information that can be tapped for support.
I was thinking more along the lines of an expendable rocket. Maybe even solid fueled. No need to launch a pressurized craft with wings and life support to get two suits up there. I mean, they're not NASA!
I tried to work out if an 8 ton rocket (controlled from the ground) would work, but can't find enough information.
Well, opening the door or setting deadlines is good. i.e. "I'm going to check on your progress in three days."
However, sending out an email saying "Everyone needs to meet and sing kumbaya to built group unity and get together on how this thing works" is stupid. Give me a task, let me do it, and if it doesn't work, fire me.
Or they could adopt Unix Philosophy. If a program does one thing well and stores all data in flat text files, working independently on programs is easy, since the formats are agreed upon.
I do most of my good dev alone in a room. I even make deadlines! I used to work for someone who used to work at JPL in the 1970s managing software development. One developer would ride his Harley Davidson wearing a cape and goggles and lock himself in a room with the necessary hardware and ask that Twinkies and Coke be left outside the door. They didn't see him for a week, but the code was good. It was for the Voyager program, so we know it was good.
There's a difference between not trusting an ex-frat boy alone in a room and a responsible software developer in a room. Treating everyone on a team the same just breeds discontent. If people work well alone and can be trusted to do so, don't make them waste their time in meetings.
I was thinking more along the lines of using White Knight to send up a cargo craft that carried some suits. I wouldn't think it would take more than 8,000 pounds (max-lift capability for white knight) to get to LEO from 50,000 feet.
This would probably take Burt a week and $500,000 to develop, but NASA would take a year or two and tens of millions of dollars to do the same thing.
And if it's too much for one White Knight to handle, maybe they could launch two of them and mate the rocket at altitude.
I'm not enabling anything. Once it gets so gunked up that he can't do my mom's books on it, then I'll tell him "You should use firefox, you should have gotten a Mac, and until you promise me you'll do either of those things, I will not fix your computer."
Slashdot Mirror
Remember, there is no quantity of juice sufficient to stop a male from staring at the hindquarters of a female in estrus.
Am I missing something? What's this a reference to?
The only windows I can see from my cube are on my monitor. Having no (real life) windows in the building wouldn't affect me very much.
Or are countries no longer allowed to sell their resources anymore?
And what's funnier is that you can change it back if you want to.
I'm a funny guy.
Copycats. Get it? They're all cats, and they get copied. (Or copy other things, in a couple cases. See? It's a double entendre. Or something.
It's revolutionized how I use my Mac. I don't think this will help very much because you have to look closely at the tilted windows instead of just seeing smaller versions of the windows you've seen before.
But for every prude we have a goatse.
What do you mean I should have alphabetized the cleaning supplies???
Now maybe a private company can develop it for 2% of the cost and we'll have cheap, environmentally benign power.
He is constantly saying how the Linux guy is overpaid because you gave him $50,000 up front and you're only paying the Windows guy $10,000 a month.
/me is looking forward to going home to my smart, sexy geek woman. And my fiance, too...
Maneuvering: RCS system on a cylinder is easy to design. Attachment: Put a handle on the container for the station's robotic arm. Open the outer airlock door and put the suits inside using the arm, then close the door and repressurize the airlock.
But if you say 2 hour meetings weekly to cover deliverables and glorious silence locked in a dark room with my music blaring, and supervisors who email me to communicate, then I'm up for that.
Then again, it might be old wardials from the Dead Phone Call office...
Solution:
1. Comment your code
2. Make programs do only one thing, and then make them talk together. Make components, not programs
3. Wikipedia for development. Functionality and business logic are therefore documented by the creator and supplemented by testers, creating a very large database of information that can be tapped for support.
I tried to work out if an 8 ton rocket (controlled from the ground) would work, but can't find enough information.
However, sending out an email saying "Everyone needs to meet and sing kumbaya to built group unity and get together on how this thing works" is stupid. Give me a task, let me do it, and if it doesn't work, fire me.
Or they could adopt Unix Philosophy. If a program does one thing well and stores all data in flat text files, working independently on programs is easy, since the formats are agreed upon.
Maybe he's dyslexic, you insensitive clod!
[/sarcasm]
I do most of my good dev alone in a room. I even make deadlines! I used to work for someone who used to work at JPL in the 1970s managing software development. One developer would ride his Harley Davidson wearing a cape and goggles and lock himself in a room with the necessary hardware and ask that Twinkies and Coke be left outside the door. They didn't see him for a week, but the code was good. It was for the Voyager program, so we know it was good.
There's a difference between not trusting an ex-frat boy alone in a room and a responsible software developer in a room. Treating everyone on a team the same just breeds discontent. If people work well alone and can be trusted to do so, don't make them waste their time in meetings.
And it would give Rutan a chance to show off Tier 2.
This would probably take Burt a week and $500,000 to develop, but NASA would take a year or two and tens of millions of dollars to do the same thing.
And if it's too much for one White Knight to handle, maybe they could launch two of them and mate the rocket at altitude.
Blackmail is an excellent way to promote FOSS!
White Knight can carry 8,000 pounds to 53,000 feet. Maybe this is enough to send a rocket to LEO with a few extra spacesuits?
Of course, he also uses AOL, so I'm not sure how well that will work in WINE.