Thanks for the article. One thing I'd like to add is that beyond measuring/profiling starting performance, it's useful to set a starting hypothesis for what improvement changes are expected to bring, both a theoretical upper bound (assume the change will make some portion run in 0s), and an estimated realistic timesave (going from O^2 to O, perhaps) in terms of seconds and percent relative to starting performance under a representative load.
Doing this exercise before making changes will train this "deep understanding" of systems and oftentimes stop you from doing low-impact work.
I really appreciate you reading my article and I'm grateful for your valuable comment. I wanted to let you know that I did some research on what you suggested and it makes a lot of sense, I understood that before making changes to something, it's helpful to think about what we expect those changes to achieve. This includes two things: first, the best-case scenario where the changes make things super fast, and second, a more realistic estimate of how much time they might save compared to how things are right now. Your suggestion could be the basis for a whole new article!
Thank you again and I'd love to hear more of your thoughts in the future.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thanks for the article. One thing I'd like to add is that beyond measuring/profiling starting performance, it's useful to set a starting hypothesis for what improvement changes are expected to bring, both a theoretical upper bound (assume the change will make some portion run in 0s), and an estimated realistic timesave (going from O^2 to O, perhaps) in terms of seconds and percent relative to starting performance under a representative load.
Doing this exercise before making changes will train this "deep understanding" of systems and oftentimes stop you from doing low-impact work.
I really appreciate you reading my article and I'm grateful for your valuable comment. I wanted to let you know that I did some research on what you suggested and it makes a lot of sense, I understood that before making changes to something, it's helpful to think about what we expect those changes to achieve. This includes two things: first, the best-case scenario where the changes make things super fast, and second, a more realistic estimate of how much time they might save compared to how things are right now. Your suggestion could be the basis for a whole new article!
Thank you again and I'd love to hear more of your thoughts in the future.