Timeline for Project Euler #909: L-Expressions I
Current License: CC BY-SA 4.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 28 at 20:53 | comment | added | gnasher729 | In my experience, you can take any code and make it maybe ten times faster, making it unreadable in the process. That may be a good compromise. However, no you cannot improve your code through deeper insights anymore. And for Euler problems a factor ten improvement is very often not enough. So you do this only as the very last step after you run completely out of ideas. | |
| Aug 26 at 19:22 | comment | added | Toby Speight | I know you are embarrassed that you can't offer more advice, but I genuinely believe that "this code is hard to understand" is extremely valuable feedback (even though it hurts when I receive it!). If polfosol takes that criticism and posts a new question with named functions, improved identifiers and (where all else fails) explanatory comments, then a more informed review is likely to be the result. | |
| Aug 26 at 17:54 | history | answered | Thibe | CC BY-SA 4.0 |