There's an over-abundance of information. All that's left for HN is angry, emotional quibbling by those who lack the basic qualifications to evaluate the data and science, even if they were interested in actually doing so.
("Hacker News"? This particular little niche website is fast becoming Wall Street Blog West. People who came for the tech are leaving because of the increasing emphasis on how to make a few fast buck any old way.)
I agree. I found it depressing that your comment was down-voted to the negatives.
As a long-time San Francisco resident I found it irksome that Alex was so quick to bemoan the lack of culture to consume without showing any possible interest in creating any.
In my opinion, San Francisco is a beautiful place for creators.
Where did I claim otherwise? I only noted that his suggested approach -- which is clearly reflected by 37signals -- has led to me maintain a lower estimation of their decorum and the value of their positions.
The submission title is a direct quote from the article: The decline of the MBA will cut off the supply of bullshit at source
Second, this article has the facts wrong. MBAs from top schools aren't having trouble finding jobs, nor have those jobs started paying way less.
I don't have the statistics to support or refute this claim, but the article discussed a massive glut of graduating MBAs, not just the top of the class from "top schools". I'm not sure if you actually read the article, or simply penned a knee-jerk defensive response to the harsh wording.
Unit tests are narrow and focused, and aimed at verifying features. What you're talking about is something I'd call white box QA. Which is valuable, though it's essentially just an extension of design, and has the same limits.
It seems like most negative arguments regarding "unit tests" start by defining them as a small subset of what can be usefully tested, and then arguing against the value of testing such an incomplete subset.
I don't see the point of drawing such an arbitrary line. I leverage "unit" tests to automatically test units of code as completely as possible (not just 'verify features'), and I expect the same of tests that others write.
No amount of testing the former will lead you to realize the latter. Sure, you might happen to come to the realization while writing the test, but you might do so over breakfast too.
You're a bit more likely to do it during a time you've set aside to fully consider potential failure scenarios.
Testing can verify that your software works within the space of behavior that you already know about. It can't make up for your failure to understand the problem fully.
Thinking about correctly testing software is generally one of the best ways to improve your understanding of the problem.
I quite often find bugs during unit testing simply because I'm forced to think about how the software will break, rather than thinking about how it will (or should) work.
I think of it as being quite similar to waiting overnight to proof-read your own paper. You need to be in the context of the reader, not the writer, or your brain will skim over most mistakes.
They have a restriction on taking pictures of things you shouldn't (which includes most of the campus), but they don't have restrictions on cameras.
In addition to there being no written rule against it, I've openly and regularly hauled digital video and still cameras across campus without ever hearing any complaint from the omnipresent security guards.
How do you think people work on iPhoto/iMovie/FCP? Check out cameras from a locked facility?
Heterogeneous collections, discriminated unions, and GADTs can be implemented easily in either thrift or protobuf by leveraging inclusion of custom type-tagged messages/data.
However, while the encodings are absolutely sufficient to represent these data structures -- if you so choose -- my experience dictates that keeping serialized messages typed and as simple as possible is advantageous from the perspective of long-term maintenance and interoperability.
I hope not. Between Protobuf and Thrift, I don't see the point of adopting a less efficient, even more niche NIH serialization format and RPC protocol.
> As an analogy, you can take the routers that were stupidly configured to use stratum 1 NTP servers. These misbehaving devices placed too much strain on the NTP "network" because they used it inappropriately. But it was only the NTP servers that a lot of these routers were configured for that were having problems. Yet no one would claim that it's the NTP network's fault for the issues.
A poor analogy:
- AT&T sells the iPhone.
- AT&T sells the service.
ergo,
- AT&T is responsible for providing quality service to the iPhone.
All of this is going to lead to massive disillusionment with an open online lifestyle. Privacy is going to make a major comeback in the decade to come.
Or, alternatively, it's going to lead to an entire generation's total acceptance of human foibles as it becomes clear just how universally human our failings truly are.
To put it another way: the only reason to maintain your own backups of your site data -- aside from healthy paranoia -- is because you expect your service provider to fail at doing their job. And if that's the case, shouldn't you be finding a service provider that does it better?
If you don't expect your service provider to fail, you don't know anything about service providers.
Everybody fails.
Our colocation facility has redundant generator systems. They're tested regularly, and have handled failures previously. Yet, when the power went out, three of the backup generators failed, and our site (as well as Craigslist, Yelp, and others) was out for 45 minutes.
Reason 1: I pay for my bank account one way or another. It's bank's responsibility to keep the system running and secure, not mine. Sometimes we just can't do everything ourselves and have to rely on others.
You are responsible for reading your statement and ensuring that all activity is valid, much in the same way that you are responsible for ensuring the viability of your recovery strategy.
Reason 2: Many of us host something somewhere. How many do backups?
Anyone who wants to keep their data badly enough to pay (time, money) to do so. Coding Horror is a popular technology blog, and there's a significant cost in traffic and credibility when it fails.
Jeff Atwood lacked cognizance of the risks and made an incredibly poor technical and business decision in failing to validate correctness of his backups and implement a suitable recovery strategy.
Colin's statement was in the context of the question of BSD vs. GPL licensing.
RedHat's model it's clearly more effective than simple charity, but I don't see a difference between RedHat and any other OSS-reliant contributing vendor. As an example, Juniper funds FreeBSD development based on sales/support of their high-end networking products, and contributed the MIPS port included in FreeBSD 8:
The main difference is that these companies make their money by incorporating FreeBSD into their products, are not required to provide all the source to their products, and thus can contribute back improvements as they see fit.