#Cursor generate roughly 1k lines of Python.
This included the (pseudo) code for querying #Bookwyrm. I would have preferred to generate this later (as a second step) But maybe it my mistake. I was prompting it wrong. I shouldn't have mentioned anything I didn't directly want.

Without looking at the Bookwyrm client code in detail, I doubt that it will work as my instance ( @realn2s@bookwyrm.social) require #2fa 🤷🏻

Checking the HumbleBundle client code I noticed several things

It contained a ton of normalization code. Of which I'm not sure if it is necessary (it might as well be, but I would leave it out for now. As it much harder to figure out that code isn't required but get executed nevertheless, than noticing that code is missing)

The authentication was done through a session cookie you had to extract form the browser. Cursor proposed to write it to an env file (that doesn't feel terrible secure 😬)

The Humble bundle client could either get the session cookie passed, or it would query the env 😬. I don't consider this good programming practice.

The code looks like it handles HumbleBundle games as well. This was requested and is additional code which shouldn't be there.

Reading through the code it looked about right. But it was too mich code, too much gold plating for me to be confident that the code really would be working.

Cursor provided no way to test the code apart from running it. And I'm not going to run it with my understanding.

On the positive side
I learned about the Click command line option "parsing" library

and about the dataclass decorator in #Python

Next step, let's try if Cursor can iteratively fixe some of my "issues"

2/n