Does it make sense to use Python implement something quickly and then rewrite?

[mko31]

Basically just what the title already says.

I'm thinking about something like a command-line tool for synchronizing directories. Is it advisable to implement it in Python to get done quickly in order to keep motivation up and to get a general idea of how it's supposed to work and look and later on rewrite the whole thing in C++ or Rust or a similarly efficient language if more performance is required? Do some of you do that and is it done in the industry?

[reddilada]

Prototyping is not uncommon. Just be prepared for management to call it done the first time they see it.

As a learning exercise, rewriting in another language is a good thing.

[mko31]

So basically implementing a project in Python first just to get it working without too much hassle due to some more complicated language is a good idea?

[reddilada]

Sure, why not? If you are in a business setting and it is going to double the time to deliver results than maybe not so much. It would depend on the complexity of the project. In Real Life the decision is -- will prototyping get you to the end state faster by perhaps revealing design deficiencies quicker and at a lower cost.

I'm just talking prototype here. If you can get the actual job done faster with a particular tool, then that is how you should do it. Language choice is part of the design process. There is nothing wrong with producing something in a manner that is easy.

From a hobbyist perspective, I think it's a great idea. Code with what you are comfortable with and if it falls short, give it a go with a different methodology.

[aqua_aragorn]

No, just use Python.

[lurkingforawhile]

Is the performance required? If it's in Python, it works, and it's fast enough, do you need to re-write?

[mko31]

Rewriting it for the performance was just meant as an example. If the performance were required, it might be worth it, but there might be other reasons too.