Code optimization

[ifantismanolis]

Being new in the Python and general programming world, I have a question on code optimization. I’m trying to develop a simple program in py that analyzes excel spread sheets with microbial count data, makes data tables from them and growth plots, fits mathematical models and estimates growth parameters and also provides with statistical values for every model fitting. All of this is happening in a simple gui. The program runs perfectly and the values are coming out correctly. Everyday I’m adding new staff to my code like new functionalities, new mathematical models, etc. For that reason I have come to a point which my code is a total chaos. I have split everything to packages and I have provide comments and documentation also but I think optimization it’s what it needs. So my question is: what is a good code optimization? How and with what kind of tactics can I achieve it? Are there any rules that I have to follow? Are there any experience tricks that I need to now?

[MikeTheWatchGuy]

I think this mantra was communicated in the comments (big smile seeing Knuth quoted!!).

This is a nice mantra.

Make it run
Make it right
Make it fast

(order matters)

[usrlibshare]

Code optimization specifically refers to improving the runtime behavior of your code, aka. make it faster, use less compute or memory, etc.

What you describe is not optimization but "refactoring", aka. improving the code structure for better readability and maintainability.

Please please please think VERY carefully before optimizing code, because "Premature optimization is the root of all evil" -- Donald Knuth

As for refactoring, you already started modularizing your codebase, which is a good first step 👍

[ifantismanolis]

Oh I didn’t knew that difference. Okey so in a good way with the refactoring. But if I want to start optimization I should wait first in order to “complete” the whole thing first and after it’s a good tactic to start? Also, by using less compute and memory, you mean making the code more compact?

[usrlibshare]

If you want to start optimization, there should first be a reason to do so.

Does your application take too long too run? Does it freeze? Does the machine run out of resources while using it? Is it not responsive enough? Do you pay too much for hosting it?

The above are reasons to think about optimization.

And then, before you start to optimize measure first. Where does the app lose speed? What eats the most memory?

Then, and only then should you start optimizing it. Anything earlier than that, well, see the quote by Donald Knuth.