> In our case, we still felt this decision was justified because we don't have to recreate a scheduler with all the complexity of React's; we can build a small, self-contained implementation that only implements what we need.

I wish there were more details about this. Implementing a small scheduler seems like a monumental task and I'd love to learn more about how to implement a base-case.

Not OP, but if you're building a small scheduler for batching changes, it should be pretty straightforward:

- `jobs` is an array of functions

- enqueue adds a job to `jobs` and starts running jobs if not running

- job running can be triggered by animation frames or setTimeout

I really like the saying 'bell the cat' as well. Anyway, came here to say that I started to do this (create the missing documentation that would've been helpful for me) - it is by no means ready ( on mobile this site looks almost unreadable ) but it is a start: www.hugotutorial.com - if you have any feedback, I would love it!

So, they've been useful for me and some of my friends, but it is worth sharing the specifics to know if it'd apply to your own situation. I did create a site focused on creating cover letters (crowded marketplace, but I had fun doing it), www.coverletteremails.com, here's what I learned in the process:

First, the format has changed. It was written about in this thread, but if you are sending an email, then the body of the email is basically your introduction / cover letter. I've never opened an attachment to an email (especially if it was .docx file, which does still happen) when evaluating candidates.

Second, emails haven't been as useful in sharing cover letters and resumes (kinda ironic that I built a site focused around emails, I know - lessons learned :) ). What has worked really well is a simple html page. This has worked far better - here is an example of one that I used, edited. https://www.coverletteremails.com/letters/honeycomb.io/ (full disclosure - I didn't get that job, but working at honeycomb would've been incredible).

Having a URL like the one above has been helpful. Usually, if you are applying through something like greenhouse.io, there will be a section for you to enter your cover letter, in that section, I would write something like "I put together a quick intro of myself at https://wwww....".

I don't have any statistics on things like 'how many times was this opened' because I thought it'd be cheesy to include something like google analytics on a page like that. I guess I could evaluate logs and such, but never got around to it. So the only evidence I have is interviewers saying something like "I liked your intro / or I liked your cover letter ... how'd you build that?"

hope that's helpful

FYI, "It uses Tuft CSS, inspired..." should be Tufte.