undefined | Better HN

0 pointsblub3y ago0 comments

Performance is something that needs to be considered throughout the development cycle. If optimization happens at the end then it’s either a rewrite or a minor concern anyway because the building blocks like frameworks and libraries were already optimized. Or the software is just slow but still sells for other reasons.

0 comments

charlie03y ago

Totally depends in the business. Most businesses just don't need ultra low ms response times.

Rewriting an app because is too slow is a rather extreme approach. Most of the times it's just a small part of the application that needs optimization and not the entire app.

I'd argue that if the app experiences huge growth, then that's a good problem to have and a rewrite is in order.

blubOP3y ago

This is not about ultra-low responses or anything. Performance is just as much part of an application’s architecture as security or usability are. You can’t add those things at the end, they need to be done iteratively.

So when you say you optimize at the end as needed, you get away with that because somebody already did that job for you.

A) The frameworks and libs are heavily optimized, so that developers deploying them will get the best possible performance just by idiomatic usage and connecting those libraries together.

B) The software itself is not technically challenging.

When A and B don’t hold, ignoring performance will get the project in big trouble.

j / k navigate · click thread line to collapse