lessons learnt from the WIL simulation project
I need test driven methodology, since I’m careless. MUnit seems good.
It’s extremely harmful to follow others without establish a framework of my own when dealing with legacy code, especially when the style of my thinking is in such a contrast with others.
I need simplicity. I need to separate the core logic/ algorithm from other messy code dealing with various input and output and formatting.
Although matlab has a profiler, it’s not desireable to spend too much time optimizing the speed in matlab. matlab code is meant for the clarity of the algorithm.
The first task should be identify and solve really important problems when writing simulation. That’s what simulation is all about.
Cat:
- Uncategorized | Time: 12:48 pm (UTC+8)
