Good code is succinct. OOP is not a pre-requisite for "good code", it depends on what you are using it for. It takes longer to write less code than to write more code. Not taking the time to write good code will eventually result in a very complex program that is hard to modify, hard to fix bugs with.
You write good code to save time down the line. Sure, bad code is fine for one-use scripts, but if you are building a product that you know will be around for a long time (i.e not a prototype, you've done that already), it pays to write good code; Good code will make it easier to fix bugs, easier to add features, and lead to better software.
You write good code to save time down the line. Sure, bad code is fine for one-use scripts, but if you are building a product that you know will be around for a long time (i.e not a prototype, you've done that already), it pays to write good code; Good code will make it easier to fix bugs, easier to add features, and lead to better software.