Just dropping in for the customary exchange of greetings. Except in this case is isn't really an exchange as such, being as it is a blog whose very nature dictates that all communication can only traverse the distance between our computers in one single direction (with that being from myself to you). Unless of course one takes into account the possibility that you, the user, make use of the post commenting function, in which case it could be argued that this does indeed constitute an exchange of greetings. That said, it is one which is rarely consummated - as can be seen from the sparsity of such reciprocations on this very website, precious few internet users are of the commenting persuasion and a page generally needs to have somewhere in the region of a hundred viewers in order to secure a comment. And that's assuming the page is even relevant to the interests of that particular set of users and capable of provoking the thought required to drive them to express views upon it. Sadly these are criteria which have almost certainly gone unmet by this particular work (what with it being a foolishly pedantic ramble), and so it is logically defensible to say that this post does not, in fact, count as an exchange of greetings in any but a few cases. Therefore my first sentence was erroneous. Sorry about that.
Merry Christmas!
Thursday, 24 December 2009
Friday, 11 December 2009
Cambridge raverviews!
So, here's how they went.
First up was the subject-specific interview. This one had moments of awesome and moments of shoddy, but was generally okay. Once again I was surprised by the complete lack of personal statement questions - they began by reading through the main points ("so you've done C++ and python, made a few programs...") and then indirectly asked why I wasn't taking computing. It was posed as something like "Most candidates are normally doing A-level computing, but you don't seem to have done it at all; where does the background in computer science come from?" Thankfully I was prepared for this, and explained that it was something that greatly interested me and which I had mostly learned for fun in my free time. To answer the implied question of why I had no formal computing education I said something vague about the Standard Grade course not being particularly relevant to a degree (which is true), which is what I'd always intended to do (which is mostly true, although I wasn't very certain of what I wanted to do back then - I decided against Standard Grade computing on the grounds that I was already learning it myself). And then they asked about what sort of projects I've done, so I rattled off a big old list of things I've been doing recently. Hopefully it wasn't too disjointed and rambly.
And then came the technical questions.
Firstly, they got me to work out what a piece of code did, which was simple enough but took me a little while as there were a few off-throwing loops. They didn't appear to be too bothered by that though, and I think bonus points were gained on the second part of this one as I worked it out relatively speedily. They then got me to devise an algorithm (I don't think I can say what for), which I luckily managed to do rather quickly - they seemed fairly pleased by this one. I then had a proof by induction, which got off to a terrible start when I mistook the technique they asked me to use for a direct proof. And it went downhill from there. The less said the better, really. Not one of my finest moments. Moving onwards, this was followed up by a question about a finite state machine diagram, and I get the impression that several bonus points were gained when I mentioned that I had seen one before (based on the rather surprised reaction by which this was received). They asked me to add bits to it in order to add extra functions, and there was a bit of to-and-fro-ing here as I made a few mistakes at the beginning and then went about the last part of the question in what was apparently not the intended way. They said it was still correct though, so hopefully the question wasn't too much of a failure.
And that was that. Not too bad really; it could have gone far worse. It was certainly better than the Imperial interview anyway, although I hear that Cambridge interviews are much more important that Imperial interviews when it comes to selecting candidates (Imperial do a lot more pre-interview selection, and so those with interviews are fairly likely to get offers).
This first interview was closely followed by the TSA, or Thinking Skills Assessment. A glorified IQ test really, but with slightly harder questions and a large number of questions that are to do with identifying underlying assumptions, flaws or main conclusions in arguments. The one I did at Cambridge was actually a lot harder than the online practice one, and I ended up using the full hour and a half. I did however answer all but four questions with certainty which varied between definite (for most), and moderate (for about a fifth of them). Not a clue what my results were, and indeed I'll never be told; it'll make a contribution to my application in consummate secrecy. Ominous.
So, tired and mentally worn out as I was, I trudged on to the last event of the day: the Natural Sciences interview. This has to be taken as well because the Computer Science Tripos at Cambridge involves a Natural Sciences portion for the first year (which is rather awesome actually). However, I was slightly worried at the prospect of an interview on the topic as I've done minimal revision for such a thing. And "Natural Sciences" is so ill-defined it could well bring in work I did and forgot in first-year Biology.
Thankfully, however, it was just Physics with a bit of Maths. And IT WAS GLORIOUS! Glorious and victorious. The questions were almost all easy, and I steamed through about seven or eight in the twenty-minute interview. I made a few mistakes, but in general I managed to answer every question with all the speed and accuracy of a well-guided cruise missile. Yes, that's a mild exaggeration. However I do feel rather positive about this last interview, and so it was a nice way to end the (long and arduous) day.
So then I was off, on the six-hour train journey back to here, where I found an offer from Imperial awaiting me. I'm still dancing on the ceiling about that one. And it's making it considerably difficult to type.
First up was the subject-specific interview. This one had moments of awesome and moments of shoddy, but was generally okay. Once again I was surprised by the complete lack of personal statement questions - they began by reading through the main points ("so you've done C++ and python, made a few programs...") and then indirectly asked why I wasn't taking computing. It was posed as something like "Most candidates are normally doing A-level computing, but you don't seem to have done it at all; where does the background in computer science come from?" Thankfully I was prepared for this, and explained that it was something that greatly interested me and which I had mostly learned for fun in my free time. To answer the implied question of why I had no formal computing education I said something vague about the Standard Grade course not being particularly relevant to a degree (which is true), which is what I'd always intended to do (which is mostly true, although I wasn't very certain of what I wanted to do back then - I decided against Standard Grade computing on the grounds that I was already learning it myself). And then they asked about what sort of projects I've done, so I rattled off a big old list of things I've been doing recently. Hopefully it wasn't too disjointed and rambly.
And then came the technical questions.
Firstly, they got me to work out what a piece of code did, which was simple enough but took me a little while as there were a few off-throwing loops. They didn't appear to be too bothered by that though, and I think bonus points were gained on the second part of this one as I worked it out relatively speedily. They then got me to devise an algorithm (I don't think I can say what for), which I luckily managed to do rather quickly - they seemed fairly pleased by this one. I then had a proof by induction, which got off to a terrible start when I mistook the technique they asked me to use for a direct proof. And it went downhill from there. The less said the better, really. Not one of my finest moments. Moving onwards, this was followed up by a question about a finite state machine diagram, and I get the impression that several bonus points were gained when I mentioned that I had seen one before (based on the rather surprised reaction by which this was received). They asked me to add bits to it in order to add extra functions, and there was a bit of to-and-fro-ing here as I made a few mistakes at the beginning and then went about the last part of the question in what was apparently not the intended way. They said it was still correct though, so hopefully the question wasn't too much of a failure.
And that was that. Not too bad really; it could have gone far worse. It was certainly better than the Imperial interview anyway, although I hear that Cambridge interviews are much more important that Imperial interviews when it comes to selecting candidates (Imperial do a lot more pre-interview selection, and so those with interviews are fairly likely to get offers).
This first interview was closely followed by the TSA, or Thinking Skills Assessment. A glorified IQ test really, but with slightly harder questions and a large number of questions that are to do with identifying underlying assumptions, flaws or main conclusions in arguments. The one I did at Cambridge was actually a lot harder than the online practice one, and I ended up using the full hour and a half. I did however answer all but four questions with certainty which varied between definite (for most), and moderate (for about a fifth of them). Not a clue what my results were, and indeed I'll never be told; it'll make a contribution to my application in consummate secrecy. Ominous.
So, tired and mentally worn out as I was, I trudged on to the last event of the day: the Natural Sciences interview. This has to be taken as well because the Computer Science Tripos at Cambridge involves a Natural Sciences portion for the first year (which is rather awesome actually). However, I was slightly worried at the prospect of an interview on the topic as I've done minimal revision for such a thing. And "Natural Sciences" is so ill-defined it could well bring in work I did and forgot in first-year Biology.
Thankfully, however, it was just Physics with a bit of Maths. And IT WAS GLORIOUS! Glorious and victorious. The questions were almost all easy, and I steamed through about seven or eight in the twenty-minute interview. I made a few mistakes, but in general I managed to answer every question with all the speed and accuracy of a well-guided cruise missile. Yes, that's a mild exaggeration. However I do feel rather positive about this last interview, and so it was a nice way to end the (long and arduous) day.
So then I was off, on the six-hour train journey back to here, where I found an offer from Imperial awaiting me. I'm still dancing on the ceiling about that one. And it's making it considerably difficult to type.
Thursday, 10 December 2009
Imperial college verdict
I got an offer! Yaaaaaaaaaaaaaaay, etc. I'm rather surprised actually, as I've spent the last week or so gradually lowering my estimation of how well I did and by the time I opened the letter (which, ominously, was small and white) I was already certain of being rejected. 'Twas a pleasant surprise indeed.
Unfortunately, it's rather harsh:
So, how did Cambridge go? Well, that'll have to wait for tomorrow when I have the energy to write anything of length. I just gave my entire brain-usage quota for the day to Cambridge. It wasn't too bad though; indeed, the second interview was glorious. Returning home to find a nice shiny offer from a university I was already mentally crossing off as a failure topped off the evening nicely, and has killed my short-term memory thus making me forget all the specifics of what went down in Cambridge, so even if I had the energy to write I probably couldn't recount the day's escapades just now. Watch this space, if you can be bothered at this time of night.
Unfortunately, it's rather harsh:
- A band 1 in Maths (Advanced Higher)
- A in Physics (Advanced Higher)
- A in English (Advanced Higher)
- A in History (Higher)
So, how did Cambridge go? Well, that'll have to wait for tomorrow when I have the energy to write anything of length. I just gave my entire brain-usage quota for the day to Cambridge. It wasn't too bad though; indeed, the second interview was glorious. Returning home to find a nice shiny offer from a university I was already mentally crossing off as a failure topped off the evening nicely, and has killed my short-term memory thus making me forget all the specifics of what went down in Cambridge, so even if I had the energy to write I probably couldn't recount the day's escapades just now. Watch this space, if you can be bothered at this time of night.
Wednesday, 9 December 2009
And so it begins...
Today I leave for Cambridge, to be interviewed and multiple-choice-tested tomorrow. Oh dear.
I shall tell of the horrors I faced upon my Thursday return, unless of course I'm too scarred by it all and can't post again until Friday. Either way, watch this space!
I shall tell of the horrors I faced upon my Thursday return, unless of course I'm too scarred by it all and can't post again until Friday. Either way, watch this space!
Sunday, 29 November 2009
Oh noes!!
*annoying popping sound*
MCAFEE WARNING
The program 'McAfee updater' is trying to access the Internet!!! OMGWTFLOL!!
*pause*
*annoying popping sound*
MCAFEE WARNING
McAfee is out of date! Oh noezzz what shall we do?!?!?
I shit thee not. Well, perhaps it wasn't worded quite like that, but that's how I choose to read it. Yes, McAfee SecurityCenter (bloody American spellings) has finally caught up and realised that the most potent threat to my computer is, in fact, McAfee SecurityCenter. And not just because it's designed by people with dodgy spelling skills and space-bar-aversion; no, apparently it's trying to access the Internet. Not only that, but it's antiquated as well! (And for some reason it's of the view that downloading the latest version would solve this.)
Usually, when it starts complaining about updates, the resolution is a simple case of clicking 'install updates.' However, since the latest SuperAwesome McAwesomeUpdate (NowWithEvenFewerSpaces), its very components are at odds with one another all of a sudden, and such an endeavour is obstructed by anti-virus anti-productivity red tape. So what happened? Well, allow me to retell a tale whose horrors shall play upon your very bones like some form of poorly-tuned percussion instrument. Yes, I know that didn't make any sence.
Upon restarting (which I was compelled to do by a big impertinent pop-up which repeated its demand like a child seeking sugar), I was immediately affronted by a torrent of McWhineBoxes. Every single one was from good ol' McAfee, asking for yet another of its components to be allowed access to the Internet. I honestly wasn't aware that it comprised so many discrete processes, but there we go. I suppose it serves as an example of the lengths programmers will go to outrequire the latest hardware.
Now, at least that can be easily dispelled through an hour or so of mindless allowing (during which period I may unintentionally have allowed Internet access to thousands of malwarez without noticing). However, another more pressing issue remains: McAfee SuperFireWallPlus isn't intalled!!! Or, at least, the middle-right portion of the SecurityCenter window believes that. The bottom-left portion knows it's there, but is keeping that to itself. Why? It's simple; the two portions have fallen out:

