Oh I have been in a similar position myself. Was a single dev in a startup and I needed to cut corners. I implemented everything. From embedded controllers to u

Oh I have been in a similar position myself. Was a single dev in a startup and I needed to cut corners. I implemented everything. From embedded controllers to user interface and I even used code that some students wrote as a proof of concept to save time. Codebase was a mess. It worked in the end, but barely and maintenance was horrible. I demanded help when the product was on the market and the new dev began to refactor parts of the software. Was awesome to have help and the new dev teased me when he discovered my greatest sins and most idiotic decisions that I committed. Wasn't meant seriously from his side, but at some point it nagged on me nonetheless because he was a bit of a smartass at times. Helped me to reflect what I implemented with the resources and time that I had. You will rarely be happy with the code and design decisions you made yesterday anyway. Learn from the mistake and move on. A dev that never wrote bad code probably didn't write much to begin with. People that constantly question design decisions often might just want to prove themselves to you or honestly want to know why you did it. I often answer something like "I was full of optimism about it at that time".