1. Doing much better than expected during my first semester.
2. Found a special someone.

1. Doing below expectation for my second semester, therefore dragging my overall result down to a place I don't want it to be.
2. Losing my special someone.

1. I'll graduate 6 months earlier.



2. I was still considered a "new student" during my 2nd semester, while 99% of the "new students" had only just matriculated. This meant that during module bidding, no one could outbid me since I had way more bids points than they did. This isn't really a big deal though....

1. The modules I'm taking are always "different" from the rest, even those in the same stream, because I started my journey at a time when everyone else had already started their's.



2. Being different, it's hard to find friends to take modules together. More often than not, I end up alone in the module, and have to make friends during class. This may be fine in the level 1 or 2 modules, but as you climb higher, it gets harder because everyone's already in a group of their own. This is probably my biggest regret....Having to start each semester alone in modules which no one else I know is taking. Some familiar faces may walk through the doors, but sometimes they don't.



3. Somewhat related to the point above, is that you won't know how your new friends would perform during project work. And having to work with different people all the time, while it's good training for future employment, is hard to build rapport.



4. So most if not all my problems so far are related to not having friends in the beginning with me in the same module. In the big scheme of things, it may not be a bad thing. I get to make more friends. I just don't like the "lost" feeling in the beginning. Some folks may not see it as a "real" problem....



5. Here's a "real" problem. I only realised this yesterday. This may be a little hard to understand. The modules available for the academic year and usually published before the year starts, so students can plan the modules they plan to take for the whole year (both semesters). This would become increasingly important as you progress further. Let me give an example. A 4th-year graduating student would be left with say....8 modules? He could look at the module offerings for his last academic year, and plan his last 8 modules such that exam and lecture dates do not clash. For me, my last academic year overlaps two regular academic years (semester 2 of one year, followed by semester 1 of the next). So I would not know which modules are offered and when during my last semester. There is a chance that whatever modules I have left at that point could clash and there's nothing I can do about it.

1. Refresh my knowledge of creating/working with SQL databases.
2. Learn ASP.Net for web applications.
3. Learn J2EE for web applications (lots of luck).
4. Throw out my old notes, pack my cupboard to make room for next semester's books/notes.
5. Train up and pass my IPPT before school starts (this is quite hopeless).

"First of all, you should decide which breed of guppy you want to breed. I recommend beginners choosing Black guppy or any type that shows black guppy train, because these can require less care. Choose one or two big and colorful male as you can because that indicate the male have reached its' full grow state. Also you should choose a big female because they give birth to more babies and strong babies later on."

1. This is one of my biggest pet peeve. Say the opposing team's defender clears the ball with a powerful kick that sends the ball back to the edge of your penalty box. What happens? In real life, the keeper would come out and knock the ball back to his defenders. In the game, the keeper stands there watching, while one of the central defenders run from somewhere near the halfway line (if you push up using flat-back strategy) back all the way to claim the ball. Usually he's followed by an opposing team's player. Great......



2. NO ONE WANTS TO GET OPEN! Imagine the full-back running with the ball, with his winger and an opposing player all in a line, with the opposing player in the middle. What happens? Does the winger get open? Nope. He stays in that straight line, lest the full-back pass him the ball. I've lost count of the times I lost the ball because none of my other bloody players would simply GET OPEN!!



3. In Fifa 2005, when one of your players are injured, the controller would vibrate when the injury was suffered. In Fifa 2006, it may or may not vibrate. I played with an injured left-back throughout the whole game once because the controller did not vibrate. Yes, the player status bar would show if the player's injured, but I really haven't the time to look at the bar when I'm looking for another player to GET OPEN!!! AAaaaaahhhhhhhhh!!! *tears out a clump of hair*



4. Long through balls. Oh my God.....The AI has no idea how long/through balls should work. When the midfielders pass the ball over to the strikers using a long through chip (the strikers would be behind the opposing team's defenders at this point to prevent offside), the ball does not land ahead of the strikers. Instead, the strikers run while the ball is in the air, and as the ball land, they would be right at the position to receive the ball. This would also mean that once they touch the ball, the opposing team's defenders would be able to steal it from them. WTF? PASS THE DAMN BALL FURTHER UPFIELD!!! AAAaaaahhhhh!!! *tears more hair out*

1. "A bad place to lose the ball." Tell me, where would be a good place to lose the ball? Go ahead, think. Where would be a good place to lose the ball?

1. Now all screen resolutions from 1024 * 768 and above would be able to view this site quite nicely. If you're using 800 * 600, you'd need to scroll. Can't be helped. Previously, the layout was designed for the 1024 * 768 screens, so even if your resolution was higher, you would still see the site in 1024 * 768 format, with white space on the right.
2. It should load faster and consume less CPU cycles on IE.
3. The problem of white spots on dark pictures on longer exists. I thought it was a Blogger bug, but as it turns out, it was due to the CSS.

New problems:

1. This black border used to be only as tall as the contents using CSS. Now with HTML Tables, the border will be as long as the panel on the right even if the post was short. A little hard to explain, just click on "Read Comments" of any short entry, and you'll see what I mean. All the white space inside the border. When I used CSS, the browser understood that it could "close" the panel as long as all the content has been displayed.