Hacker News new | past | comments | ask | show | jobs | submit login

My third iPhone project, and the first truly big whack of MVC code I'd ever written.

Everything was tested and working, but I didn't want to release yet. Had to optimize a meaty, graphical tableview that was choppy and dropping frames.

Got it glassy smooth, tested it lightly, then released.

Press was solid, sales were outstanding, everything was going well. (edit: I forgot: This was especially exciting news because I was about to leave a safe job for big adventure)

But the app was crashing and destroying any data the user had input before the crash.

I had to pull the app while I figured out what was wrong, destroying the product's amazing momentum and killing my sales rank. I didn't care. I felt terrible, taking people's money with a broken product.

Came down to one over-released button object, one line of code, along with a boneheaded assumption of when I should commit persistent data.

I donated the entirety of my early sales to charity and chalked up the experience to the importance of rigorous QA, no matter how trivial a change seems.




"I donated the entirety of my early sales to charity and chalked up the experience to the importance of rigorous QA, no matter how trivial a change seems."

WOW. Respect.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: