Hardkoded

A few weeks ago I wrote about stable worktrees: six fixed slots, wt1 through wt6, reused instead of recreated.

I moved my whole life into my AI bot.

In Getting Out of Worktree Hell I wrote about stable worktrees: a fixed set of six, wt1 through wt6, each tied to its own cmux session.

The title of this post looks like deep research of unit testing and AI, but it’s more a set of random thoughts.

Puppeteer-Sharp has one simple goal: to be a port of Puppeteer, as close as possible.

I found out that my GitHub profile was quite old.

Git worktrees aren’t new.

If you work on more than one thing at a time with Claude Code, you know the problem.

Everybody is talking about loops these days.

The last time I shared something on this blog was in 2023.

It has been a while since I wrote those Puppeteer-Sharp blog posts (maybe it’s time to do it again?).

I know, I know, I should be writing these posts more frequently, but I’m having so much fun at my new gig, and it’s not easy to keep up the pace.

I’m so excited to announce that, after eight months, Puppeteer-Sharp 3 is here!

I’m so thrilled to announce that my book UI testing with Puppeteer has been published!

Wait, What happened with the November report?

We accomplish two big milestones in September.

It is my pleasure to announce that today Microsoft forked Playwright Sharp!

I’ve been porting Puppeteer code (to puppeteer-sharp) from javascript to C# since late 2017 and Playwright code (to playwright-sharp) since early 2020.

Two months passed since our last monthly report back in July.

As promised last month, We shipped PlaywrightSharp.Firefox v0.10!