My horror story: I made a calorie counting app that allows the user to save nutrition facts of foods. I was an amateur at the time I didn't know how to manipulate arrays; I built a custom array to store user data, each x value would be a food name, each food had 11 attributes at the time. I made 250(x) custom slots with 11(y) attributes, a single event for each attribute was used to save all the data properly (in my amateur head :/), that is 2750 events, don't worry it gets better. I had 3 menus, one for a log, another for recipes, and finally one for individual food. That's 8250 events.
A few months later I learn some python and learned what to search for in construct in order to program more efficiently.
I replaced that 8250 conditions with a single event to trigger a save, a loop sub event with an incremental function, another sub event to organize and save the array. I refactored the programming (which originally took me a weekend) in less then 10 minutes. Now the menus are Infinitely sized.
The end result left me feeling like I am probably wasting tons of time and don't even realize it. But then again I got in so many reps and learned a very valuable lesson; stuff will indeed go wrong and I will be the one to blame half the time, and that is why creating is hard work, not quitting + experience * talent = success. My advice is to abstain from the project for a few days until it bothers you so bad that you want to go back. If a week goes by then it time to go to work.
Point is we all do dumb things in our own dumb little ways. Its the ones that stop putting in effort that you never hear about, although you will read them complain a lot about the app store : ).