51 karma · joined July 18, 2019
- Start with the answer first.
- Group and summarize your supporting arguments.
- Logically order your supporting ideas.
I think the first point is the most important one. To get the attention of busy executives it is important to give them the answer first and then elaborate. The answer would get their attention and that's a battle half won already.
git commit --amend --reset-author changes both author time and commit time.
git rebase changes commit time.
All three commands can be used just before a merge and push to clean things up. So there is no guarantee that the author time or commit time we see in the final commit history accurately represents the actual time at which the work was done.
Also is it Racket specifically that makes it a good contender or is it the fact that it is a Lisp that makes it a good contender? Would any other Lisp like Scheme or Clojure or Common Lisp be equally good?
This does not sound right. On the contrary, I have always seen emergency exits in Japanese buildings.
Is there a similar programming language that makes mathematicians feel at home? Something that makes them feel that they would rather write their implementation in that language itself instead of writing it with math notation on paper first?