Timeline for How to profile before optimising for readability
Current License: CC BY-SA 4.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 25, 2018 at 23:43 | comment | added | trichoplax is on Codidact now | I was considering how frequently code is edited and how much time is spent not as an indicator of poor readability, but in case those measures might be an indication that this part of the code might benefit from improved readability (even if it is good already). In a codebase that has roughly uniform readability, so anywhere could be made more readable, I'd want to prioritise improving those parts that people spend more time reading (whether due to frequent changes or to high complexity). | |
| Dec 25, 2018 at 23:31 | comment | added | trichoplax is on Codidact now | That's a really interesting distinction between implementation readability and abstraction readability. | |
| Dec 25, 2018 at 23:13 | history | answered | Ralf Kleberhoff | CC BY-SA 4.0 |