![]() The previous chapters deliberately focussed on concepts, packages and functions to increase efficiency. Even worse, there is a trade-off between code speed and code readability we’ve already made this trade-off once by using readable, (but slow) R compared with verbose C code!įor this reason this chapter is covered towards the latter half of the book. This means that time spent optimizing code early in the developmental stage could be wasted. When developing code, the causes of inefficiencies may shift so that what originally caused slowness at the beginning of your work may not be relevant at a later stage. ![]() Knuth’s point is that it is easy to undertake code optimisation inefficiently. The real problem is that programmers have spent far too much time worrying about efficiency in the wrong places and at the wrong times premature optimisation is the root of all evil (or at least most of it) in programming. On the subject of optimisation he gives this advice:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |