first day of sem break

failed the trend micro competition due to mismanagement. i learned this time around that no matter how good one is, you can only do so much in a given amount of time. one has to be smart in choosing which projects to be part of. do the projects add value to the current skill set of the person? what is the probability that the skill to be learned from such undertaking will be useful in the future?

one has to be smart in choosing which projects add value to the company. focus on your core competencies and expand slowly but surely. just look at steve jobs. the macs. pixar. ipod. what's next? one thing at a time.

starting today, i hope to finish an alpha version within two or three days of my own task scheduler. something like what google desktop has. actually, the end product will be an approximation of google desktop and i'm calling it pip's desktop. hehe. google desktop is great but it leaves some stuff to ask for. so i'm inspired by google.

...

of course not, i wouldn't steal code from others. that would be unethical.

...

prototype (done so far) :

programming language used : c#
storage method : m$ access database
design pattern : none. everything is in one big class.
can: accept tasks with names, priority levels, primitive categorization and date due

alpha (to do):

interface for online version (PHP) and mobile devices (J2ME, PPC)
additional storage capability for MySQL, XML, CSVs
java version
MVC model : separation of presentation and application layers

finished product:

an application that will allow you to track your schedule wherever you go. yep, it's a glorfied pen and paper checklist. using various technologies, i would like to learn designing different systems and how they can interact with each other.