4 ms·

MatLab is a disaster for this. Great software, but a horrible, horrible coding environment. I came from a CS background and did a EE masters. Working in Matlab

MatLab is a disaster for this. Great software, but a horrible, horrible coding environment. I came from a CS background and did a EE masters. Working in Matlab made me want to cry because of the problems you're describing; I think they're endemic to Matlab rather than anything you're doing wrong. Source control will help, just look at some of the git tutorials. Go through them enough to where you can create a "release" branch that you can roll back to if things go wrong. You probably won't need or use the rest of the features right away if ever. 15k lines also really isn't that much. It sounds like you're managing it OK (separate files instead of one massive one, yay!) other than not having source control.

hodder 9y ago
Interesting to know others have had similar experiences in Matlab. I'm hoping to find the time to recode the whole thing in python in the new year as well as implement source control. Thanks for sharing your experience.
- auxym 9y ago
  Before you launch into a "recode the whole thing" project, read this: https://www.joelonsoftware.com/2000/04/06/things-you-should-never-do-part-i/ https://www.joelonsoftware.com/2000/04/06/things-you-should-... Having your code base in python would be great, but do consider doing it piece by piece. Try to see if there's a part that would benefit greatly from the better organization features of python, and start there.
auxym 9y ago
> separate files instead of one massive one, yay! Matlab doesn't give you a choice here... every single function has to go in its own file. I'm also not a huge fan of matlab.