3 ms·
I'm sorry, I really did try to read this because it sounded like it might interesting, but it's well over 2.5K words and by about halfway through I still had no
by Silhouette 15y ago
I'm sorry, I really did try to read this because it sounded like it might interesting, but it's well over 2.5K words and by about halfway through I still had no idea what it was really about. I skipped down to the final paragraph and that still didn't seem to tell me. May I respectfully suggest that future posts this long have a one-line or at least one-paragraph summary at the top?
- andywood 15y agoI think it's more than the lack of a summary. The whole essay could really benefit from a lot more editing and tightening up.
- michaelochurch 15y agoI agree. I'm outraged and disgusted by things I've seen over the past 12 months-- some have happened to me, most to other people-- and it's really affecting the quality of my writing.
- rhizome 15y agoA classic technique is to allow someone else to read the essay before publishing it.
- michaelochurch 15y agoI agree with you. Usually I put 1-2 months before writing a blog post/essay and posting it. I just see this matter as a bit more urgent, as I really want to see the American Spring (the 2012 campaign of people calling out unethical behaviors at companies, rather than protecting scummy ex-employers) happen. Words-of-prose can be like lines-of-code: beyond about 500, it takes a long process of review not to have some degree of mess.
- DavidAdams 15y agoI wouldn't be so hard on this essay. It's a little scattered, but there's some gold in there. Writing a concise, powerful essay is really, really hard, which is one of the reasons that people who are really good at it become famous (Jonathan Swift, Christopher Hitchens, etc).
- michaelochurch 15y agoThanks. Usually I have a 1-day/500-word minimum between initial writing of anything like this and posting it, because I don't want to embarrass myself with mediocre writing. I like to have days between drafts. This time, I want a message to get out, and fast. I might rewrite it in a week or so. Pretty much all of my 2000+ word blog posts deserve to be more than one post.
- bluekeybox 15y agoHalfway through I got a feeling that (a) the author doesn't know what he's writing about, (b) he's never read Eric Ries, otherwise he would at least state somewhere early a different interpretation of what "fail fast" could mean.
- michaelochurch 15y agoI did, actually. In systems, failing fast (as opposed to silent failure) is a good thing. Technical fast-failure is often correct. Better to catch the bug at compile time than at runtime. Better to throw an exception than do the wrong thing. Full agreement. No question there. That's because failure is objective and should be reported (and acted on) fast. I haven't read Eric Ries, so I have no opinion of him. I know that people are using "fail fast" to justify being ethically sloppy. I don't have any basis for assessing whether this has anything to do with Ries. Quite probably, it doesn't.
- bluekeybox 15y agoThanks for the reply. Brief disclaimer: (a) I should probably explain myself somewhere other than in an HN comment, (b) I'm still learning many things myself, so I welcome any criticism someone more knowledgeable than me may have. I feel that you're missing an important consequence of "failing fast". That consequence is something that struck me when I was reading Ries, but I don't think that one must read Ries to realize it. You write as if your peek from a systems perspective provides a ready answer to why "failing fast" could be a good thing, but it doesn't. Here is the best I can do to explain myself. Startups are hard. People put a lot of work into them. Oftentimes, the work turns out to be in vain. The "in vain" part is precisely what makes startups hard. If the work one put into a startup was not in vain, then almost by definition doing a startup would become no different than holding a 9-5 job except with longer hours. Now, "failing fast" means that the moment when you learn that the work you did was in vain comes sooner rather than later. Thus "failing fast" reduces the amount of work you do in vain, which is generally a good thing. So far this is no different than the systems thinking and your analogy with compilation/runtime engineering process you describe. Here is the crucial part though. By going somewhere and finding out it's a dead end, you learn something (gain information). Now fixing a bug early rather than late provides you with no new knowledge, so this is where the difference I'm talking about comes in. Think of knowledge that a certain directions are dead ends as if it was some surplus value. You accumulate that surplus value the more "dead ends" you try. If exploring dead ends had no associated cost (both timewise and monetary), it would be in your interest to explore as many "ends" as there are, in hope that perhaps one of them leads outside the maze, which would be a breakthrough. Note that it would never be in your interest to introduce as many bugs in a program as you possibly can. Coming back to startups, there is normally a cost associated with failure. If startups are run in a certain way, however, that cost is minimized, and then you find out that, at early stages at least, the benefits of exploring different directions may outweigh the risks.