One of the entries 'Cap' describes one thing and links to another though. The description is of a collaborative code editor. The link and screenshot are for a Loom alternative, so screen recording.
The article also reminded me of this Charlie Munger quote:
“It is remarkable how much long-term advantage people
like us have gotten by trying to be consistently not
stupid, instead of trying to be very intelligent.”
Sometimes not doing something stupid is at once easier and harder than trying to get into a good habit.
In the fiction category I thouroughly enjoyed the "Green Bone Saga" by Fonda Lee:
- Jade City
- Jade War
- Jade Legacy
The story sits somewhere between Asian mafia clan drama, crime and magical fantasy.
They were the kind of books where I buy both audio and paperback to keep reading wherever possible..
On jamstack.org's list of static generators[0] you can filter by template language. For "R markdown" it only has:
Bookdown[1], Rmarkdown as you mentioned, and Blogdown[2].
I've never looked at R markdown before. Thanks for sending me down the rabbit hole with Bookdown. It might solve one of the questions I'm currently thinking about.
Compared to more modern tools Jira is actually not very flexible.
For me the most flexible and useful tools are Kanbanize[0] and Kaiten[1].
Both companies are engaged in furthering the Kanban method which also means they care about having a lot of features for displaying cards, limiting work in progress, defining workflows and have solutions for working together on bigger workflows with several teams.
I use both professionally.
A lot of other solutions have assumptions built in which really limit flexibility. One example in Jira is the coupling between workflow status and columns on boards.
