Timeline for Fighting the half-life of code
Current License: CC BY-SA 4.0
15 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Aug 9, 2022 at 21:34 | comment | added | candied_orange | @DocBrown yes and MIT wanted everyone to know LISP. Remember, the requirement is that grads can read your code base without needing another class. They may know more than that. But if LISP really is all they know then examine how much you hate LISP. Either that or start taking the dean out to dinner. | |
Aug 9, 2022 at 21:00 | comment | added | Doc Brown | @candied_orange: in my experience, CS programs can be sometimes edgy. My first university programming course, for example, was based on SICP with Scheme (>30 years ago), Not what I would really recommend to the OP today, though I guess chances are not too bad my old programs would still run today, if I had kept them. | |
Aug 9, 2022 at 20:34 | comment | added | candied_orange | @DocBrown My reasoning is if it's taught in your local CS program it's likely to be both mature and have staying power. I've rarely seen the hype make it into the core curriculum. Still not what you had in mind? | |
Aug 9, 2022 at 20:27 | comment | added | Doc Brown | @candied_orange: not really what I meant, but alas, I think it is good enough as it is. | |
Aug 9, 2022 at 20:20 | comment | added | candied_orange | @DocBrown better? | |
Aug 9, 2022 at 20:19 | history | edited | candied_orange | CC BY-SA 4.0 |
added 263 characters in body
|
Aug 9, 2022 at 20:09 | comment | added | Doc Brown | I think your first advice could be improved: popularity is good, but popularity plus a certain degree of maturity is better. Often, some new things earn a short-term popularity because they are hyped, but often those things vanish as quick as they have appeared. | |
Aug 9, 2022 at 14:22 | history | edited | candied_orange | CC BY-SA 4.0 |
edited body
|
Aug 8, 2022 at 15:43 | comment | added | candied_orange | @user7088941 better? | |
Aug 8, 2022 at 15:42 | history | edited | candied_orange | CC BY-SA 4.0 |
added 414 characters in body
|
Aug 8, 2022 at 15:29 | comment | added | user7088941 | This is a good answer, but could you illustrate your point with some examples? It is a bit too abstract at time for me. For example you say " most infrastructure choices don't have to be spread throughout the code base"; what would be an example of an infrastructure choice? Also if I code a long, complicated algorithm, that is related to my research and the thing outputs a picture at the end, what would be the abstractions and decompositions that I could use? I guess there is not much that I could do here ... | |
Aug 7, 2022 at 17:41 | history | edited | candied_orange | CC BY-SA 4.0 |
added 10 characters in body
|
Aug 7, 2022 at 17:33 | history | edited | candied_orange | CC BY-SA 4.0 |
added 1 character in body
|
Aug 7, 2022 at 17:27 | history | edited | candied_orange | CC BY-SA 4.0 |
added 1059 characters in body
|
Aug 7, 2022 at 17:20 | history | answered | candied_orange | CC BY-SA 4.0 |