Also I don't like how lazy it is. It even decides to skip tests in the same manner I do, just because they are a bit inconvenient 😂

Not sure if my explanation makes sense. I might try storybook soon again, to see what has improved.

I did when it came out, but documenting events was annoying as hell.

For example, I had an event "select". In order to use actions, I had to make a story with onSelect, otherwise it would not work.

Then it showed both "select" and "onSelect" in the table under the component (in doc module).

If nothing else, the source code might be worth learning from. 🙂

Admittedly I haven't seen your talk about graphql. Just going by the title, how well do you think it has aged? I've seen many companies leave graphql and return to REST/RPC.

My biggest obstacle of public speaking is the fear of "being wrong", however I would like to try it once.

I might give it a try once we finish beginner box :) thank you for the ideas

Thanks, I'll check it out, although I might try to find or write some simple tracker that can be used on the phone, as there's not enough space for laptop on the table we have 😅

I am just struggling with tracking initiatives and statuses. Hopefully I'll find a way that fits me soon.

We should play another part on Tuesday - with all players this time.

It went fine :)

We were missing one player so I had to gm and play wizard (just for fights), but the players seemed to like the game overall.

Got through about 1/3 of beginner box.

Luckily there's not too many conditions to track in BB in comparison to higher level play. Hopefully tracking in a notepad will be enough.

Summary at the start of the turn sounds useful, thanks.