Ask HN: Premature optimization – when to use?

Re:Ask HN: Premature optimization – when to use? by dudul on Tuesday August 11, 2015 @11:11AM (#10041618)

In your case this is not premature optimization. You have written functioning code, and use it to tackle your problem, you just saw (and proved) that it wasn't fast enough, now you can optimize.

Premature optimization is when you try to write "clever" and "fast" code without first exercising it in real world scenario to actually see that it is not fast enough.

[ Parent | on HN ]

Re:Ask HN: Premature optimization – when to use? by nekopa on Tuesday August 11, 2015 @12:22PM (#10042260)

Cheers for this idea.

I was just wondering when I should stop the prototyping 'hacks', and sit down to try doing things smarter.

I have tackled the "MVP" of my problem, and I am still hacking away to get exactly what I need, but I am starting to think about the whole idea of 'technical debt'. I have enough code now that it is starting to not fit in my head.

I am wondering if this is the inflection point for starting to optimize - maybe abstract the code enough that I can keep building and keep it all in my head at the same time...

[ Parent | on HN ]