No it really didn't help much. There are a number of reasons. A tip or a hack cannot solve what is essentially an emotion regulation problem. You probably don't procrastinate on all tasks. For example you can probably read reddit or play games all day. But you dread even starting some tasks. It might be due to multiple reason: past failures, critical feedbacks etc. You will need to introspect and solve that complicated emotion.
Of course, if you notice a broad pattern in every part of your life please consider professional help.
Countries like India are heavy users of diary products. Lactose intolerance is rare too. But always fare very poorly in the height rankings. So it cannot be concluded that it is diary products alone.
It is a great example "Worse is better"[1]. XML has a lot more functionality than JSON but very few people can fully understand all the X* family of specifications, whereas JSON is a _lot_ easier and handles majority of the use cases.
There are many, many real life situations where a developer needs to choose between using JSON, XML or YAML to store their configuration data, message formats etc. Simply stating that JSON is good only in one scenario and XML must be used in every other is over-simplification.
My biggest problem with these list making solutions are what I call the collateral tasks. For example, my list says "Buy a Christmas gift for Jen".
When I start shopping online, I realize that I don't know much about Jen, so I need to call a friend. Lots of discussion later, I finalize on something to buy then I need to think of a personal note to write.
At the checkout, my banking application tells me that my internet password needs to be changed. The whole process gets aborted!
Probably, I exaggerated a little but my point being that each task involves a million micro steps which may or may not be anticipated. No wonder there is a lot of procrastination!
I have seen sites using captchas which ask such visual questions thinking that only a human can answer them. This project really makes me doubt the effectiveness of such techniques.
Even if you don't use Emacs, I believe you _have_ to try magit. It will quickly become an essential part of your git workflow. You could zoom out to grasp the overall state of your project, dive into specific details and perform intricate surgery of your git history, all with single-key presses. It is pure genius.
It seems most of the content is under "Standard YouTube Licence"[1]. Since this is historical footage I would have preferred if it was under Creative Commons, so that it could be included in other videos. Anyways, this makes YouTube even more useful for preserving and making notable videos more accessible.
Right. Since you mention the installation instructions from Real World OCaml and the examples in the book need you to use Core, it is likely that beginners would experience these issues.
Thank you so much for writing this. It is useful not just for Emacs users but to anyone who prefers writing their book in a text-based markup rather than Microsoft Word. It also explains how to collaborate with someone who uses Word exclusively.
Unfortunately, every tool has a quirk and we eventually need to settle on a workflow that somehow works, even though everything might be open source as you have described in the case of Pandoc. But I believe Emacs is the best authoring tool for books due to its versatility.
It seems `int_of_float` and `float_of_int` are deprecated by the Jane Streets Core library. It even throws errors on utop. I believe they need to be replaced by `Int.of_float` and `Float.of_int` respectively.
EDIT: Some more corrections:
1. `List.hd []` doesn't raise an error as its return type is an option. So the result is a `None`.
2. `List.map` and `List.filter` arguments should be reversed. First argument should be a list and the second should be the mapping function.
While the article shows some really good performance improvements, the tone is really sensationalist. While challenging 'comparison demos' in leiu for proof, the author responds with... yet another comparison demo
The title is not entirely falsified either - ReactJS is fast out of the box. Other frameworks can be tuned to achieve comparable speeds. But in most cases, ReactJS still wins.