howToTestFE

Pretty sure Laravel source code comments above functions were always something like 3 lines, with each line slightly less length than the previous one. Not sure if this is still done or enforced at all, but it was always neat to see.

Here is an example - https://github.com/illuminate/database/blob/master/Connectio... - looks like each one is 3 characters shorter.

Site/course on teaching how to write tests, mostly about frontend tests in React but also just generally things like Vitest/Jest https://howtotestfrontend.com/courses/jest-vitest-fundamenta...

+1 very confusing name for another mongodb compatible db.

Yep. I think there are so many new apps, when I run a `npx skills add ...` , the list of what tools (like claude code, open code, etc) to install skills in is getting larger every time I use it.

I will check it out though.

100%. its a horrible code smell, and AI loves to jest.mock (or vi.mock()). (The most recent blog post on my site covers this as one of the things to look out for in AI generated tests...)

in JS (with Jest/Vitest) it is far too easy to call mock()...

yup vitest is great (my default choice for new projects).

vitest browser mode is really nice too. (new-ish feature, although at this point it isn't exactly new).

learn step by step the main features of both Jest and Vitest (they're very similar for most common usages) in these interactive4 lessons

Blog post comparing Vitest vs Jest

not sure how interesting to others, but i thought this was really cool.

(I am not affiliated with posthog at all. Just typed an incorrect address and came across it.)

Has anyone got any good resources for something like this? I haven't touched C in years, and never worked on anything game-like. But it does look like a really interesting project to start something like this.

tldr - `tsc` can be replaced with `tsgo`. `eslint` replaced by `oxlint`, and `prettier` replaced with `oxfmt

this makes me want to play simcity again! really cool