markalby
I rebase a lot using Fork (git gui) and it’s really easy to drag and drop reorder commits, rename, apply as fixups or squash in. I can see how jj makes sense if you’re in the command line, though. And splitting changes from commits in git is really annoying, but it only comes up once in a blue moon for me.
Turn on persist logs in the dev tools network tab; go through as much as the flow as possible; filter out domains that aren’t your site: google, facebook, external api calls; download the .har for all of whats left; convert har into a k6 script using a library, or dump that into an llm to convert it to their newer browser script and point the llm at their docs; edit it to be dynamic so you can test paths from different product pages/types, and scrape and enter proper guids, etc.
On the flip side we’re seeing a lot more bot traffic likely due to bad actors doing this too, but by writing these tests you begin to see what calls cause load and be proactive.
I picked up the habit a couple years ago of just undoing the autocorrect to an em dash and leaving it as two dashes to avoid accusations -- now it’s stuck with me