If I was your TA, I would be worried about this. And, unfortunately, I have had senior level students who I've had to dissuade that cut+paste code is not a vali

If I was your TA, I would be worried about this. And, unfortunately, I have had senior level students who I've had to dissuade that cut+paste code is not a valid methodology past year 1. They way to think about things is like this: code is an expression of a problem. It's no coincidence we call them programming languages. They're not write-once, any code you write will be read an order of magnitude more than it will be written to. The way you write things makes me feel like you don't recognize Computer Science problems, and that you are beginning to realize that the code by itself doesn't constitute the problem. This is a common thread through undergraduate CS students, and it will take some people a long time before this clicks naturally (especially when it feels like writing code is a struggle alone, once you become more fluent code will no longer be the barrier). You aren't hirable as someone in mindset you are in, but you're moving closer to someone who can be. Continue on your mental journey of seeing problems first. Start working harder at following best practices. You'll get there.