So is abstracted crap only ok if it's already in the JS standard library?

I have some knowledge, albeit very primitive, that I picked up from an HCI introduction and some good designers, but nothing too technical / formal yet.

As opposed to the very few questions about rxjs, where people understand everything perfectly.

I guess.

On my screen, the website is scrollable. Not sure if the animation needs to have top: 30vh and height: 80%

Also: there is a big layout shift right after loading.

const tokens = ['parenOpen', 'bang', 'plus', 'minus'] as const;

type Token = typeof tokens[number];

type TokenTable = Record // alias for { [key in Token]: T }

const isToken = (t: string): t is Token => tokens.includes(t);

const patterns: TokenTable = { bang: /\+/, // rest }

Also, it appears to be feature-rich and yet easy to use for simple use cases.

If there is an upcoming meeting with a zoom/teams/ link attached, you can join by pressing enter.

Never had to look for a meeting link again.

I'm not sure if Alfred has this as well, but nevertheless, i just love this feature

In a perfect world (for me, from my point of view), there are no deadlines, but rather short plans and enough understanding of the plan to decide whether doing something specific is useful or a hindrance (and to what degree) for executing that plan.

But alas, deadlines are easier to decide on.

After all, it is currently the nature of web software that the source code must be available (for browsers to interpret)

citation needed.

Other than that, I would love to see a bit better semantic markup, not because I'm some sort of HTML purist who demands everything to be pure, but because it would make it easier to style with CSS (which I did, to add dark mode, bigger font sizes and max widths). Currently, it's nested tables with occasional classes and ids, but not for everything.