Timeline for What is the most efficient way to continue developing a piece of software in the long-term?
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 5, 2022 at 12:59 | history | edited | Pablo H | CC BY-SA 4.0 | clarified the idea |
| Dec 5, 2022 at 12:55 | comment | added | Pablo H | @Michael Yeah :) hence the "". But from the point of view of documentation, all that general stuff is more or less easy to grasp reading the code. Not saying those are trivial decisions to make, though. Of course, if there are very specific choices for naming, that should be written down, especially the rationale for that. | |
| Dec 4, 2022 at 16:38 | comment | added | Michael | lol @ naming conventions being trivial... naming things is said to be one of the two hardest things in computer science. | |
| Dec 2, 2022 at 23:28 | history | answered | Pablo H | CC BY-SA 4.0 |