Can anyone point me to something legible on the subject? We'd like to start moving in the direction of provably correct systems and software, but I haven't been able to find much out there on the subject. Agile certainly isn't it, and every time I mention it, I get accused of "trying to go back to the failed software model, waterfall".

NASA does it, the aircraft industry does it - why can't we write systems that are robust? There was a similar article about "1,000 programmers furiously writing commands in 1/2 day to send to the Curiosity Rover", but finding details about how this process is done and managed is about as hard as finding out the truth about a political candidate. Where can one find this sort of stuff?

Because KDE, like Gnome, is slow and a RAM hog. XFCE screams...

The United Way is terrible. They also strong-arm companies into strong-arming their employees into "100% participation". No, thank you.

Wasn't there someone who did this as a psychology experiment a while back? Took out ads in the Enquirer and WWW saying "Send $1 to..." and an address. I forgot how much money the guy got, but it wasn't trivial, as I recall...

And you are absolutely correct - given that you are INFORMED as to both sides of the issue. People are easily swayed by emotional appeals presented on TV, which doesn't present the other side of the story nearly as often. People too easily forget the fiasco after 9/11, when the money given by people that was SPECIFICALLY earmarked to be used for 9/11 victims and survivors was instead used to buy a bunch of shiny new comms gear for ARC.

And that assumption would be wrong.

Until you do a little research. Look into the side of the BOD of ARC and what the executives get paid. It's all public information. I think you'll be surprised.

You obviously didn't actually READ what I posted, did you? ARE was charging enlisted men while giving officers stuff for free. Thats a DIFFERENT issue than you raise, which was American vs. Aussie troops.

A quote from the comments section on Charity Navigator:

3.9% sounds low until you figure it out in dollars.

It should be obvious to someone who posts here. Think about it.

During WWII, ARC would give away free coffee and doughnuts to officers, and that was well-publicized. What wasn't publicized was the fact that ARC would charge enlisted men a dime for the same thing. When my father learned of this (he was an officer), he demanded that his men be given the same deal. When ARC refused, he gave them their doughnuts and coffee back, and spread the story among the other officers.

This is unlawful conduct under Section 45 of the Competition and Consumer Act of 2010, as well as RICO statutes.

Confirm. My uncle retired from the ARC with a *very* good pension. I'd never give a dime to ARC.

I've got 30 years of processional experience, so does that make me more of an expert? Snarky comments aside:

The name "compiler" is primarily used for programs that translate source code from a high-level programming language to a lower level language (e.g., assembly language or machine code).

This is from Wikipedia, and is the most commonly-accepted definition in the industry, academia notwithstanding. I hardly think that JavaScript qualifies.

I'm still not sure why you chose to create monolithic applications, when the clear industry trend is towards more flexibility, particularly by using web services.

That was funny! Bravo!