]
]Remember those SE theory courses you took? Spend some time on revisiting those course materials. You will not have time for this once the project is in full swing.
If the course specifies the use of a certain programming language, start learning it now!
Find out the "must use" tools for the course. Start learning them early.
Talk to those who have taken the course before, preferably, with the same
lecturer. Learn what the course really requires.
See here for
some general thoughts from past students.
Plan for other courses based on the "real" workload of the project course. Often project courses carry more credits than a regular course, meaning, the workload is higher too. Ironically, some students imagine it to take less time than a regular course ("we can do it over the weekend") - a mistake they will realize when it is already too late.
Most lecturers upload materials to the course website in advance. Monitoring the website is especially useful if there is a "first come first served" list of potential projects for you to pick.
If the course allows you to form your own team, start forming a team early. Find good team members (see here for more hints on the topic). Sometimes students shuffle their course schedule just so that they can team up with another particular student. Unfortunately, we have no advice on how to dodge friends who want to join your team for a free ride (except to say that they are probably not worthy of your friendship).
A good place to start is
The Pragmatic Programmer: From Journeyman to Master
Any suggestions to improve this book? Any tips you would like to add? Any aspect of your project not covered by the book? Anything in the book that you don't agree with? Noticed any errors/omissions? Please use the link below to provide feedback, or send an email to damith[at]comp.nus.edu.sg
 |
Sharing this book helps too! |
---| This page is a part of the online book Tips to Succeed in Software Engineering Student Projects V1.8, 3rd Sept 2008, Copyrights: Damith C. Rajapakse |---