She said that process “used a large amount of available memory and interrupted the computer’s other flight-processing functions”.
You should always always always check your input params size!
“It’s very over-budget and behind schedule, so it doesn’t surprise me that it’s got some bugs – it’s the way it presented itself” that’s alarming, Moss said.
No words…. The same all other the world.
Noting interesting. Different people has different mindsets and desired workflow.
When processing large amounts of data, it’s important to choose a good algorithm, but “good” does not always mean “fancy”. It’s important to think about how your code will perform in practice. Constant factors drop out of “Big O” analysis, but they can be large enough to matter in the real world. Simpler algorithms are easier to optimize, and less vulnerable to bad edge-case behavior.