Borislav Grigorov

The moment I deployed the app on prod, @terribledustin DMd me. "Hey man! Just wanted to let you know a crazy Haptic bug! I signed up, and it logged me into YOUR profile." Oopsy 2/9

It took me 20 minutes to find out that every new user got initially logged in as the first user in the DB. Because why bother adding WHERE clauses in the query that fetches the saved user. Luckily nothing critical happened and that defect got fixed. Pheww. 3/9

Few hours later I decided to update a post I have posted on my product page on Haptic. Rewrote the text. Uploaded an image. Than removed the image cuz didn't like it. And booom . All of the images disappeared from the database. On prod. Good job! 4/9

How come? As I told you, I'm not a big fan of WHERE clauses in SQL. So every time a user deleted an image, all of the images got removed from the database, because the query didn't have the id of the image to be deleted. Awesome! 5/9

I quickly fixed the problematic portion of the query and applied some "magic" to restore the images. Nobody noticed, except me 6/9

There were many more minor bugs, but nothing critical, mostly visual inconsistencies and one non-working button. Fixed them all and now the app seems quite stable after several days of me (+ 50-ish other people) using it on production. (thanks, guys) 7/9

Why I'm sharing this? I spent 4 months developing Haptic, and it's still far from perfect. Things are gonna break. It's gonna be embarrassing. But you can always fix your parachute in the air. You have no choice. So better jump and be creative! 8/9