If your code 1) runs the first time with no non-trivial errors or obvious bugs, 2) does at least what you intended it to do, reliably, efficiently, and isn't ea

If your code 1) runs the first time with no non-trivial errors or obvious bugs, 2) does at least what you intended it to do, reliably, efficiently, and isn't easily de-railed... then you're getting close. If 3) you find you can easily and quickly modify it to add features... months later... that's closer still. Of course if you have to answer to someone about why you did it this way or that way, or who can't comprehend your code, then (in that environment) you may have farther to go. Longer, bigger, harder projects may test your skills. Be your own best critic, always strive to do more with less.