Build.2.Score - Part.II

Here comes the second part of my thoughts on FYP tips...

Tip#3 - Make Web Applications The Last Choice.

Depending on the major you are taking, you may want to avoid web applications. To be honest, I feel that there is nothing cool about web applications. You need to master atleast 3 to 4 things before you can come up with a decent user interface. Don't believe me? Let's count together - ASP.NET (VB.NET or C#), Javascript, CSS and DHTML. Also, different browsers render the UI differently.

Windows applications are many times easier to build and most IDEs are mature enough to handle the development. Just drag-and-drop and whalla! Most of the time, the FYP assesses us for the problem domain (or business problem) that we need to solve - not much on whether the application is web-based or not (unless specified).

If you really have to build web-applications, make sure you only web-enabled the right features. Web-enabling a leave application is ok but on an invoicing or POS system, it is impractical.

Tip#4 - Choose the Right Topic

Unless you are assessed on algorithms or AI (or taking a degree in game development), avoid developing games in your FYP. I've seen many friends who develop games for their FYP struggled miserably - particularly when they chose to develop 3D games. I believe at any point in time, some of us would have thought about developing games but unless we are studying it (or up to it), don't risk it in an FYP.

Developing games will give a lot of disappointment. First of all, there is no way we can produce a C&C Generals or a Counter Strike in 6 months FYP duration (plus documentation!). Secondly, the awesome games out there will have indirectly set the expectations of people - so you have to build your game up to par. Lastly, telling you inteviewer about your game isn't going to impress him/her (unless it is a game company).

Choosing the right topic that you can understand and deliver is essential. As a bonus, choose a topic that can benefit you in a job interview.