Come to think of it, clicking past warnings and pop-ups is actually quite pervasive.
I replied to another comment later in this discussion sticking up for my former employer against this hit piece.
Further, I said that (I'd imagine quite a few current and former Amazonians feel compelled to say something.) in response to the implication that current employees are being compelled by the company to speak up, and to the implication that them speaking immediately after the article was written is equivalent to "working on the weekend."
Yes, rahvin112, I read every word of the article.
I don't doubt that there are places within Amazon where management sucks. I socialized quite a bit while I was there, and, like any large company, there are places with poor management practices (demanding long work hours and burning people out, etc).
But yes, if what the article claims is true did or does actually happen there, it would greatly surprise me. I do know that some of the claims are outright lies, though (paying for our desks? unreimbursed travel pay??), so I'm skeptical of the rest.
As a former employee, this article really changed my view of the NY Times. I guess I expected more from such a well-known, established news source. But, this lengthy "expose" was clearly written by two authors with an agenda, and to what end? Readership?
I loved my time at Amazon.com. Yes, it was challenging. My time there forced me to grow as an engineer when I knew I was at risk of stagnation. But, I worked very reasonable hours (~7am-4pm, by choice to avoid traffic) and only very rarely (once very few months on average, typically leading up to Black Friday before all our deployments were locked down) worked nights of weekends. I traveled twice for Amazon - and had no trouble expensing the flight, hotel, meals, and transportation to/from the airport. I never saw anyone cry at their desk. Everyone who worked there was very civil.
I left for opportunity more than anything - an opportunity to both advance my career and be closer to my family on the east coast.
But yeah, I really have to wonder why the NY Times is busting Amazon's balls. I feel like a dope for not being more suspicious of them before now.
Not surprising given we are all created in his image.
In Soviet Russia, God created US in HIS image!
You need IDE for large project. Regardless of the language used.
The OP is still correct about Java. "Non-trivial" is not the same as "large project." Small applications can be written in Python, Ruby, Perl, and C without an IDE, but writing a small application without an IDE is really difficult task in Java (and C# or basically any other
Further, you do *not* need an IDE for large projects regardless of language. I've seen a number of large projects (tens of thousands of lines of code) written in C and Ruby where more than half of the developers did NOT use an IDE. In fact, for the C projects on which I've worked recently (last 10 years, including those with tens of thousands of lines of source), the primary code editing tools used by the developers were exclusively text editors like nano and vim - there is no IDE during development.
A rock store eventually closed down; they were taking too much for granite.