3 ms·
I hate it but you're wrong. (I agree with you, but I'm wrong too.) I used to work for a small company that made it big (you've heard of them.) We went from
by carapace 7y ago
I hate it but you're wrong. (I agree with you, but I'm wrong too.)
I used to work for a small company that made it big (you've heard of them.) We went from ~25k to ~250k users while I was there and the VCs were lining up to pound money up the founders' asses. Limosine rides and $500 steak dinners to woo them, the whole thing. I left, they eventually went public, and last I heard the Walton family owns it now or something.
Anyway...
The front-end guy "Chris" (not his real name) and the back-end guy were pals, and they would just push any old shit to production. The CEO had no clue, and I wasn't in a position to get them to stop. There was one other guy working remotely who didn't care or also had no clue.
So, "Chris" (not his real name) would shit out some PHP, bang on the new feature or whatever for a few seconds, and if it worked even slightly at all he would push it.
Shit broke all the time.
The poor dumb users would be on the support forums telling each other how the heroic Chris was working furiously to fix it, and I'm sitting there fuming because Chris is the ruthless asshole using them as unpaid QA.
That fucker is a millionaire now. Go figure.
- sonnyblarney 7y agoThis is a very good anecdote, and helps us understand that 'shit' is in the eye of the beholder. If it solves a real problem, and allows companies to do 'xyz' , maybe it doesn't matter if there are bugs and glitches here and there. If there is only 'one kind of car' and that's all anyone knew, nobody would mind that there were always leaky oil issues if the alternative was 'horses'.
- kyshoc 7y agoIndeed. The YC application has a question along the lines of "why is the thing you're building so compelling that customers will tolerate a buggy product?"
- carapace 7y agoIt's a terrible anecdote, it's only redeeming quality is that it's based on a true story. We could have fired Chris and replaced him the next day. We should have. We will never be able to know or quantify the loss accrued to Chris's irresponsible behavior. We got lucky. It costs nothing extra to write correct bug-free code if you know how, and bug-free code will always be preferable to buggy code.