Hey, at least Steve-o paid people to put up with his bullshit. Open source necessarily entails community; corporations do not.
Yes, you will have less time and money if you have kids, but it's not an entirely fair comparison. You don't know how much happier or more fulfilled having kids will make you feel until you do (and isn't that a big part of why we do our hobbies?). For many of us (most of us, hopefully) the deal works out in our favor because we're happier than we would be if we had all that time and money to spend on our old hobbies. It's a net gain, but it's easy to present as a net loss because it's the unknown.
I'm actually looking forward to wireless charging. The reason is that one of the primary reasons a piece of portable electronics becomes useless to me is the charging connector gets worn out. It a simpl fact that plugging it in and out multiple times a day and stressing it in odd directions is going to cause it to simply not work over time.
I'd love a situation where I just sat my devices on a pad for them to charge and even to sync data at faster-than-wireless speeds. That way I only had to plug them in in limited situations, (such as travel).
Also, it would be nice from a device standpoint. Right now I have an octopus of micro-usb chargers on my chest of drawers. I have half a dozen devices that need charging through the week. I'd love to just leave the ones I don't use on the mat and have them charged and ready to go when I took them.
My wife had an n900. she dropped it and cracked the digitizer. (Not the glass, not the screen, the digitizer.) She has a pin set since it's synced to an exchange server. we assumed there must be SOME way to get the photos off of it. Nope. With a pin set, you can't connect it to a computer. And without a digitizer, you can't do squat. Now, all the pictures she's taken on the system since it was last backed up are stuck on it forever.
I feel bad for her. Not only does my Samsung Epic 4G have a SD card w/ all my photos, google+ automatically uploads them to picasa and syncme automatically downloads them to my home fileserver.
The agribusinesses are right, it is anti-science, and it is bullshit. In this case, the side with the truth also has the money. Imagine that.
Code reviews. Make sure everybody on the team has seen everyone else's code and understands it. Do regular (monthly, bi-weekly, whatever) code reviews. Code quality will go up.
Egoless programming. Don't allow anybody to become a rock star or the only person who can read or write any bit of the code. Everybody must be cross-trained on someone else's code, at least. The team is responsible for the code, so make sure people are polite during code reviews. Polite doesn't mean downplaying problems. It means pointing out problems without being an internet jackass. Nobody "wins" at code review, but the code quality goes up. This works as well as any other software development methodology, with lower overhead, less dedication and no cargo cult behavior.
Professionalism. Foosball tables and other wank infantilize the staff. You're adults, you're there to write high quality code. Keep regular hours, understand that you're there to code, you don't want anybody pulling all-nighters or living in their office. Code quality will go up because it's taken seriously.
Encourage openness. Encourage experimentation. Allow radical changes once in a while. Good programmers want to be understood, respected, listened to and believed. They don't want to be pigeonholed into some kind of geek stereotype, they don't want internet fame and glory, they don't need you to do their laundry for them, they don't need to be coddled.
Reduce (but don't eliminate) time pressure. Code quality wants to go up. It's prevented from going up because management wants you to get to market as fast as possible. Everything you do that improves quality takes time away from feature development. Make it clear that moving deadlines up means fewer features *always*, lower quality *never*. Never sacrifice quality to satisfy a suit.
+1. I haven't yet seen an empirical argument (as opposed to an argument from first principles) that biodiversity is necessary. I wouldn't want to throw it away, but in this world everything is a tradeoff, and the value of warm fuzzy feelings diminishes rapidly when lives—or simply ways of life—are on the line. When scientists warn of catastrophic species loss, the wooey green types are invited to imagine Bambi and her friendly woodland friends rather than the lichens and cockroaches with different colored dots on them that are what's being discussed. We can lose as many species as it takes to keep this species alive; an Earth without humans is absolutely meaningless and absurd. Let's see the proof, rather than conjecture and assumption founded on essentially religious notions of the "earth mother," that it actually matters before we decide to halt human progress in its tracks.
Most programmers doing these kinds of calculations are using floating point numbers, which already have interesting rounding error failure modes that most programmers don't understand. This is going to exacerbate the problem.
Decreasing hardware intelligence and counting on programmers to make up the difference hasn't been a winning proposition in a long time.
They work equally well, but only one of them extends your life and reduces your stress level.
I'm sure your anger and ranting has been a tremendous political boon to wherever it is you live. It seems to be working just as well over here.
Make sure to read "Travels in Siberia" first. If the thought of most of your travel expenses going towards bribes bothers you, reconsider it.