Yes yes yes. Think of all the poor coworkers who slaved away FOR those guys and will never reap the same benefits.

When the work is something like sales or marketing, long hours may be effective, since you can reach more clients or brainstorm ideas. The work isn't necessarily mentally exhausting. I can see how a VC would want long hours because getting to market first is a great way to edge out competition. But for engineering work, where correctness or deep comprehension of a problem is key, long hours will slow you down. I've seen it happen. A team will pull an all nighter, desperately rushing to solve a difficult problem or a mysterious bug only to still be stuck with it in the morning. Programming is in the realm of the mind and a good solution is rarely large quantities of code. If you need to write verbose and lengthy functions, you might be doing it wrong. Sure, you can type faster or copy and paste, but you will miss something that will take you hours to find. I find that I can solve difficult problems by relaxing and keeping the idea in my mind. Take a walk, a nap or daydream. The answer will pop into your head. It's number 37 in the 97 things. http://programmer.97things.ore...
However, the exceptions given are valid. If you fully understand the problem and know exactly what you want (and it's your personal project) stay in the groove while it lasts.

Exactly. A couple of years ago payload growth was due to asset storage. As more and more resolutions were released, games would store multiple copies of each image (sprite or texture) so they would match the resolution of each device they supported. This avoids resampling artifacts at the cost of payload size. Many options were invented to reduce payload bloat such as:
- Apple Introduced app thinning; where the bundle contains all assets but the device only downloads its resolution
- Download resources after installation - popular with freemium games
- SVG, Core Graphics, OpenGL, and Metal rendering to textures
- Using unicode glyphs for icons
Using some combination of these techniques allow me to reduce the size of my app package over the years while adding features. If you take a look at the facebook ipa and open er' up, you will see they got the asset size real small, but their frameworks weigh in at 295 MB. The only way around that is to stop using react or bring it into iOS as a shared library. But that would add even more bloat to an already bloated operating system.

Then you're children should be quarantined until such time as you agree to vaccination, and if any outbreak is ties to your children, an electric chair is awaiting you.

...The accident was a result of engineers saying no, but management overriding the decision. With this introduction, Bob makes it quite clear that when we choose not to stand up for that which we believe, it can have dire consequences.

There are some things that bother me here. (And they should bug you too)

1. The engineers did indeed stand up by saying no, but authority didn't give a fuck. In the end the engineers did not have control of the project.
2. The engineers didn't merely believe, they knew. I'm sure there were test results and rigorous math involved. Yes, I understand the terms are too often used interchangeably but it's important to know the distinction. When some yahoo stands up for his belief in, I don't know, let's say, god, there is big difference. Belief does not require proof.

When you stand up for something you can't prove, that can have dire consequences as well.

Granted, this writer is a former preacher, and it shows.

Australia needs Rowdy Roddy Piper!

http://www.youtube.com/watch?v=TwJJ3yBsvAw

why did their civilization suddenly die out?

Are you actually serious with that question???

I believe the OP was making the common mistake of personifying the system instead of the people. That is common these days. However, the classic maya vanished before that, around 800 C.E. While the people didn't actually 'vanish', their way of life did. While it is possible that the maya became victims of their own overgrowth like the romans, subject to the law of diminishing returns, it seems more plausible they just abandoned it when it no longer served them. Perhaps the city was more a project or experiment than an exercise in domination and superiority like it was with the romans. The experiment served its purpose and then the people dispersed back into the jungle. It's unfortunate that most of what they learned and recorded during this time was destroyed by those invading peoples you mentioned.

I'm not going to bother to look it up, but I bet it is more than 40 times, a LOT more.

Let's see, eh.
Ballmer's 2009 Total Compensation:
$1,276,627 [src: forbes.com]

Microsoft factory worker in China:
65 cents x 15 hours x 24 days (people work 6 days a week there) = US$234/mo [from below post]
$2,808/yr

Ballmer makes about 454.6X a factor worker. Not really a thousand times, but getting there. Not to mention these workers have to buy their own bedding so they essentially have no benefits. None.

It certainly qualifies as "hacking". See, it's the quotes that modify the meaning. For example, If you were to buy something with inkjet prints or photographs of dollar bills you could say: I tried to buy this candy bar with "money", and they turned me away. Or "sex" in place of masturbating in front of your monitor. Or Nickelback as "music". I could go on.

181 upgraded, 0 newly installed, 0 to remove and 6 not upgraded.
Need to get 275MB of archives.
After this operation, 8,425kB disk space will be freed.

Such a beautiful thing. Show me a Windows system that can do that.