Thought I'd put this down since on second reading its quite nifty, methinks. No one ELSE has to feel the same way - I feel its nifty and that's adequate.
Some background to this letter: I wrote this just before going on a 4 day vacation to Kandy around x'mas. Thought I'd share a few thoughts with my supervisees. The letter was a result of the overwhelming feeling that I'm a totally crappy supervisor - a feeling I still have. So, the letter apparently has not solved that particular problem.
In hindsight its also interesting to note that only 1 student replied to this epistle - unfortunate creature. The rest, I think, did not understand it at all or having been so disturbed by it, have resolved never to refer to it again!
Ok, on second thoughts, the letter is quite 'konky', but I've already resolved to publish it so here goes........
My Dear Supervisees,
Since I'm off for a couple of days of total relaxation, my mind could not but help drifing towards the less fortunate, or more specifically those unfortunate beings with Final Year Projects on their minds. So in my infinite compassion I thought I'd
leave you with a couple of random thoughts that you might find useful/interesting(pick one and only one option, it's one or the other - if its useful its not interesting and if its interesting it wont be useful).
There are a couple of ways in which you can reconcile yourself to your final year project.
a. It's something you've always wanted to do or something that has truly aroused your interest
b. The topic that you've chosen is not your main interest but in doing the project you are sure that you will come across many items of interest that you will enjoy studying
c. It's something you have to do well in order to increase your chances of getting a 1st class.
I hope all of you can lay claim to options a or b. I say this not only because it seems obvious that you will enjoy your projects( if that is indeed possible), if thought of in that light but also because I believe that a 1st degree project is a defining element in your professional life.
Recall that you need to draw conclusions from your project and these conclusions will be your own; not out of a textbook, not out of your supervisors or assessors head but your own. For the first time in your life you will be studying a problem for one whole year and drawing 'your own conclusions'. No one else on earth will know this conclusion or opinion that you hold with as much familiarity or authority as yourself. It is this conclusion, the embodiment of a years study, that you will hold up as your battle standard in life after graduation.
For this to be possible you need to love or at least enjoy what you are doing. So if you can't lay claims to options a or b, please do try to find an area in your project that you can be passionate about.
I guess by now I have successfully confused you, yet again! No matter if that is the case - simply disregard the preceding paragraph. Now on to more practical considerations. And it doesn't matter what your view of your project is a,b or c , when it comes to practical stuff.
To those of you who are on the wrong side of the midpoint interview(i.e. after midpoint, closer to submission):
Now is the time for evaluation and consolidation and planning of that terrible terrible thing called the Documentation.
1. Check whether you are solving a valid problem. Is there a need for a solution? Can you present a watertight case for the justification of constructing your system?
2. RESEARCH: Have you done enough background research? Have you covered all aspects of the problem you are trying to solve? Do you have references for this background research?
3. ANALYSIS: Have you investigated enough alternatives? Is your analysis in line with the stated problem you are solving? Does the analysis follow from the preliminary research?
4. DESIGN: Does the design of the system follow through from your analysis? Can a laymen understand how your system is organized? Do you provide enough alternate perspectives.
5. METHODOLOGY: although natures wonders and geometrical quirks ( waterfalls & spirals) are interesting, what is important is that you have handled the problem in a sensible scientific and practical manner.
6 TESTING: Decide what needs to be tested. What are the critical aspects of your system? What is in short
the rational for testing.
ABOVE ALL, ensure that you are solving a very 'specific' problem and all your work is 'focused' towards solving that specific function - FOCUS.
To those of you on this side of the midpoint:
1. You need to clearly define and scope your problem.
2. You need to justify the validity of the problem and the need for a solution - This will involve a lot of background research.
3. Identify good resources for research.
4. Identify the problematic/risky areas
5. Define 'very specifically' what software you will be constructing
4. You need to identify and start learning the tools you will use (MatLab, C++, SQL Server)
5. You need to identify a development plan - Look at 5. in previous section.
ABOVE ALL, ensure that you are solving a very 'specific' problem but ensure that you have thoroughly investigated the problem domain.
And now, if you have managed to hold onto your sanity, you will be glad to observe that you are at the end of this rather disturbing epistle. My parting words, dear supervisees, is - Reflect on what i have told, if indeed you are inclined to do so,
and then ....
Take a Break. Tis' after all, the season to be jolly .............. tralalala... laa la la la la - Give the blasted project a rest.
We shall tackle your projects in the new year!
Adios.
Gamindu
urped by gumz @ 1:54 PM
