30

Anyone else approach coding with the mindset of - "make it work, then make it right".

It really helped me up my productivity

Comments
  • 3
    I do that
  • 3
    It's basically what agile says
  • 23
    I do "make it work but don't let your boss know yet, otherwise he would ask for it to be deployed and you wouldn't have time to make it right".
  • 6
    Depends. If its something I've never implemented before then yes. First making it work is better than making it right. But if I'm adding something I have a clear idea of how it works then I just start adding it correct from the start.
    Using clean code guidelines when making it work makes it easy to improve when refactoring though.
  • 2
    Why not both at the same time?
  • 1
    That's the only logical approach for me personally. Who cares whether or not someone else's code runs 10 times faster than mine if mine is the only one with the correct functionality? You can and should always iterate on it and optimize _afterwards_. But I do catch myself reusing code whenever possible, not sure if that's always a good practice...
  • 1
    Hoo, are you approaching me?
    I can't make you work without getting closer!
    Oh? Then come as close as you like?
  • 1
    Absolutely 👍
  • 2
    @theskywalker
    Yes.
    Hitler chose this approach.
    Did not work out well.

    Just kidding.
    Though your pseudo and this kick-start rant indicate, you're just about feeding business greed.
    Congrats.
  • 2
    @unclesam

    He rolled over the developing(/ment) community of Europe.

    Just like overreacting managers do when they realize they fucked up schedules.
Add Comment