32
payb4k
6y

You refactor after there's code. You can't have clean code if there isn't code to be cleaned to begin with. Code first. Think of perfection later.

Comments
  • 1
    I'm currently working on a project where the original developers seemed to have had that philosophy. Not even refactoring can fix that abomination.
  • 3
    Next thing you know you have so much spaghetti code it could be a pasta version of cthulhu
  • 1
    Divide and conquer. Cody tiny parts refactor as you go. Periodic full clean up passes. Much cleaner.
  • 3
    True and not.

    If you write crap code by default, you're gonna have a bad time. If you prematurely optimize, you're gonna have a bad time.

    The key is to strike a balance between the two, given your level of skill.
Add Comment