If I want that kind of a challenge, I could start "challenging" myself to cook a dinner with both hands tied behind my back while refusing to light the stove.
Wait, you
don't uppercut yourself repeatedly before playing? I'm shocked... truly shocked.
CGs weren't without their problems, but the good thing was, over time it balanced itself out.
I remember on CG where we reached Tier 8 on Friday evening, so a lot of players didn't even have a chance to take part in it.

I had a week off and made 60 millions in that CG and could afford my first Python. The forum was outraged. Good times.
Thing is, FD have
never been good at estimating numbers on any of their CGs. They
started to get good, but sometimes I just get the feeling maybe it's one of those development shops where the devs[1] have no strategic vision or input for the game, and don't collaborate on those issues. For example:
- Regression testing. Every time there's a patch, something which was broken, then fixed, breaks again, in exactly the same way. FC's update, it was
research limpets and tissue sampling.
- Estimating effort for CGs. When we got our first non-market-available collection CG for Meta Alloys... it got given numbers like a standard trade CG, which was never going to work because of how slowly you collect meta-alloys... by the time you collected 10, you could have shipped 1000t of a given market good. This got adjusted, but not by much. Then we had a search and rescue CG, which also got issued with standard market-CG numbers and suffered the same issues. Someone made the right call then, and got the numbers right, with the CG capping out after close to a week. All future search and rescue/salvage CGs had the right number at that point, but then a "collect tissue samples" CG came out, which has the same limitations, but again had market cargo levels set.
- The length of time it takes for fixes, and their knock-ons. Major imbalances always take FD
at least a year to address. No idea why, but in the meantime, they develop game mechanics/activities which
rely on that imbalance or bug. Then of course, the bug gets fixed, et voila, we have a forum up in arms because so many people had just accepted "this is the way things are now". It's like they don't know what's coming next, or how to implement it.
As my footnote will further reinforce, don't take this as dev bashing. I've built my career off software dev, and I've seen a lot of good and bad things go on... but rarely, if ever, have I dealt with a dev who is a plain potato. Rather, they're not given the direction, time or freedom-of-action to actually get the job done, and that's a call by managers.
[1] Not bashing devs here, in my experience it's never the devs themselves who are at fault, rather, a litany of cultural issues resulting in it simply never happening. A highly skilled dev
can resolve the issues, but it's usually cloak-and-dagger stuff while they fight an impotent management team