Check out my Bitbucket projects

CCC16S1: Done in Java on my own, it was decent.

CCC16S2: This one was easy, Java.

CCC16S4: This one was really hard. I wanted to solve it by brute force, however this was not possible. On my own I was able to get 3/15 points. However after looking at the solution guide and the test data, I got the marks. Had to do it in C++11 because I thought Java was too slow, however I'm sure it would have been possible to do it in Java too.

16 BIT S/W ONLY: This one was really easy, but then again, it was only worth three points.

CCC16S3: First attempt got 9/15 (on my own, no test data, no editorial). On the second attempt I got 13/15 (with the editorial's help). I'm not going to keep going right now though, maybe another day

A20: This was a fun one. Not too hard, not too easy. Done without reading solutions.

CCC16S5: Very hard

CCC15S1: Really easy. No solutions read.

CCC15S2: It was easy, however I got stuck because I misinterpreted the question. It was important to realise that 'J' sizes were also numbers of the Jerseys. Got 6/15 on my own. Got the rest after reading the editorial, rereading the input specification and input example.

CCC15S3: Got 12/30 By accident. Couldn't get farther without the editorial. Kind of quirky how std::upper_bound and std::lower_bound and their equivalents don't do the opposite of one another, but instead do the same thing save for a greater than equal or greater than difference. Not really worth posting my code on BitBucket because it is basically the same as in the editorial.

CCC15S4: Dijkstra's algorithm! I know this! 14/15 on first try with no help. Not going to go for the last point. Get more practice in for other stuff on the CCC.

CCC14S1: Pretty easy.

CCC14S2: Pretty easy.

VMSS7WC16C1P3: 8/10 without test cases. Rest with test cases. Would have been happy with the 8, but there were no partial marks.

CCC13S1 (Same as CCC13J3): This one took 15 minutes. Probably should move on to harder problems now.

CCC13S2: This one took 40 minutes. Deque helps in C++, or just being more careful.

CCC12S3: Problem from hell. Probably not, but I couldn't solve it in an hour, and I was using the cccgrader website which was timing me and made the whole experience frustrating.

CCC17S: Wrote it. I guess we're done here now.