tag:blogger.com,1999:blog-3050447570835882614.post6893680821467678649..comments2022-09-08T01:07:10.654-07:00Comments on alexrwallace.com : Coding for readabilityAnonymoushttp://www.blogger.com/profile/00166863868451280471noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-3050447570835882614.post-57395748324836295762013-09-16T10:48:38.620-07:002013-09-16T10:48:38.620-07:00I love me some Python ;-) I've also seen some ...I love me some Python ;-) I've also seen some awfully written Python that made me wish people actually followed some of the above advice!<br><br>I will concede that there are some cases where my 10 year statement does not hold true. As you mentioned latency and increased system capacity can definitely cause issues and tend to require tweaks to keep up. The purpose of the statement was more to make the point of don't over think what you are coding, especially in terms of efficiency. After all as you mentioned. FAT was an efficient solution at the time, but now could probably use a refresh because things have changed. That will be a much harder proposition if the code isn't clearly written.Alex Wallacehttps://www.blogger.com/profile/00166863868451280471noreply@blogger.comtag:blogger.com,1999:blog-3050447570835882614.post-59786618269519040362013-09-14T10:41:37.336-07:002013-09-14T10:41:37.336-07:00Readability is king, which is why we should all co...Readability is king, which is why we should all code in Python. ;-)<br><br>I think your overall point is bang on, but I will take some issue with the "code written 10 years ago runs blazingly fast today". If the workload is the same, that statement is generally true. However, workloads tend to grow to suit the capacity of systems, and over time not everything follows Moore's Law. Specifically, any that is latency sensitive tends to need tweaking, because the trade-offs between CPU/memory/disk *have* changed over time. A good example of this are file systems. FAT was actually pretty efficient for the problem it set out to address, but it's lousy bad for today's much larger disks and files.Christopher Smithhttps://www.blogger.com/profile/13820642342200638732noreply@blogger.com