As you surely know, coal plants exhaust is filtered to the extend that the exhaust is cleaner than the intake. At least that is so in germany
Accepting your premise...
It sounds like the Germans need to set up some big filter plants that do nothing but intake, filter, and exhaust the air, if their air is so shitty that running it through a coal fired power plant cleans it.
I have seen first hand a gypsy neighborhood raised by bulldozers.
Apparently, Hillary Clinton was wrong... it doesn't take a village to raise a child, it takes a group of bulldozers.
Any software requiring documentation is broken.
I blame Bob Wallace.
Bob Wallace was one of the originators of the concept of "shareware", and he got paid not for his software. This made people wonder how Quicksoft was able to stay in business.
When questioned about this at one convention, he made circling motions with his hands on either side of his head, and said "Software is
Or, to put it another way, Quicksoft made their money by having a relatively feature-full product which was nearly impossible to use without documentation. And people have been mistakenly trying to copy his success by utilizing the same technique, ever since.
Why did WordPerfect lose out to Microsoft Word? It wasn't because WordPerfect didn't already own the market; it did. It wasn't because Microsoft Word had more features; it didn't. Was Word a lot better, intrinsically, than WordPerfect? It actually wasn't.
Frankly, it was because of the F1 key. By the time WordPerfect got around to deciding they needed a "Help!" key, some of the function keys were already assigned, and so they assigned the next available one to be the "Help!" key. It helped sell a hell of a lot of keyboard templates. And it hid the help from anyone who'd experimentally go looking for it by hitting unlabeled keys in order until they found it (in fact, this would totally screw you up in WordPerfect).
Microsoft hit on a UX innovation: when something goes wrong, make the "Help!" key the first key someone is likely to hit, before all other keys.
And then they did it one better: The F1 was assigned to be the "Help!" key in *all* their products. Instead of just being a great UX thing, locating the key where they did on the basis of probability, they turned it into a Schelling Point: anyone who wanted "Help!" in any Microsoft product knew where to go to find it, if they had ever used some other Microsoft product, and needed "Help!" there.
So back to the original question: should you invest in documentation? Well, yes... if your product has already failed to the point where it's nearly impossible to use without documentation, or because, like Bob Wallace, you intentionally made it nearly impossible to use without documentation because that's one of the premises of your business model.
Maybe you want to write books on your project, once it's used by enough people to make that profitable, and that's how you plan to turn your hobby into a vacation fund. Or maybe you want to get to be a published author about a product so you get hired as a tech writer somewhere, or you get a lot of speaking engagements, and monetize your efforts that way. But if making your product hard to use was one of your initial conditions, then I think your software is broken.
It is more cute that you don't kniw the difference between waste and spend fuel.
Reprocessing spend fuel produces more waste than not reprocessing, hint: for fuck sake read about the topic instead of making cute comments that in hint seight only show you are a dump ass, and not a smart ass.
It's also cute when someone who can't spell attempts to "correct" a theoretical physicist on a physics topic, and their correction is wrong:
http://www.world-nuclear.org/i...
http://en.wikipedia.org/wiki/N...
So it'd be like working with Linus Torvalds?
Actually, no. Linus has given us Linux and git. Whereas Congress has given us debt slavery, corruption, economic stagnation and Forever War.
I suppose we'll have to take the bad with the good.
I've known "rock star" coders. If you don't want someone like Vint Cerf or W. Richard Stevens or Kirk McKusick or Eric Allman or Mike Karels or Dennis Ritchie or Sam Leffler on your team, then you are a freaking idiot.
And if you haven't heard it before, then you've probably never done a startup in Silicon Valley: Talent attracts talent.
Fission only at places where you can cool them, and preferable the road infrastructure is good to get fuel to them and waste away.
It's cute that you think waste has to be hauled away and stored, instead of reprocessed into more fuel.
Missing option: The planet of another star
When arguing solar vs. nuclear, what you are really arguing about is where to put the reactor, and whether it's going to be a fusion reactor now, or a fission reactor now, with a fusion reactor replacing it later.
I'm disappointed that codes for new construction haven't started mandating the installation of solar.
So are the companies selling solar. Meanwhile, Chevron is disappointed about codes for new construction not mandating the installation of furnaces requiring heating oil.
As customization reaches lower and lower levels, it becomes increasingly difficult to meaningfully compromise it. Probably the only way to meaningfully compromise an FPGA is to autodetect an internet connectin, and stream out to it everything you receive, possibly only on receiving a particular activation signal.
The "FP" in "FPGA" stands for "Field Programmable"; it's possible to compromise in the field, in a rather meaningful way.
That's easy!
Start with a computer that doesn't need tweaks/updates from time to time, and then add video conferencing software that allows you to not upgrade it in order to support new platforms because the basic protocol never changes, but is already ubiquitous on every platform someone might want to use, and get it all from a vendor who has no monetary interest in forced updates!
An elephant is a mouse with constantly changing government regulation.
Its ok, just a matter of time before Israel implements the final solution to the Palestinian problem.
The primary reason for traffic slowdowns on these highways was rear-end collisions blocking traffic.
You've apparently never driven on U.S. 101 in the SF Bay Area; the primary reasons for traffic slowdowns are:
(1) Auuuuuuuugh! There's a huge ball of light up in the sky! We fears it, my precious!
(2) Look! An accident! Is there blood? Hey, Bill, can you see any blood?!?!
(3) I must get in the fast lane because it is the "fast" lane, even though I'm coming up on my exit!
(4) I must get from the fast lane all the way over to the exit lane, but it's OK if this takes forever, I was in the fast lane for 50 feet, dammit!
(5) Yes, I know it's after 3 PM and before 7PM! What do you mean, the lane to the left of mine is "The Car Pool Lane"? I'm driving slow in the middle lane; if you want to pass, you should get into the car pool lane and pass, then get back into this lane; you probably won't get a ticket anyway...
(6) Let me race up in this lane that I need to be out of before too long, rather than getting over now, even though I see barricades ahead, because I know some dumbass will let me in, right? Right? Hey, dumbass, I'm talking to you!
(7) I want to get on one of the bridges, but I don't want to wait behind all the people who also want to get on one of these bridges, so I'm going to block the next lane over until someone lets me in just to punish everyone else... if I have to wait, then everybody else damn well has to wait, too.
That probably should have been a countdown; fast lane discipline while car pool hours are in effect is probably the number one cause of traffic slowdowns, followed by "I'm too stupid to get over ahead of time", with "Auuuugh! Ball of fire!" in third place...
With your bare hands?!?
