I saw that, I was more interested in other examples you might have since you said that you have started to run two sessions at once to be more productive. And this bug doesn't look like such workload.
The issue is I am working on non-public projects so it is harder to share. But I have a mono-repo that has 8 packages in the packages/* folder and it is all managed by pnpm. I had two sessions going locally in two separate terminal windows in cursor. One was modifying 2 packages to add a feature and another session was modifying another package that was orthogonal to the first two.
This isn't really professional - it felt wrong - one shouldn't be adding two separate features at once, but because they were isolated I could check them in separately into Git as two separate commits.
It was as if two coders were working on the same checked out code.
I need to move this into a cloud service and that is coming soon.
Ping me at ben@benhouston3d.com and I can show you some live demos. It works incredibly well.
I don't see anything wrong with that tbh. If it works that's great since this means that you're bound by the compute power you have and not the amount of devs available at that moment. I guess this is what the wet dream is about.
Working on two features at once is not weird pre-llms too. Though it's a scheduling problem rather than parallelism. CI tests are running for feature A while you work on feature B. If feature A fails, at some point you context switch back and work on it more etc
Of course, business incentive is to have people complete as much stuff as they can per time unit. I don't think I ever had a luck to work in an environment where anyone in the team wouldn't be working on multiple things at the same time. Truth to be told these weren't the traditional scrum or any other bs driven environment. More like high performance teams where pretty much anyone was quite exquisite.