Now, one question remains. What did this new and glorious update actually add, to counterbalance the inconvenience of having to exhaustively allow every single one of McAfee's myriad sub-processes, and at the expense of the program's capability of determining its own integrity?
A new splash screen.
MCAFEE WARNING
The program 'McAfee updater' is trying to access the Internet!!! OMGWTFLOL!!
*pause*
*annoying popping sound*
MCAFEE WARNING
McAfee is out of date! Oh noezzz what shall we do?!?!?
I shit thee not. Well, perhaps it wasn't worded quite like that, but that's how I choose to read it. Yes, McAfee SecurityCenter (bloody American spellings) has finally caught up and realised that the most potent threat to my computer is, in fact, McAfee SecurityCenter. And not just because it's designed by people with dodgy spelling skills and space-bar-aversion; no, apparently it's trying to access the Internet. Not only that, but it's antiquated as well! (And for some reason it's of the view that downloading the latest version would solve this.)
Usually, when it starts complaining about updates, the resolution is a simple case of clicking 'install updates.' However, since the latest SuperAwesome McAwesomeUpdate (NowWithEvenFewerSpaces), its very components are at odds with one another all of a sudden, and such an endeavour is obstructed by anti-virus anti-productivity red tape. So what happened? Well, allow me to retell a tale whose horrors shall play upon your very bones like some form of poorly-tuned percussion instrument. Yes, I know that didn't make any sence.
Upon restarting (which I was compelled to do by a big impertinent pop-up which repeated its demand like a child seeking sugar), I was immediately affronted by a torrent of McWhineBoxes. Every single one was from good ol' McAfee, asking for yet another of its components to be allowed access to the Internet. I honestly wasn't aware that it comprised so many discrete processes, but there we go. I suppose it serves as an example of the lengths programmers will go to outrequire the latest hardware.
Now, at least that can be easily dispelled through an hour or so of mindless allowing (during which period I may unintentionally have allowed Internet access to thousands of malwarez without noticing). However, another more pressing issue remains: McAfee SuperFireWallPlus isn't intalled!!! Or, at least, the middle-right portion of the SecurityCenter window believes that. The bottom-left portion knows it's there, but is keeping that to itself. Why? It's simple; the two portions have fallen out:

Now, one question remains. What did this new and glorious update actually add, to counterbalance the inconvenience of having to exhaustively allow every single one of McAfee's myriad sub-processes, and at the expense of the program's capability of determining its own integrity?
A new splash screen.
Subscribe to:
Posts (Atom)