2 ms·
i always take the approach of get it functionally complete first then optimize for performance. It's easier to track optimization bugs (which can be nasty) and
by chasd00 8y ago
i always take the approach of get it functionally complete first then optimize for performance. It's easier to track optimization bugs (which can be nasty) and you always have something to revert to that at least works.
I agree that 99% of all projects never push beyond what relational databases are capable of. I've seen developers who were tasked with writing basically a todo list say that they're going with a nosql database because RDBMs don't scale.