Absolutely fascinating article. I'm really glad that HN contains the occasional non-tech related story. It seems somewhat obvious how an engineering mindset transfers very well to other disciplines, and unbeknownst to me, beekeeping is one of them.
When I saw the title my first instinct was, okay, what's the metaphor between a beehive and a development team or a startup? You could find some parallels, but I agree this article is better.
While I really like the non-tech topics (I remember one about raising chickens as well), and I love reading all the HN comments (more detailed how-to experiences, startup metaphors, and beehive monitoring devices), I really did not like the tone of this article. I felt the form actually detracted from the content enough to come here and mention it.
I like learning about the details of a new field, and I like to hear about issues facing beginners, but this article seemed somewhat pretentious and naïve. I'm all for admitting and learning from mistakes, but not making them into some Shakepearian drama (loyalty, death, duels). The whole tie-in with literature seemed formulaic, not to mention strained, as if it were an assignment for a writing class. I felt this story would've been better served with a straight-up blog-like narrative--just the facts. Not every story belongs in the New Yorker.
It's stories like this that get the brain thinking in different directions than we do in a typical tech day. I absolutely love stories about ants and bees in general, so very refreshing to see here.