I think this is reasonable, but at the same time, please get those million lines out of your system on somebody else's project. If that can't be done, if you c

I think this is reasonable, but at the same time, please get those million lines out of your system on somebody else's project. If that can't be done, if you can't spend your free time honing your abilities, then accept helpful feedback from other more experienced developers. Don't just accept feedback--assume your code is garbage, and ask how you can make it better. If the answer eventually becomes "it's good enough for business purposes", then find out why that is, and learn from that. Communication is hard, and explaining why a codebase is just wrong can be as difficult as explaining to somebody why you find them abrasive. At the same time, it's the job of senior engineers to make the effort and try. Sadly, in a startup environment, it's usually smarter business-wise in the short-term just to sack the inexperienced developers or railroad them into simpler work that they can't screw up, and kick the can down the line.