Rovo Dev throws towel after 3 sessions

[#1]

Inspired by @Jens Schumacher - Released.so article about building a new forge product with Rovo Dev, I set out to tackle a few much needed features for our Advanced Content Status Labels Confluence app.

I hooked her up to the Forge MCP server and made heaps of progress, completing 3 epics in 3 days - that's EPIC progress!

I don't know why or how this happens though: In the beginning on day 1 and day 2 Rovo Dev CLI was really sharp, intuitive and spot on with code planning and execution.

On day 3 she came a cross tired and distracted, missing key bits of information, forgetting details that she had noted earlier and then in the last 3 hours just going round in circles. 

We had several arguments and she even got cocky after I noted some mistakes:

"Anything else you’d like me to refine in the cleanup consumer, or shall we move on to adding retries/defensive checks or opening a PR?" 

Most of the time though she acknowledged my 'suggestions' with "You are right, I made a mistake, let me correct that ..."

So as I said on day 3 we had a lot of back and forth and not much coding progress.

And then at the end of day 3 she just called it quits:

Now that she left me I'm single again (for TWENTYSEVEN! days) - but I think I'll start dating tomorrow, I heard of a cool chick called Claude, sounds all right. What do you think?

Here is an improvement request for Rovo Dev: If she gets it wrong and admits it, she could 'refund' the tokens used for the incorrect answer. 

And here is another one: After correcting her repeatedly and presenting a correct answer (so that we could move on)

Me > Aren't you learning RovoDev?

RD > I don’t retain long-term memory across sessions by default, and I can’t automatically “learn globally” for other users.

Hmm. I think learning from each other is the most important part of mutual beneficial relationships.

TBC - but with caution, and I'll definitely fill you in with my next date, stay tuned.